Looks like Level3 at this point, not Qwest. Some traffic wasn't getting to us, which caused the dip in our outbound. It lasted about an hour.
On Mon, Apr 27, 2009 at 3:01 PM, Greg Schwimer <gsch...@gmail.com> wrote: > I lost about 500Mbps of my outbound through Qwest. Not sure why yet. > > > On Mon, Apr 27, 2009 at 2:31 PM, Paul Jasa <pj...@univision.net> wrote: > >> Confirming outages in SoCal area affecting AT&T (lost a large circuit >> out there @ 1:24 PDT). I should add not all SoCal sites are affected, >> just some. >> Paul J. >> >> >> >> >> -----Original Message----- >> From: James Laszko [mailto:ja...@pcipros.com] >> Sent: Monday, April 27, 2009 5:20 PM >> To: Kevin Loch; Ray Sanders >> Cc: outa...@outages.org; nanog >> Subject: RE: Phoenix Area Network Issues? >> >> Just got off the phone with AT&T MIS Support - there is some extremely >> large facility outages in the Southern California area. I'm seeing >> T1-OC3 facilities down from San Diego to Los Angeles to Riverside to >> Palm Springs. >> >> We've seen voice, data, legacy AT&T and legacy SBC/PacBell circuits >> affected. >> >> If anyone has any further details, it would be appreciated. MIS people >> said an "email was forthcoming shortly" >> >> >> Regards, >> >> >> James Laszko >> Pipeline Communications >> ja...@pcipros.com >> >> >> -----Original Message----- >> From: Kevin Loch [mailto:kl...@kl.net] >> Sent: Monday, April 27, 2009 2:12 PM >> To: Ray Sanders >> Cc: outa...@outages.org; nanog >> Subject: Re: Phoenix Area Network Issues? >> >> Something is definately happening, 50% drop in inbound >> traffic to our PHX datacenter across all transit providers. >> >> - Kevin >> >> Ray Sanders wrote: >> > Are there any fiber cuts or other routing issues anyone in the Phoenix >> > area is aware of? >> > >> > >> > Thanks. >> > >> >> >> >> >> The information contained in this e-mail and any attached >> documents may be privileged, confidential and protected from >> disclosure. If you are not the intended recipient you may not >> read, copy, distribute or use this information. If you have >> received this communication in error, please notify the sender >> immediately by replying to this message and then delete it >> from your system >> >> >
