Level 3 issues?

Nick Olsen nick at flhsi.com
Mon May 16 21:06:02 UTC 2016


Saw the same here. Legacy TW (AS4323) connection didn't take quite the hit that our Level3 (AS3356) did. But they were both seeing similar issues. Had to push traffic some specific routes toward cogent *shudder*.
  
   Nick Olsen
Sr. Network Operations  (855) FLSPEED  x106

  

----------------------------------------
 From: "David Hubbard" <dhubbard at dino.hostasaurus.com>
Sent: Monday, May 16, 2016 4:18 PM
To: "nanog at nanog.org" <nanog at nanog.org>
Subject: Re: Level 3 issues?   
I just heard from someone there is suspicion that a fiber cut occurred in FL, possibly Miami area, and it has revealed a capacity issue on the L3 network. Haven't received official word on that yet, but I know our legacy TWTC connection is nearly as useless as our L3 connection thanks to the network merging activities.

David

On 5/16/16, 4:10 PM, "Jordan Medlen" <jordan-medlen at bisk.com> wrote:

>Have been seeing issues since just after 3P. Had to swing my traffic over to another provider. Level3 says issues seen from Costa Rica on up to WDC.
>
>
>Thank you,
>
>Jordan Medlen
>Enterprise Communications Manager
>Bisk Education
>(813) 612-6207
>
> <http://www.bisk.com/>
>
>On 5/16/16, 3:49 PM, "NANOG on behalf of David Hubbard" <nanog-bounces at nanog.org on behalf of dhubbard at dino.hostasaurus.com> wrote:
>
>>Anyone seeing issues with Level 3 networking right now? We're seeing huge latency and loss on traffic coming inbound (to us, AS33260) but it seems to be at the peering points with other major ISP's and Level 3. Comcast for example:
>>
>> 3 33 ms 21 ms 70 ms te-3-5-ur01.hershey.pa.pitt.comcast.net [68.85.42.29]
>> 4 * 33 ms 106 ms 162.151.48.173
>> 5 214 ms 54 ms 41 ms 162.151.21.229
>> 6 561 ms 764 ms 459 ms 4.68.71.133
>>
>>Thanks,
>>
>>David
>
 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Attachment 1
Type: application/octet-stream
Size: 1355 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20160516/d4dae763/attachment.obj>


More information about the NANOG mailing list