Ok fine I'll be the first one to say it... Is it just me (and I know it isn't :P) or did, well, all of Sprint decide to take a puke from 12:30AM EDT till around 1AM EDT? Simultanious with a significant failure to route AOL from a large number of networks... -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
The sprint outage list announced a lot of work being done in planned maintenance window. Aparrently sombody did an 'oops'. Purpose for maintenance: Network buildout/enhancement Maintenance date: 07/24/2000 Maintenance start time: 00:01 AM EDT Estimated end time: 07:00 AM EDT Duration: 6 hours within the maintenance window. Details of maintenance: Upgrade IOS code to newer version (12.0(10)S5). ----- Original Message ----- From: "Richard A. Steenbergen" <ras@e-gerbil.net> To: <nanog@merit.edu> Sent: Wednesday, July 19, 2000 9:32 PM Subject: Sprint/AOL
Ok fine I'll be the first one to say it... Is it just me (and I know it isn't :P) or did, well, all of Sprint decide to take a puke from 12:30AM EDT till around 1AM EDT?
Simultanious with a significant failure to route AOL from a large number of networks...
-- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
On Tue, 21 Mar 2000, David A. Snodgrass wrote:
The sprint outage list announced a lot of work being done in planned maintenance window. Aparrently sombody did an 'oops'.
Purpose for maintenance: Network buildout/enhancement
Maintenance date: 07/24/2000 ^^^^^^^^^^^^^^^^ Maintenance start time: 00:01 AM EDT Estimated end time: 07:00 AM EDT
I got that notice and thought maybe that was it too, until I noticed the date was a few days in the future...so I called an opened a ticket. First person I talked to played dumb (ok...maybe they didn't have to play) and said she knew of no backbone problems. If I shut down my BGP session with Sprint, and 10 minutes later, they're still propogating my route advertisements, and routing in loops, and not routing at all in some cases, I think that's a problem. About an hour later they seemed to have mostly stabilized, so I called back to tell them, "don't call me, I'll call you" and was told that "something had happened" that had forced them to reset a whole bunch of their routers. The guy made it sound as if some customer/peer might have sent Sprint a lot of routes they weren't supposed to have. ---------------------------------------------------------------------- Jon Lewis *jlewis@lewis.org*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
On Thu, 20 Jul 2000, Richard A. Steenbergen wrote:
Ok fine I'll be the first one to say it... Is it just me (and I know it isn't :P) or did, well, all of Sprint decide to take a puke from 12:30AM EDT till around 1AM EDT?
At exactly 22:21:31 PDT our sprint bgp routes exploded. Looks like someone at sprint broke their route filters, again. No official word from sprint, I have a ticket open with them. -Dan
participants (4)
-
Dan Hollis -
David A. Snodgrass -
jlewis＠lewis.org -
Richard A. Steenbergen