Community Forum

Packet loss and latency - Seattle

Highlighted
Regular Visitor

Packet loss and latency - Seattle

For the past 2 months I have been having packet loss and latency spikes throughout the day. Cables have been reconnected and tightened and the modem has been restarted a million times. There are no splitters in my unit, though I'm in an apartment and I don't know about the rest of the building. Here are my modem stats:

 

Downstream

  DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables
Downstream 1 25 615.00 MHz 5.60 dBmV 38.98 dB 256QAM 1296512101 22 0
Downstream 2 21 591.00 MHz 4.50 dBmV 38.98 dB 256QAM 1522971707 10 0
Downstream 3 22 597.00 MHz 4.50 dBmV 38.98 dB 256QAM 2062763007 8 0
Downstream 4 23 603.00 MHz 5.20 dBmV 38.61 dB 256QAM 2063734144 10 0
Downstream 5 24 609.00 MHz 5.30 dBmV 38.98 dB 256QAM 2061665928 14 0
Downstream 6 26 621.00 MHz 5.80 dBmV 38.98 dB 256QAM 2210580592 23 0
Downstream 7 27 627.00 MHz 5.90 dBmV 38.61 dB 256QAM 2214506407 16 0
Downstream 8 28 633.00 MHz 5.90 dBmV 38.98 dB 256QAM 2213247092 28 0
Downstream 9 29 639.00 MHz 6.30 dBmV 38.61 dB 256QAM 1008637118 27 0
Downstream 10 30 645.00 MHz 6.40 dBmV 38.98 dB 256QAM 1456805600 27 0
Downstream 11 31 651.00 MHz 6.10 dBmV 38.61 dB 256QAM 1457549909 20 0
Downstream 12 32 657.00 MHz 6.30 dBmV 38.61 dB 256QAM 1460199134 28 0
Downstream 13 33 663.00 MHz 6.40 dBmV 38.98 dB 256QAM 994648198 28 0
Downstream 14 34 669.00 MHz 6.40 dBmV 38.61 dB 256QAM 1940324439 15 0
Downstream 15 35 675.00 MHz 6.10 dBmV 38.61 dB 256QAM 1940604257 30 0
Downstream 16 36 681.00 MHz 6.10 dBmV 38.98 dB 256QAM 1940892214 42 0
Reset FEC Counters

Upstream

  UCID Freq Power Channel Type Symbol Rate Modulation
Upstream 1 4 36.50 MHz 42.75 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 2 3 30.10 MHz 42.75 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 3 2 23.70 MHz 44.25 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 4 1 17.30 MHz 45.75 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s

64QAM

 

Here is the error log:

 

Date Time Event ID Event Level Description
6/13/2020 0:25 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:25 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:27 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:27 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:28 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:28 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:29 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:29 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:31 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:31 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:32 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:32 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:33 82000700 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/13/2020 0:33 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/18/2020 9:13 73040100 6 TLV-11 - unrecognized OID;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/18/2020 12:00 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/18/2020 13:23 73040100 6 TLV-11 - unrecognized OID;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/20/2020 21:20 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/24/2020 16:30 73040100 6 TLV-11 - unrecognized OID;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;
6/24/2020 16:30 82000500 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:a4:d2:a1;CMTS-MAC=00:fe:c8:06:72:42;CM-QOS=1.1;CM-VER=3.0;

 

I have contacted Comcast support and they alternatively say that my connection is fine (obviously wrong, but they are probably testing at a moment when it appears fine), but I also had a rep state that my node was over capacity. That explanation seems reasonable, but they did not have any information on any upcoming maintenance or node splits, so who knows how much longer I will have to deal with this. The loss and latency spikes are concentrated on the first hop (96.120.102.65, I'm in downtown Seattle):

 

Reply from 96.120.102.65: bytes=32 time=462ms TTL=254
Reply from 96.120.102.65: bytes=32 time=29ms TTL=254
Reply from 96.120.102.65: bytes=32 time=134ms TTL=254
Request timed out.
Reply from 96.120.102.65: bytes=32 time=25ms TTL=254
Request timed out.
Request timed out.
Reply from 96.120.102.65: bytes=32 time=222ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 96.120.102.65: bytes=32 time=264ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 96.120.102.65: bytes=32 time=45ms TTL=254
Reply from 96.120.102.65: bytes=32 time=19ms TTL=254

 

I could also post PingPlotter screenshots that look like a warzone, but I don't think they will insert correctly here.

 

The periods of packet loss result in me losing connection to my work VPN throughout the day, and low latency applications such as video calls and games have been completely unusable. Any ideas on how I can actually get this fixed? Thanks.

Highlighted
Regular Visitor

Re: Packet loss and latency - Seattle

My connection has been extra terrible today so I'm following up with some PingPlotter screenshots. I'm running out of excuses to tell my employer why I can't attend calls...

 

ping.PNGping3.PNG