The problem seems to be site limiting, rather than network limiting. i.e., news sites are being overloaded, which is causing slow or no response to http queries due to either server overload (my guess) or news site transit link overload (also possible). This is what seems to be causing lacking of response to news sites, instead of generalized network or peering congestion. It doesn't help that it looks like CNN decided to turn off the "akamization" of their content. This had the immediate effect of helping them get the news up on their site faster, but the lack of Flash Crowd protection really hurt them in the long run. It is definately a Flash Crowd day. :( - Daniel Golding -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of deeann mikula Sent: Tuesday, September 11, 2001 10:22 AM To: Charles Sprickman Cc: Avi Freedman; nanog@merit.edu Subject: Re: Horrible world trade center crash, traffic effect On Tue, 11 Sep 2001, Charles Sprickman wrote:
On Tue, 11 Sep 2001, Avi Freedman wrote:
FYI, 2 planes crashed into the world trade center. Sounds like on purpose.
Not to be ghoulish, but the traffic impact is looking to be fairly large on the 'net (and on the PSTN in the NYC area).
few people (in pgh, PA) that i have been talking to on irc have reported ./'d news sites everywhere. (cnn.com, yahoo.com, msnbc.com, etc.) my office has been relegated am radio, which is pretty pathetic for an ISP. pretty poor performance for a network orginally designed to faciliate communication in just such circumstances. i hope that military and federal communication is faring better than the commercial sites.
All VHF TV stations except for CBS 2 are off the air, many radio stations are off the air, and it's largely impossible to get a call in. All
i assume that in nyc or dc only. we are listening to AM radio just fine... deeann m.m. mikula director of operations telerama public access internet http://www.telerama.com 1.877.688.3200