11–20 of 49 posts
I am still unable to reach any of the above sites/networks via my Time Warner Cable connection, though.
While most of these services have now been rerouted via Above Net etc, some ISPs such as Time Warner (in NY at least) still seem to be routing via Level3 and unable to get to a lot of destinations.
Time Warner always seems slow to re-route. T-Mobile is having the same issue.
Too funny -- I diagnosed this to L3 on my home net this morning and I found myself saying "I wonder if anyone else has this issue?". When it comes to the backbone providers there is no Twitter account or status.level3.net or status.theinternet. Hard to do when everything is decentralized. I usually go hit NANOG when stuff like this happens but you're not guaranteed to find something real time there.
Not sure what was going on there, I wish I did, but seems to be related?
Edit: that was going to an nyc digital ocean VPS
Earlier quoted context omitted.
Time Warner always seems slow to re-route. T-Mobile is having the same issue.
Because Time Warner sucks.
Earlier quoted context omitted.
Because Time Warner sucks.
Confirm. Woke up this morning to limited connectivity, realised I was getting to some sites and not others. While on hold with TWC (where they said there was an 'outage affecting service in your area'), loaded HN to see if, well, HN would load, and this was the #3 story. Thanks HN, GFY TWC!
Tracing route to debian.org [128.31.0.51]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 42 ms 28 ms 28 ms cpe-74-73-128-1.nyc.res.rr.com [74.73.128.1]
3 14 ms 13 ms 12 ms gig-0-2-0-3-nycmnya-rtr1.nyc.rr.com [24.29.98.1]
4 12 ms 15 ms 15 ms 184.152.112.105
5 17 ms 15 ms 15 ms ae-3-0.cr0.nyc20.tbone.rr.com [66.109.6.76]
6 13 ms 12 ms 15 ms 107.14.17.169
7 15 ms 12 ms 13 ms xe-4-2-0.edge4.frankfurt1.level3.net [4.68.63.121]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.These issues have been around for at least a couple of weeks now. I too have been monitoring Internet Pulse and what I see is not only Level 3 puking on a regular basis but several of the other backbones also. Quite honestly, it's either a gross lack of competence or the feds are beginning to condition the net as they are in the military. ~Ginn
Too funny -- I diagnosed this to L3 on my home net this morning and I found myself saying "I wonder if anyone else has this issue?". When it comes to the backbone providers there is no Twitter account or status.level3.net or status.theinternet. Hard to do when everything is decentralized. I usually go hit NANOG when stuff like this happens but you're not guaranteed to find something real time there.