>From here it looks like a problem around NTT/Level3 handoff. Relevant snippit from mtr going from our colo to our Comcast business line...
6. ae-11.r00.lsanca07.us.bb.gin.ntt.net 0.0% 128 71.8 71.8 71.7 72.3 0.1 7. ae-2.r23.lsanca07.us.bb.gin.ntt.net 0.0% 128 10.2 10.7 10.1 19.0 1.4 8. ae-6.r22.asbnva02.us.bb.gin.ntt.net 11.7% 128 75.2 75.4 75.0 81.0 1.0 9. ae-1.r05.asbnva02.us.bb.gin.ntt.net 0.0% 128 71.0 71.1 71.0 71.6 0.2 10. ae-0.a02.asbnva02.us.bb.gin.ntt.net 18.9% 128 70.3 71.7 69.8 102.5 5.2 11. lag-12.ear2.Washington12.Level3.net 99.2% 127 7085. 7085. 7085. 7085. 0.0 12. ae-1-3501.ear3.SanJose1.Level3.net 97.6% 127 19439 19547 18857 20346 750.4 13. ComcastRegional-level3-200G.SanJose1.Level3.net 51.6% 127 191.5 195.1 184.5 204.8 3.5 On Mon, Nov 6, 2017 at 10:32 AM, jstefanik Outages via Outages < outages@outages.org> wrote: > Meant to send this to the whole list. Sorry! > > > I’m seeing a few reports via Twitter that Level3 is having issues. > DownDetector shows a massive number of sites with high latency on their > home page as well. Our Comcast link in Hartford, CT is going nowhere. Pings > are off the charts and packet loss is quite high. > > > > Jim > > > > Sent from my iPhone 7 Plus > > > > On 6 Nov 2017, at 13:25, Nate Schmoll via Outages <outages@outages.org> > wrote: > > > >>> anyone else is seeing lots of packet loss and 100ms+ latency mostly in > east coast on comcast network? > >> > >> Experiencing the same thing here in Everett, WA, US. > >> > >> ~Nate > >> _______________________________________________ > >> Outages mailing list > >> Outages@outages.org > >> https://puck.nether.net/mailman/listinfo/outages > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages >
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages