North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Anyone seeing Level3 issues in Dallas ?

  • From: Jason Seemann
  • Date: Fri Jul 20 16:03:34 2007
  • Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PG3RNqezNwm3VBBs6EEA9k5rzZ/Y8UdYv7IChwR2Hh9zX7VM0O8BAQRFAMR2zqna8NzLUYZBovyGcZTr7IjqAsPJw8vhOWj7/BaYS5hn8pNZwlGrVh8nzMdtjhz+4LBOZiUd+FADDxBHyeQ7vJZL22nJyJccKOKSF/hVSi7XO58=
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=CyBMjzndfEDAEX9HRHx23C1iRCW7tgeYcUuLt3uk34n+AgOKQl+l/a2V75Ciw/FzAgweTmxcjqj9R6Jt6aZwqxRza/IX9EDJ6EdxDjk2yLa5diTEGqhiIcz+gOV2vp5C/g0cUKSkDmuuyDJzyy1xkGIAGiltT6/0lXZxTylvrmg=
Our representative told us they had a massive fiber cut in the Dallas metro area that affected a number of connections.

Jason


On 7/20/07, W. Kevin Hunt <[email protected]> wrote:

Yeah, this morning Broadwing/L3 had yet another failure, and it took them
hours to figure out what the hell was wrong.


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Scott Francis
Sent: Friday, July 20, 2007 11:39 AM
To: W. Kevin Hunt
Cc: [email protected]
Subject: Re: Anyone seeing Level3 issues in Dallas ?


panther reports issues between L3 and e.g. Savvis, GBLX, PCCW and
others in the LAX/SFO area (we're having performance issues with some
of their CDN nodes in those areas right now). Possibly more widespread
than just California ...
--
[email protected]{gmail.com,darkuncle.net} || 0x5537F527
    encrypted email to the latter address please
     http://darkuncle.net/pubkey.asc for public key

On 7/19/07, W. Kevin Hunt <[email protected]> wrote:
>
> All my traces die one hop into Broadwing/L3 Dallas.
> After noticing it, I killed my peer w/ them, and still had issues
> getting to anyone I know prefers L3 for peering.
> I turned it back up when I saw some L3 destinations working via TW
[snip]