[38955] in North American Network Operators' Group
RE: BGP instability (was Re: Exodus Down)
daemon@ATHENA.MIT.EDU (Vivien M.)
Sat Jun 23 22:49:28 2001
From: "Vivien M." <vivienm@dyndns.org>
To: <nanog@merit.edu>
Date: Sat, 23 Jun 2001 22:49:21 -0400
Message-ID: <NDBBKECCEHKIHGIMJECAGEOPCJAA.vivienm@dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20010624024026.8934.cpmta@c004.sfo.cp.net>
Errors-To: owner-nanog-outgoing@merit.edu
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Sean Donelan
> Sent: June 23, 2001 10:40 PM
> To: nanog@merit.edu
> Subject: BGP instability (was Re: Exodus Down)
>
>
>
> According to Exodus' trouble ticket it is a BGP instability between
> several locations in their network and with BGP customers.
Hmmmmm... You somehow found a way to get this information without agreeing
to the NDA? Impressive. (For the people around here who aren't Exodus
customers: subscribing to their network engineering/outage list
theoretically implies agreeing to an NDA, which is presumably why no one
here mentioned this)
That's a minor thing, though. More importantly:
a) Slashdot and co went down way before this Exodus BGP business
b) Slashdot and friends seem very singlehomed to me (and using Exodus IP
space, too), so I don't see why they'd be speaking BGP to Exodus
c) Some very specific areas of Exodus' network are affected, not wlhm01.
d) Slashdot and co's _network_ seemed up fine... at least some of it. Right
now, interestingly enough, that doesn't seem to be the case.
Thus, I don't see the link between the Exodus BGP thing and the
Slashdot/Freshmeat/etc. outage.
Vivien
--
Vivien M.
vivienm@dyndns.org
Assistant System Administrator
Dynamic DNS Network Services
http://www.dyndns.org/
