05/16/2016 20:05:29 GMT - The IP NOC reports IP services are being impacted by a suspected fiber cut in Miami, FL. The Transport NOC is actively investigating the suspected fiber cut in coordination with Field Services. The IP NOC is working to locate alternate routes for traffic to expedite restoral while the fiber cut is addressed. Thanks, Jason Walter From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Chris Cariffe via Outages Sent: Monday, May 16, 2016 4:13 PM To: outages@outages.org Subject: Re: [outages] Level 3 in FL was brief... 4 18 ms 22 ms 15 ms xe-3-0-3-0-sur06.pompanobeach.fl.pompano.comcast.net<http://xe-3-0-3-0-sur06.pompanobeach.fl.pompano.comcast.net> [68.86.163.57] 5 16 ms 14 ms 14 ms te-0-4-0-2-ar01.pompanobeach.fl.pompano.comcast.net<http://te-0-4-0-2-ar01.pompanobeach.fl.pompano.comcast.net> [162.151.2.177] 6 21 ms 19 ms 19 ms ae14.edge4.miami1.level3.net<http://ae14.edge4.miami1.level3.net> [4.68.62.129] 7 604 ms 593 ms 605 ms ae-1-5.bar1.sanfrancisco1.level3.net<http://ae-1-5.bar1.sanfrancisco1.level3.net> [4.69.140.149] 8 589 ms * 588 ms ae-1-5.bar1.sanfrancisco1.level3.net<http://ae-1-5.bar1.sanfrancisco1.level3.net> [4.69.140.149] 4 17 ms 11 ms 27 ms xe-3-0-3-0-sur06.pompanobeach.fl.pompano.comcast.net<http://xe-3-0-3-0-sur06.pompanobeach.fl.pompano.comcast.net> [68.86.163.57] 5 16 ms 26 ms 15 ms te-0-4-0-2-ar01.pompanobeach.fl.pompano.comcast.net<http://te-0-4-0-2-ar01.pompanobeach.fl.pompano.comcast.net> [162.151.2.177] 6 14 ms 19 ms 18 ms ae14.edge4.miami1.level3.net<http://ae14.edge4.miami1.level3.net> [4.68.62.129] 7 97 ms 90 ms 97 ms ae-1-5.bar1.sanfrancisco1.level3.net<http://ae-1-5.bar1.sanfrancisco1.level3.net> [4.69.140.149] 8 97 ms 89 ms 89 ms ae-1-5.bar1.sanfrancisco1.level3.net<http://ae-1-5.bar1.sanfrancisco1.level3.net> [4.69.140.149] On Mon, May 16, 2016 at 3:56 PM, Dan Wood via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: We are also seeing an issue in Tampa. 4.69.137.117 - Tampa1.Level3.net<http://Tampa1.Level3.net>, seems like the broken spoke in the wheel. On Mon, May 16, 2016 at 3:50 PM, David Hubbard via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: Experiencing the same nightmare here, in Tampa. However, customers reporting issues nationwide, here’s part of a trace from Philly Comcast to us where it dies at L3 peering point: 3 33 ms 21 ms 70 ms te-3-5-ur01.hershey.pa.pitt.comcast.net<http://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 From: Outages <outages-bounces@outages.org<mailto:outages-bounces@outages.org>> on behalf of "Mr. NPP via Outages" <outages@outages.org<mailto:outages@outages.org>> Reply-To: "Mr. NPP" <mr.npp@nopatentpending.com<mailto:mr.npp@nopatentpending.com>> Date: Monday, May 16, 2016 at 3:47 PM To: outages <outages@outages.org<mailto:outages@outages.org>> Subject: [outages] Level 3 in FL we are getting reports from multiple customers mostly comcast that connectivity through level 3 is full of packet loss. anyone seeing anything? thanks _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages