I can't believe how much chat there is about this outage, and so little talk about what diagnostics showed the problem was. It was a DNS issue, NOT a general routing issue.
It hit us here in Austin TX. It looked like a DNS outage... but I was using Google DNS. Routing was NOT down... I could still access a selection of web servers by direct IP address, and ping and traceroute. Rebooted my modem and router repeatedly. Modem acquired a link quickly, and status page showed it had a valid configuration. Modem's signal strength dropped from the usual minus-8-ish to minus-6-ish dBmV. Router acquired IP and WAN domain name effortlessly.
I tried OpenDNS, Earthlink, Dell, and some other public DNS servers I have in a list, but they didn't work either. All timed out. I didn't know what TWC's DNS servers were, so I zeroed them out in my router config, then rebooted. Well, DHCP picked up TWC's DNS servers like nothing was wrong. STILL had no working DNS resolution! And I could still access websites by direct IP address. I was also still receiving mail and web traffic to my own servers, though well below usual levels. The email server was rejecting all mail though, since it couldn't verify the sender's domain names.
Exhausted, I gave up and went to bed. Everything was simply working again when I got up.
The evidence suggests that TWC decided to *filter* DNS traffic, possibly even to aggregate and reroute all of it, and they screwed the pooch. I can't think of any legitimate reason they'd need to do this. I think I'm going to go back to running my own DNS server. Not much I can do about state-redirected DNS traffic other than tunnel it through a VPN perhaps.
"an immediate, specific, and harmful impact on the national security of the United States."
Yes, and see, they measured it out to be on the order of
"This of course implies that they have no backup system — or at least that the backup are not held for long."
Unfortunately, it proves nothing. The recording systems capture EVERY byte coming along the cables and can be used to REPLAY exactly what data went between two points at any time. This means they can go back and re-examine traffic to find hidden transmissions they overlooked before. They don't throw anything out (specifically stating that they keep anything encrypted forever) and longevity is reported as anywhere from 4 days to several years of 100% of the Internet's activity. Reports vary due to being what the system was capable of at the time, probably. The UT center probably won't be full until your kids are out of diapers and graduating high school.
So, Netflix pays to have a direct line installed to Comcast, thus circumventing Comcast's backbone provider, and saving Comcast the expense of paying for all that video bandwidth. The bill is picked up by Netflix. For some refuckulous reason, Comcast wants to CHARGE Netflix for this direct-peering arrangement, and when Netflix goes "dude... whut?" Comcast starts bawling about being "forced" to provide Netflix with "free bandwidth"? Hahahhhhahahahahaa.....
See, when I walk down the street to drop a note off at my neighbor's house, I am NOT "cheating" USPS and "forcing" them to provide me with a "free" delivery. I've gone and done the damn thing myself, at my own expense, if any.
What's happened here is that Netflix found that Comcast's backbone providers could not be trusted to move data reliably and equitably. Then they went and determined that it would also be damned cheaper to just run their own line to Comcast's network as well. This contributes to a multi-pathed Internet which circumvents the grievously centralized Internet that we have now, studded with gate-keepers who do nothing but impose obstacles and demand money to overcome them. The Powers That Be cannot have this. Although the peering benefits Comcast in this case, it sets a precedent which could cost them profit in the future. By failing to rise up and sabotage this aspect of network neutrality, Comcast would receive the scowls of their monopolist peers.
Now, some versions of BASIC would evaluate each line of code you'd just input for obvious errors as soon as you hit enter to save it. It would work whether you had preceded the code with a line number or not. It would try to tell you what kind of error it thought it saw. If you had multiple syntax errors, it might frustrate the fark out of you by responding with the same error even though you'd retyped or edited the line to fix one of them. Some of them would just flash $ERR?$ or something useless at you instead.
0 cls:forx=1964to2014:?"Happy Birthday, Basic":nextx
LBASIC was very easygoing about spacing and is probably the reasonicanstilleasilyreadsentenceswithoutspaces.
The feature only failed me under one circumstance as in; 100 letcall="5982341000":ifphone<>callprint"They Don't Match!" because since "phone" would never match "cal", it would always cause "They Don't Match!" to unexpectedly come out on the line printer, scaring the shit out of ya in the process.
I say; boycott Costco peanut butter. Take multiple jars of it to the checkout counter, but then set them aside and say you aren't buying them.
140224 042320 126.96.36.199 - 188.8.131.52
140226 084433 184.108.40.206 - 220.127.116.11
140226 210354 18.104.22.168 - 22.214.171.124
140301 232858 126.96.36.199 - ns382685.ovh.net
140217 122758 188.8.131.52 - 184.108.40.206
140217 124326 220.127.116.11 - 18.104.22.168
140218 081257 22.214.171.124 - 126.96.36.199
Instead of hyperinflation expanding faster than light in the first microseconds, perhaps our Bang opened into a pre-existing "cavity" of a few light-minutes across. Perhaps we burst out of a dimple in the wall of a larger space; an ancient, nearly-collapsed universe, breathing new life into it and restarting inflation. Expansion was at purely Einsteinian speeds (is there such a term?), but an illusion was created of superluminal motion.
I've also got a theory that the acceleration of inflation is less due to mysterious 'dark energy' than to our halo of "new" matter approaching a halo of really, really old cold matter and inactive black holes that exists beyond the Hubble radius. The Great Attractor may just be a lump that is a bit closer than the rest.
Or acceleration may be due to our 3-dimensional universe passing over and through higher-dimensional topologies that are invisible to us but for their gravity. We've begun to roll downhill, for reasons of absolutely no significance, and we'll just continue to do so until things level out. The higher-dimension topologies being invisible to us, we just have to take them as we get 'em, like unexpected waves.