The air line reservation system Galileo had significant problems
earlier.
Excerpt from Reuters:
"The outage began about 8:30 p.m. Mountain Daylight Time on Wednesday
and lasted until 10:55 a.m. MDT on Thursday, said Beth Tennis, vice
present of enterprise networks for Quantitude, Galileo's Denver-based
networking subsidiary. It affected three of the four T-1 high-speed
data transmission lines supplied to Galileo by AT&T Corp., said
Beth Tennis"
4 T1's were down in Denver? Stop the world, I want off. 
You missed the bigger story about the AOL Instant Messanger outtage for a
large portion of the day (which I heard lots about from all my AIM loving
friends). Doubtless many thousands of network engineers were cut off from
their vital lines of communication.
Although I've found AT&T has the highest reliability of all the carriers
I've used. Redundant links from the same carrier frequently have a
Personally I've found AT&T to be a packet motel, packets go in but they
don't come out... To each their own...
Today was the second multi-hour outage in the past week of AIM
that i'm aware of.
- Jared
Quick everyone install MSN for redundancy.
The service interruption was apparently a result of a major regional power failure in Northern Virginia. I'm curious whether it was AOL or their providers who suffered from the power failure. I would expect AOL would have back-up power.
http://www.techtv.com/news/internet/story/0,24195,3320700,00.html
jas
John Starta wrote:
The service interruption was apparently a result of a major regional
power failure in Northern Virginia. I'm curious whether it was AOL or
their providers who suffered from the power failure. I would expect
AOL would have back-up power.
http://www.techtv.com/news/internet/story/0,24195,3320700,00.html
Something's fishy about this.
I'm in Northern Virginia (Vienna), not 15 miles from AOL's facilities
(in Reston and Dulles). I experienced no power outage that day. So if
there was a failure, it was certainly not "major regional".
During the outage, the AIM client would successfully connect, but would
abort with a database error trying to validate passwords. Sounds more
like a servier failure to me. (Although to be fair, my first test was
less than 30 minutes before the service came back, so I may have been
seeing their reboot sequence.)
-- David