Anyone else seeing problems reaching AT&T/XO possibly others from
AS6453 in Europe?
From mclink.it (195.110.152.67), I see the following:
[12-97-129-192:~] owen% traceroute 140.239.191.10
traceroute to 140.239.191.10 (140.239.191.10), 64 hops max, 52 byte packets
1 192.168.15.254 (192.168.15.254) 4.837 ms 4.359 ms 4.323 ms
2 192.168.250.1 (192.168.250.1) 4.593 ms 4.639 ms 4.561 ms
3 net152-001.mclink.it (195.110.152.1) 6.156 ms 6.119 ms 6.580 ms
4 213.21.129.56 (213.21.129.56) 32.659 ms 33.747 ms 32.600 ms
5 gw2-rm-te1.aknet.it (213.21.130.130) 32.604 ms 32.650 ms 33.107 ms
6 if-0-0-4.core1.rct-rome.as6453.net (195.219.163.33) 33.061 ms 33.313 ms 32.227 ms
7 if-7-0.core3.mlt-milan.as6453.net (195.219.158.49) 41.857 ms 41.912 ms 42.275 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
This is consistent for several other sites in net 12/8 and some others as well.
The common denominator appears to be trying to get to XO or AT&T and
dying at hop 7 as above.
Anyone else seeing problems reaching AT&T/XO possibly others from
AS6453 in Europe?
Seems to work okay from Norway:
traceroute to 140.239.191.10 (140.239.191.10), 64 hops max, 40 byte packets
1 ge0-0-0-3000.br1.fn3.no.catchbone.net (193.75.4.1) 0.165 ms 0.179 ms 0.235 ms
2 if-6-0-0.core2.OS1-Oslo.as6453.net (80.231.89.13) 0.357 ms 0.222 ms 0.237 ms
3 if-5-0-0.core1.AD1-Amsterdam.as6453.net (80.231.80.33) 25.598 ms 25.583 ms 25.605 ms
4 if-0-0.core2.AD1-Amsterdam.as6453.net (80.231.80.14) 25.710 ms 25.570 ms 25.598 ms
5 if-15-0-0.core3.NTO-NewYork.as6453.net (80.231.81.46) 147.779 ms 111.782 ms 111.807 ms
6 63.243.186.66 (63.243.186.66) 121.642 ms * 115.188 ms
7 ix-2-12.icore1.NTO-NewYork.as6453.net (209.58.26.70) 104.279 ms 103.886 ms 142.532 ms
8 vb2001.rar3.washington-dc.us.xo.net (207.88.13.50) 119.407 ms 130.336 ms 119.065 ms
9 te-3-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.9) 172.006 ms 171.869 ms 171.997 ms
10 te-3-0-0.rar3.dallas-tx.us.xo.net (207.88.12.2) 172.136 ms 172.233 ms 172.256 ms
11 vb12.rar3.la-ca.us.xo.net (207.88.12.46) 171.863 ms 172.112 ms 171.890 ms
12 ae0d0.mcr1.la-ca.us.xo.net (216.156.0.114) 171.490 ms 171.477 ms 171.505 ms
13 207.88.81.198.ptr.us.xo.net (207.88.81.198) 173.491 ms 256.940 ms 173.369 ms
14 ip65-47-242-10.z242-47-65.customer.algx.net (65.47.242.10) 179.122 ms 179.613 ms 179.397 ms
15 140-239-191-10.dsis.net (140.239.191.10) 188.329 ms 192.338 ms 188.615 ms
Yes, I was able to reach Tata (they actually have done something very good I encourage
others to follow, see below) and they resolved the issue within 15 minutes of my phone
call.
What Tata has done with as6453.net is that there is a website there which provides
NOC contact info and the phone is answered by semi-clueful people who upon realizing
that the caller is clueful and has an actual legitimate problem are able to rapidly transfer
to clueful people with the ability to fix things.
I applaud Tata for:
1. Making their NOC contact info easy to find from traceroutes. It should have
occurred to me to try www.as6453.net first, but, instead I went digging through
whois and when that proved fruitless, tapped NANOG. My bad.
2. Having people answer the phone (promptly) who are able to do the right
thing with the phone call.
3. Having engineers readily available for calls that are escalated immediately.