70%+ Packet Loss at alter.net (LA) Past Two Nights
DirtyPeanut
Newbie

I've been experiencing severe packet loss for a route to my server. Severe packet loss's observed at customer.alter.net.customer.alter.net. See below WinMTR report:

WinMTR statistics
Host%SentRecvBestAvrgWrstLast
Wireless_Broadband_Router.home1106910680010
L100.LSANCA-VFTTP-112.verizon-gni.net31069104148997
G0-6-1-2.LSANCA-LCR-22.verizon-gni.net31069104461113422
ae4-0.LAX01-BB-RTR2.verizon-gni.net41069103271512644
0.xe-7-1-0.XL4.LAX15.ALTER.NET31069103881510912
0.xe-11-2-0.XL4.LAX1.ALTER.NET41069103481511510
0.xe-11-0-0.GW2.LAX1.ALTER.NET51069102471610814
customer.alter.net.customer.alter.net751069277356362488361
te-2-0-0-13-cr01.losangeles.ca.ibone.comcast.net331069718357364479366
pos-0-2-0-0-pe01.600wseventh.ca.ibone.comcast.net711069320357363452363
173.167.58.18371068682358363466364
10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net671068355369375467375
lax16.multiplay.co.uk401068641365371495371
0 Likes
Re: 70%+ Packet Loss at alter.net (LA) Past Two Nights
smith6612
Community Leader
Community Leader

It looks like you have some loss being carried over first from what could be a local issue, but you also have a nasty issue with the border gateway between Verizon and Comcast. Are the traces still that bad looking when you try a site that doesn't hit Comcast's network in any way?

Also if you're on Wireless, go Wired while running the traces just to ensure that's not in the mix. I trust that the local network is working fine and the 1% loss is simply the way WinMTR calculates data when you stop it suddenly, since 0-1ms latency is common with Wired connections only.

0 Likes