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

DirtyPeanut

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	%	Sent	Recv	Best	Avrg	Wrst	Last
Wireless_Broadband_Router.home	1	1069	1068	0	0	1	0
L100.LSANCA-VFTTP-112.verizon-gni.net	3	1069	1041	4	8	99	7
G0-6-1-2.LSANCA-LCR-22.verizon-gni.net	3	1069	1044	6	11	134	22
ae4-0.LAX01-BB-RTR2.verizon-gni.net	4	1069	1032	7	15	126	44
0.xe-7-1-0.XL4.LAX15.ALTER.NET	3	1069	1038	8	15	109	12
0.xe-11-2-0.XL4.LAX1.ALTER.NET	4	1069	1034	8	15	115	10
0.xe-11-0-0.GW2.LAX1.ALTER.NET	5	1069	1024	7	16	108	14
customer.alter.net.customer.alter.net	75	1069	277	356	362	488	361
te-2-0-0-13-cr01.losangeles.ca.ibone.comcast.net	33	1069	718	357	364	479	366
pos-0-2-0-0-pe01.600wseventh.ca.ibone.comcast.net	71	1069	320	357	363	452	363
173.167.58.18	37	1068	682	358	363	466	364
10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net	67	1068	355	369	375	467	375
lax16.multiplay.co.uk	40	1068	641	365	371	495	371

smith6612

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.