Routing issue?

[dehrmann]

I'm having problems accessing a few websites. Here's one (a company I used to work for) where I can't access the site, and I can't traceroute it, either.

Code: Select all

# traceroute 64.124.85.100
traceroute to 64.124.85.100 (64.124.85.100), 64 hops max, 52 byte packets
 1  10.0.0.5 (10.0.0.5)  2.042 ms  0.702 ms  1.194 ms
 2  173-228-x-x.dsl.static.sonic.net (173.228.x.1)  21.416 ms  21.939 ms  20.880 ms
 3  gig1-29.cr1.lsatca11.sonic.net (70.36.243.77)  20.652 ms  21.039 ms  21.009 ms
 4  0.xe-5-1-0.gw.pao1.sonic.net (69.12.211.1)  73.639 ms  20.298 ms  20.125 ms
 5  xe-1-0-6.ar1.pao1.us.nlayer.net (69.22.130.85)  22.154 ms  21.353 ms  21.153 ms
 6  ae0-90g.cr1.pao1.us.nlayer.net (69.22.153.18)  20.672 ms  20.995 ms  20.377 ms
 7  ge4-0.mpr2.pao1.us.mfnx.net (198.32.176.11)  20.682 ms  19.772 ms  20.188 ms
 8  * * *
 9  * * *
10  * * *
11  * * *

Edit: anonymized my IP

[dane]

Above.net has an issue affecting some of their customers, but only from some IPs. I understand it's a failing interface card in one of their core routers, and that they're working to get it resolved.

We can't route around the issue because the end sites are generally only reachable via Above.net, so sending it toward other transit providers we have just brings it back to Above.net, where the issue manifests. It's also a bi-directional problem; even if we could get outbound traffic there via another route, the inbound routing is controlled by a combination of the end site and Above.net, so it ends up lost.

No estimated time to repair at this time, but they are working on it!

[dehrmann]

Thanks for acknowledging the problem and the status update. It's always nice to know it's not just me and to not have to fight to get a straight answer.

[bbusby]

I'm on the same /16 as you, it seems and things seem better:

traceroute to 64.124.85.100 (64.124.85.100), 30 hops max, 40 byte packets using UDP
1 192.168.0.1 (192.168.0.1) 9.801 ms 15.499 ms 14.421 ms
2 192.168.1.1 (192.168.1.1) 19.368 ms 18.800 ms 18.255 ms
3 173-228-4-1.dsl.dynamic.sonic.net (173.228.4.1) 40.832 ms 41.865 ms 40.855 ms
4 gig1-2.cr1.lsatca11.sonic.net (70.36.243.5) 27.786 ms 26.629 ms 25.404 ms
5 0.xe-5-1-0.gw.pao1.sonic.net (69.12.211.1) 26.499 ms 29.218 ms 28.129 ms
6 * * *
7 ae0-90g.cr1.pao1.us.nlayer.net (69.22.153.18) 47.262 ms 46.925 ms 45.821 ms
8 ge4-0.mpr2.pao1.us.mfnx.net (198.32.176.11) 26.637 ms 26.356 ms 83.920 ms
9 * * xe-3-0-0.cr1.sjc2.us.above.net (64.125.31.66) 95.136 ms
10 xe-4-3-0.er1.sjc2.us.above.net (64.125.28.53) 76.424 ms 30.138 ms 30.010 ms
11 64.124.85.100.become.com (64.124.85.100) 28.916 ms 27.834 ms 26.996 ms

(I didn't see any reason to obscure the /24)

[dane]

We think the issue may be fully resolved at this point.

[bbusby]

or maybe not fixed just yet... just lost contact w/titantv.com

traceroute to titantv.com (66.43.219.225), 30 hops max, 40 byte packets using UDP
...
9 te0-7-0-1.ccr21.ord01.atlas.cogentco.com (154.54.2.190) 76.634 ms te0-7-0-1.ccr22.ord01.atlas.cogentco.com (154.54.6.213) 76.509 ms 76.123 ms
10 * * *
11 38.104.184.6 (38.104.184.6) 101.613 ms 100.574 ms 115.371 ms
12 ins-dc2-po20.desm.netins.net (167.142.67.33) 98.311 ms 97.224 ms 96.133 ms
13 ins-db1-et-13-1.desm.netins.net (167.142.67.26) 95.049 ms 93.949 ms 92.843 ms
14 * * *
15 * * *
16 * * *
17 * * *

I can get there from the SF house just fine, so it might be something about 173.228.4.0/24 that's fubar

[dane]

We'll give it a look!