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!
You just described my morning. Opened HN right after this:
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.
Time Warner asked me to give them the milliseconds of a working website traceroute, instead of the broken link to a non-working website! It's hilarious (and quite sad) how incompetent Time Warner is.
