[36954] in North American Network Operators' Group
RE: cerf/att.net peering and or transit issues?
daemon@ATHENA.MIT.EDU (Daniel Golding)
Thu Apr 26 18:51:30 2001
From: "Daniel Golding" <dan@netrail.net>
To: "Sean Donelan" <sean@donelan.com>, <jade.deane@HelloNetwork.com>
Cc: <nanog@merit.edu>
Date: Thu, 26 Apr 2001 18:47:41 -0400
Message-ID: <FHEBKELAPEKHCBCFIEBBCEMBCCAA.dan@netrail.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20010426222349.3634.cpmta@c004.sfo.cp.net>
Errors-To: owner-nanog-outgoing@merit.edu
This was (and is) a major Broadwing fiber cut.
- Daniel Golding
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Sean Donelan
> Sent: Thursday, April 26, 2001 6:24 PM
> To: jade.deane@HelloNetwork.com
> Cc: nanog@merit.edu
> Subject: Re: cerf/att.net peering and or transit issues?
>
>
>
> There was a fiber cut about that time, which may be affecting
> routing and transit in various cross-country networks.
>
>
> On Thu, 26 April 2001, "Jade E. Deane" wrote:
> > Anyone experiencing issues transiting or peering with legacy cerf.net?
> >
> > Started noticing issues around 2:30pm PDT
> >
> > Jade
> >
> > Jade E. Deane
> > Sr. Network Engineer
> > helloNetwork
> > Las Vegas, Nevada
>
>
>
