routing issue? could someone from verizon FiOS please take a look?

Verizon Fios cannot connect me to lavra.spb.ru

This is the Russian site of the second most important monastery in Russia.

It is reachable from Boston avra.spb.ru (91.218.229.131), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 2.293 ms 0.815 ms 0.764 ms
2 100.64.0.129 (100.64.0.129) 1.108 ms 3.013 ms 1.068 ms
3 10.16.28.1 (10.16.28.1) 1.411 ms 1.277 ms 1.068 ms
4 10.16.13.1 (10.16.13.1) 4.796 ms 2.301 ms 5.207 ms
5 69.46.226.129.lightower.net (69.46.226.129) 4.380 ms 3.138 ms 4.630 ms
6 ae2.bstpmallj42.lightower.net (64.72.64.113) 3.768 ms 6.008 ms 3.888 ms
7 xe-4-0-2.bar2.boston1.level3.net (4.53.56.153) 6.030 ms 4.890 ms 7.058 ms
8 ae-231-3607.edge4.london1.level3.net (4.69.166.25) 91.525 ms 81.571 ms
    ae-232-3608.edge4.london1.level3.net (4.69.166.29) 81.327 ms
9 ae-231-3607.edge4.london1.level3.net (4.69.166.25) 78.121 ms
    ae-232-3608.edge4.london1.level3.net (4.69.166.29) 79.734 ms 78.890 ms
10 195.50.122.186 (195.50.122.186) 173.491 ms 133.054 ms 198.495 ms
11 * * *
12 oversun-gw.transtelecom.net (217.150.54.25) 210.399 ms 138.519 ms 139.291 ms
13 mr-o-rtc1-rsw-2.oversun.ru (94.198.48.154) 131.070 ms 131.007 ms 129.553 ms
14 mr-o-rtc5-rsw-2.oversun.ru (94.198.48.110) 140.012 ms 208.023 ms 145.352 ms
15 vip-h5.ihc-ru.net (91.218.229.131) 131.485 ms 133.319 ms 129.822 ms

and from comcast and other locations

apparently it has v6 routing info as well ..someone much more knowledgable than i suggested that this can be a source of reachability problems

but here is what happens on my machine

ordons-mac-pro:~ gordoncook$ traceroute lavra.spb.ru
traceroute to lavra.spb.ru (92.242.140.21), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 0.654 ms 0.351 ms 0.295 ms
2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 4.607 ms 4.326 ms 7.869 ms
3 g0-1-0-0.cmdnnj-lcr-22.verizon-gni.net (130.81.223.100) 12.172 ms 9.502 ms 7.242 ms
4 xe-9-1-6-0.ny5030-bb-rtr2.verizon-gni.net (130.81.199.226) 15.080 ms
    xe-9-1-2-0.ny5030-bb-rtr2.verizon-gni.net (130.81.209.144) 8.986 ms
    xe-4-1-8-0.ny5030-bb-rtr2.verizon-gni.net (130.81.209.84) 22.085 ms
5 * * *
6 0.ae1.br2.nyc4.alter.net (140.222.229.91) 79.467 ms 77.046 ms 74.729 ms
7 204.255.168.114 (204.255.168.114) 85.591 ms 86.899 ms
    204.255.168.110 (204.255.168.110) 87.011 ms
8 be2061.ccr42.jfk02.atlas.cogentco.com (154.54.3.69) 96.323 ms
    be2060.ccr41.jfk02.atlas.cogentco.com (154.54.31.9) 84.779 ms
    be2061.ccr42.jfk02.atlas.cogentco.com (154.54.3.69) 85.063 ms
9 be2482.ccr21.cle04.atlas.cogentco.com (154.54.27.157) 31.562 ms 31.990 ms
    be2483.ccr22.cle04.atlas.cogentco.com (154.54.29.201) 27.548 ms
10 be2351.ccr41.ord01.atlas.cogentco.com (154.54.44.85) 37.087 ms
    be2185.ccr42.ord01.atlas.cogentco.com (154.54.43.177) 42.273 ms
    be2351.ccr41.ord01.atlas.cogentco.com (154.54.44.85) 39.590 ms
11 be2157.ccr22.mci01.atlas.cogentco.com (154.54.6.117) 49.793 ms
    be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 50.583 ms
    be2157.ccr22.mci01.atlas.cogentco.com (154.54.6.117) 49.492 ms
12 be2133.ccr22.sfo01.atlas.cogentco.com (154.54.30.65) 77.446 ms
    be2132.ccr21.sfo01.atlas.cogentco.com (154.54.30.53) 77.060 ms
    be2133.ccr22.sfo01.atlas.cogentco.com (154.54.30.65) 77.001 ms
13 be2164.ccr21.sjc01.atlas.cogentco.com (154.54.28.34) 74.999 ms 74.569 ms
    be2165.ccr22.sjc01.atlas.cogentco.com (154.54.28.66) 74.852 ms
14 be2063.rcr21.b001848-1.sjc01.atlas.cogentco.com (154.54.1.162) 74.377 ms
    be2095.rcr21.b001848-1.sjc01.atlas.cogentco.com (154.54.3.138) 77.126 ms 89.476 ms
15 c1.sj.mpt.fiberinternetcenter.net (66.201.58.2) 82.483 ms 86.964 ms 80.094 ms
16 sanjose2.barefruit.co.uk (66.201.32.134) 125.112 ms 106.932 ms 124.778 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * unallocated.barefruit.co.uk (92.242.140.21) 111.898 ms *
gordons-mac-pro:~ gordoncook$

PS: my FIOS contract is up in april. Any suggestion of how to avoid a $30 per month price increase would be greatly appreciated

OFF list of course many thanks

Gordon Cook

COOK Report on Internet Protocol

Hi,

I actually saw this issue a few weeks back but with a customer's website. It's actually not a routing issue, but a DNS issue. If you check the IPs that Verizon resolves for you, they'll be different from the IPs that other resolvers will resolve.

It's weird, I know, but that's all the information I have for you.

Hope I helped,
Ammar.