ContributionsMost RecentMost LikesSolutionsTerrible Packet Loss at Peak Hours. I have Terrible Packet Loss during peak hours every day. This makes playing games nearly impossible and leads to more buffering than playing when watching videos at some points. There is clearly too much congestion in our neighborhood. This has been going on for nearly 2 years, and I've been telling myself that it's hardware issues, but the fact that it only happens during peak hours, and has been doing this on and "off" for two years has just confirmed this. How can I get a technician to come to our neighborhood and address this??? Terrible Packet Loss Spikes Terrible packet loss spikes every 10-20 minutes 20-60% Errors on Modem Time Priority Code Message Sep 16 2019 12:48:56 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 16 2019 10:03:18 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 16 2019 10:02:32 5-Warning T202.0 Lost MDD Timeout;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 16 2019 10:02:32 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 16 2019 10:01:12 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 16:44:37 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 16:44:37 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:18 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 16:17:59 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 16:17:59 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:18 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 04:50:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 04:50:06 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 04:48:46 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 13 2019 04:48:46 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 12 2019 06:45:20 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 12 2019 06:45:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 12 2019 06:45:15 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 11 2019 02:10:28 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Sep 11 2019 02:10:28 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Downstream Bonding Channel Value Channel ID 12 9 10 11 13 14 15 16 Frequency 849000000 Hz 831000000 Hz 837000000 Hz 843000000 Hz 855000000 Hz 861000000 Hz 867000000 Hz 873000000 Hz Signal to Noise Ratio 35 dB 35 dB 35 dB 35 dB 35 dB 35 dB 35 dB 35 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading -10 dBmV -10 dBmV -10 dBmV -10 dBmV -10 dBmV -10 dBmV -10 dBmV -10 dBmV Upstream Bonding Channel Value Channel ID 3 4 2 1 Frequency 30400000 Hz 36800000 Hz 24000000 Hz 17600000 Hz Ranging Service ID 1837 1837 1837 1837 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec Power Level 43 dBmV 43 dBmV 41 dBmV 39 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM Ranging Status Success Success Success Success Signal Status (Codewords) Bonding Channel Value Channel ID 12 9 10 11 13 14 15 16 Total Unerrored Codewords 10981401229 11854123422 10583887115 11854106392 11854089241 11854095652 11854092332 11854093555 Total Correctable Codewords 103059 3707 132361 12557 1049 820 1023 651 Total Uncorrectable Codewords 180511 1386 438125 1395 1544 1500 1402 1551 Internet is much slower on the Download and Upload. Usually i get 100/10 but rn i'm getting 30/5 it's super slow and I can't send clips to my team. Here's the modem signals Jan 28 2019 05:46:26 6-Notice D106.0 DHCP Renew - lease parameters tftp file-^1/20D117C6/141/001 modified;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 24 2019 10:45:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 21 2019 05:46:26 6-Notice D106.0 DHCP Renew - lease parameters tftp file-^1/20D117C6/141/001 modified;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 18 2019 08:15:20 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 17 2019 17:46:25 6-Notice D106.0 DHCP Renew - lease parameters tftp file-^1/20D117C6/141/001 modified;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:32:39 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:31:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:19:24 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:19:24 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:19:04 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:19:04 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 06:18:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:56:47 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:56:46 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:56:27 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:56:27 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:55:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:34:09 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:34:09 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 12 2019 05:33:49 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Re: Packet loss in Fortnite and Twitch/Youtube Live Streaming Very UNSTABLE How exactly did you fix this, I have this issue as well. Re: Cox Packet Loss ever since the GIGABLAST update came (100/10) plan. So the issue is on your side, but I have to keep wasting my time to fix it? Re: Cox Packet Loss ever since the GIGABLAST update came (100/10) plan. No the issue is not the router I have tried to run it directly to the modem and get the same issue Re: Cox Packet Loss ever since the GIGABLAST update came (100/10) plan. I've been getting these errors for a long time Dec 05 2018 07:47:17 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 05 2018 07:30:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 05 2018 07:29:17 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 05 2018 07:19:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 05 2018 07:18:57 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 02 2018 13:44:43 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 02 2018 13:44:43 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Dec 02 2018 13:38:51 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Dec 02 2018 13:38:51 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Dec 01 2018 13:02:00 6-Notice D106.0 DHCP Renew - lease parameters tftp file-^1/00077A1F/141/001 modified;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Nov 20 2018 16:01:48 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Nov 17 2018 13:02:01 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Nov 17 2018 13:02:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot from SNMP ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Nov 17 2018 12:57:01 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Nov 17 2018 12:57:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0; Cox Packet Loss ever since the GIGABLAST update came (100/10) plan. I've had packet loss for 3 months now and the only thing I see correlated to most people with the same issue of me isthe big updates they did with Gigablast. How can i get a technician who actually knows things about internet to fix this instead of one of these technicians who just do a bunch of simple random stuff that clearly won't do anything! Re: Packet Loss Southern California (Fortnite) I know it is on Cox's end because the issue goes away when I got to a verizon hotspot. I have friends who live miles away, and have no issues in their neighborhood. I also have friends who live miles away who have horrible packet loss, including myself. We all have nearly the same configurations. You are trying to tell me that an issue that developed at the same time among strictly Cox users, causing major packet loss in specific small regions is not your fault? Re: Packet Loss Southern California (Fortnite) Interesting, my friend a couple miles away has no packet loss, but weirdly enough I do whenever I use my internet.