Ya gotta love em .... ---------- Forwarded message ---------- Date: Wed, 23 Aug 2000 19:53:06 -0400 From: "Rippe, Mark" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: NSI Outage This is a *MAJOR, MAJOR* incident. Major enough that fixing it may well by my last official act here. And it is our problem. The Registry was alerted to this at 6:30pm EST. (I don't know who Sam O'Brian is, but I'll find out, because it sounds like someone alerted him a lot earlier.) Immediate action was taken to resolve the problem. As of now: 1. b.root is OK (I don't yet know how long it was bad) 2. g.root is OK (It was bad from about 5:15EST until 7:00EST) 3. j.root is OK (It was bad from about 6:23EST until 7:00EST) 4. m.root is still bad (We're trying to contact the operator in Japan) We're still working on root cause. I apologize for how non-technical this is. I'll have an engineer post all the technical details when we have them. The Registry Command Center does not monitor this mail list, so I was not alerted to this thread. They do, however, monitor NANOG, and there has yet been no posting there. Mark Rippe VP Registry Technical Operations -----Original Message----- From: JandL [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 23, 2000 6:18 PM To: [EMAIL PROTECTED] Subject: Re: NSI Outage Major understatment. :) :( > So we noticed today that "*.com" is boned on four of the > root-servers... This is the message we just got internally on the > topic: > > >Sam OBrian of NSI rang me back. He is currently contacting ops folk. We > >confirmed that {b,g,j,m}.root-servers.net have no NS-set for com. That is, > >"*.com" does not exist for more than a quarter of the world. He feels this > >is "not a major incident. This is a minor incident." > > Sigh. > > I have to ask the NSI folks here... what WOULD you consider a major > incident? > > D
