Packet Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem. http://i.imgur.com/1Gnp1a5.png Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 73 813000000 Hz 8.7 dBmV 40.2 dB 9 65 2 Locked QAM256 74 819000000 Hz 9.1 dBmV 40.3 dB 23 48 3 Locked QAM256 75 825000000 Hz 8.9 dBmV 40.3 dB 17 56 4 Locked QAM256 76 831000000 Hz 9.1 dBmV 40.2 dB 43 133 5 Locked QAM256 77 837000000 Hz 9.4 dBmV 40.3 dB 15 84 6 Locked QAM256 78 843000000 Hz 9.8 dBmV 40.1 dB 11 67 7 Locked QAM256 79 849000000 Hz 9.7 dBmV 40.5 dB 13 60 8 Locked QAM256 80 855000000 Hz 9.6 dBmV 40.3 dB 18 69 9 Locked QAM256 89 909000000 Hz 8.8 dBmV 40.3 dB 15 55 10 Locked QAM256 90 915000000 Hz 8.7 dBmV 40.3 dB 38 61 11 Locked QAM256 91 921000000 Hz 8.7 dBmV 40.3 dB 24 98 12 Locked QAM256 92 927000000 Hz 9.2 dBmV 40.5 dB 38 31 13 Locked QAM256 93 933000000 Hz 8.8 dBmV 40.3 dB 22 81 14 Locked QAM256 94 939000000 Hz 8.2 dBmV 40.1 dB 49 107 15 Locked QAM256 95 945000000 Hz 7.7 dBmV 39.9 dB 18 57 16 Locked QAM256 96 951000000 Hz 8.2 dBmV 40.0 dB 12 69 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 37300000 Hz 36.9 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 19400000 Hz 34.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 24300000 Hz 35.3 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 30800000 Hz 36.0 dBmV Current System Time:Mon Jan 02 20:18:17 2017 Time Priority Description Mon Jan 02 20:02:24 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:45:13 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:44:45 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:44:44 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:43:15 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:40:31 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:39:48 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jan 02 19:38:47 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Jan 02 19:14:32 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 14:49:12 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Jan 01 12:18:24 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Sun Jan 01 12:06:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:08 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:04 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 07:45:18 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 04:12:00 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:36 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:26 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 01:04:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 00:34:59 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 22:08:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:37:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:29:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:21:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:04:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 18:26:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 17:06:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 14:38:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:22:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:20:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 09:14:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 20:11:54 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:32:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:31:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 14:19:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:53:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:32:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:06:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:44:52 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:16:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 09:43:45 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 08:47:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 23:01:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:37:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:10:05 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:09:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:05:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:04:38 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 12:16:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 10:44:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 04:02:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:46 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 20:58:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 14:04:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:26:04 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:25:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:26:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:24:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:18:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:29:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:27:38 2016 Critical (3) Resetting the cable modem due to docsDevResetNow Tue Dec 27 14:13:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 14:06:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 13:57:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 12:15:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 11:34:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 09:26:31 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 17:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:59 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 14:20:37 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 13:40:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:39:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 04:37:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 00:05:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 14:36:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 09:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0;8.6KViews0likes24Comments
HUGE Slowdown with Premiere Internet
I was promised up to 150 Mbps with this plan, but in the last 5-6 months, it has been VERY slow. Speed test: https://prnt.sc/fh5aek I have tried doing a chat with support 3 times and every single time, no matter what I said, they either ended up disconnecting or just resetting the modem. Which did absolutely nothing. I AM connected by Ethernet and this result is generally the same throughout the devices in my house, some slower. This is very frustrating because downloads were so quick, but now it's so slow it's unbearable. For example, in Steam, It downloads at about the same, around 33 Mbps, or ~3.9 MBps.http://prntscr.com/fh6afbSolved6.3KViews0likes22Comments
Low Upload speeds.
basically through exhaustive testing on multiplecomputers routers and switchs i still only receive 6-9mbps upload on testmy.net and real uploads to youtube google cloud and dropbox. My download speeds are fine, Called tier 2 support ans said its likely a issue with my sb6190 since all signal reading good and speedtest to cox and speedtest.net are fine and requested i try a new modem.5.4KViews0likes14Comments
New SB8200 - improper provisioning
I just purchased and installed a new Arris SB8200 for use at my home to replace an aging SB6120. I followed the installation instructions and I called cox customer service to register the new modem via it's SN and MAC address. The modem is connected and I'm able to connect to the internet. But here's the problem... My download speeds are horrendously slow now. Immediately before I disconnected the SB6120, I ran a speed test and I was getting in excess of my current plan speeds. ~60Mbps down and about 7-8Mbps up. Now, the same test yields around 10Mbps or less down and, at times, really high upload speeds around 20-30 Mbps. I have checked all of the signal levels reported by the modem webpage and they all appear nominal. It also appears that all 32 download channels have been bonded and 4 upload channels are bonded (see bottom). Here's a current speed test report from the cox website. as you can see horrendously slow on the download side which is less than 10% of what I should be receiving. Test Results Download Upload 4 Mbps 6 Mbps My Internet Plan COX INTERNET PREFERRED Download Upload 50 Mbps 5 Mbps Speed Test Results Device Type Latency desktop 31 ms IP Address Test Server So what gives? I know that many other cox users including those in Phoenix and elsewhere in AZ have reported that this modem works as advertised when provisioned. Has mine been provisioned improperly? I know from other users of the modem that the firmware version being pushed out by COX and other providers is at least one or more revisions older than the modem's current firmware revision which is: Software Version D31CM-PEREGRINE-1.0.0.2-GA-01-NOSH Why is my quality of service all of a sudden negatively impacted by upgrading my modem (which is something Cox want's you to do every few years) to the latest model which is officially supported by Cox? As a long time cox customer going back 17 years, this is not meeting my expectation of performance and service currently. :-( I am not connecting to the modem wirelessly, but through a wired Ethernet connection. I have tried connecting directly to my PC and through my router and the results are exactly the same. Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 170 Locked QAM256 807000000 Hz 5.6 dBmV 39.8 dB 0 0 169 Locked QAM256 801000000 Hz 5.9 dBmV 40.0 dB 0 0 206 Locked QAM256 975000000 Hz 1.4 dBmV 37.2 dB 0 0 171 Locked QAM256 813000000 Hz 5.5 dBmV 39.8 dB 0 0 172 Locked QAM256 819000000 Hz 5.6 dBmV 39.8 dB 0 0 173 Locked QAM256 825000000 Hz 5.6 dBmV 39.7 dB 0 0 174 Locked QAM256 831000000 Hz 5.5 dBmV 39.6 dB 0 0 175 Locked QAM256 837000000 Hz 5.6 dBmV 39.7 dB 0 0 176 Locked QAM256 843000000 Hz 5.6 dBmV 39.7 dB 0 0 177 Locked QAM256 849000000 Hz 5.6 dBmV 39.5 dB 0 0 178 Locked QAM256 855000000 Hz 5.7 dBmV 39.5 dB 0 0 179 Locked QAM256 861000000 Hz 5.8 dBmV 39.5 dB 0 0 180 Locked QAM256 867000000 Hz 5.7 dBmV 39.5 dB 0 0 181 Locked QAM256 873000000 Hz 5.4 dBmV 39.3 dB 0 0 182 Locked QAM256 879000000 Hz 4.9 dBmV 39.1 dB 0 0 183 Locked QAM256 885000000 Hz 4.5 dBmV 38.8 dB 0 0 184 Locked QAM256 891000000 Hz 4.0 dBmV 38.5 dB 0 0 185 Locked QAM256 897000000 Hz 3.6 dBmV 38.4 dB 0 0 186 Locked QAM256 903000000 Hz 3.2 dBmV 38.1 dB 0 0 187 Locked QAM256 909000000 Hz 2.9 dBmV 38.0 dB 0 0 188 Locked QAM256 915000000 Hz 3.0 dBmV 37.9 dB 1 0 189 Locked QAM256 921000000 Hz 3.1 dBmV 37.9 dB 0 0 190 Locked QAM256 927000000 Hz 3.3 dBmV 38.0 dB 0 0 191 Locked QAM256 933000000 Hz 3.5 dBmV 38.0 dB 2 0 192 Locked QAM256 939000000 Hz 3.6 dBmV 38.0 dB 2 0 201 Locked QAM256 945000000 Hz 3.2 dBmV 37.9 dB 2 0 202 Locked QAM256 951000000 Hz 3.1 dBmV 37.9 dB 0 0 203 Locked QAM256 957000000 Hz 2.6 dBmV 37.5 dB 0 0 204 Locked QAM256 963000000 Hz 2.2 dBmV 37.4 dB 1 0 205 Locked QAM256 969000000 Hz 1.8 dBmV 37.4 dB 1 0 207 Locked QAM256 981000000 Hz 1.1 dBmV 37.1 dB 0 0 208 Locked QAM256 987000000 Hz 0.7 dBmV 37.0 dB 0 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 2 Locked SC-QAM 23300000 Hz 6400000 Hz 37.3 dBmV 2 1 Locked SC-QAM 18400000 Hz 3200000 Hz 36.9 dBmV 3 3 Locked SC-QAM 29800000 Hz 6400000 Hz 37.3 dBmV 4 4 Locked SC-QAM 36300000 Hz 6400000 Hz 38.8 dBmV5.3KViews0likes3Comments
Incompetence at the highest level
For almost 2 weeks now, I have been unable to properly use my internet services. I pay for the Ultimate Bundle, mainly for heavy gaming and streaming. Recently, I have been experiencing major packet loss, choke and request time outs with my connection. When I originally called, the person over the phone told me my modem was the problem; I had an arris SB6190. He recommended I buy a netgear cm1000, which indeed I did. A few days later, the modem arrived and the problem wasn't resolved. A ticket was created for me and a technician came out on 10 / 23 (Monday). He couldn't figure out the problem, so he referred my case to maintenance. I have called almost every day since 10 / 23 (Monday) to make sure my ticket was moving in the right direction, and EVERY SINGLE PERSON told me the maintenance team is going to work on it, and that they need 3-5 days to fix this issue. I called yesterday 10 / 26 (Thursday) to ask for a status, and I was told that a supervisor would call me back within a few hours to inform me of what is going on. I never received a call back. I call again today 10 / 27 (Friday), in which the tier 2 technician tells me a maintenance ticket was never properly put in. WHAT?!?!?! Before I elaborate, let me just tell you everything I have tried. 1) New modem - 2) Bypassed router and went direct to modem - 3) bought new Ethernet cable [cat6] - 4) tried using WiFi instead - 5) tried using multiple computers, all have the same issue - 6) had tech come out to test the lines, which tested fine - 7) called tier 2 numerous times, in which they have confirmed they do see packet loss on my connection **Also a side note. I have worked in I.T. for 10+ years, and I am not computer/networking illiterate.** Back to the status, they now tell me a tech has to come back out to look at the problem once more, and if he can't resolve it (which I am confident he 100% will not), he will refer back to the maintenance team. This is absolutely ridiculous and incompetence at the highest level. How is it possible that over 5+ people within the past week have all told me a maintenance ticket was properly created into the system, and the last day I expect it to be resolved, I get word that they cannot even see a maintenance ticket on my account. After I requested to speak to a supervisor this morning (15 minutes ago), I told him he needs to go back and review all my calls (I hope they are recorded). It is nearly impossible for everyone to magically see that maintenance ticket, but then suddenly it disappears? I even talked to the CAG Line yesterday, in which they also confirmed a maintenance ticket. I am about to ready to completely cancel my service with COX, because this is the most unprofessional and incompetent practice I have seen since Comcast.4.8KViews0likes14Comments
Microcells Won't Connect Through Cox Network
I have three Microcells in our home. They allow us to have a cell site in our home using the internet connection. Microcells are made by CISCO and they're pretty much "plug and play" units - you plug them in to the internet, and they bring your cells phone full bars, etc. These microcells have been here in our home for 4 years with very little maintenance - ATT replaces them if there is a problem. There has been no changes in configuration or hardware in our home in the past 2 years. Yesterday they stopped working. Our internet was the first suspect because what would affect all units at once? But our internet tests rock solid, no jitter, plenty of speed. We also thought well perhaps the Netgear CG3000DV2 router changed but we tested it and Cox says it is OK. We spent hours working with ATT troubleshooting the units - restarting them and attempting to reload the software from the ATT servers but the units just cannot contact the ATT server. So we looked into the ports they use. They use 123, 443, 500, and 4500. It appears from speaking to ATT that port 4500 is where they do the remote management and download of the software including updates. And we checked these ports on our router. All ports on the router are open. So now we know that the problem is most likely port 4500 being blocked but not inside our house. I have called Cox and explained the problem and asked for help. I know that Cox is more equipped to solve this problem than ATT because they are only able to help with devices - they will send me replacements for free but I know that won't fix my problem. I reviewed the ports that are blocked by Cox for "policy" - that means that they have a policy for instance of not allowing people to host a file server or web server at their home - they block those ports by policy.4500 is not one of the ports they block by policy. So how can I work with Cox in a manner that would get them to help me find the problem? Does anyone have any insight into how to solve this complex problem? The problem definition is simple - Cox is blocking port 4500 somewhere and I need their help to find out where." I have gone through a lot more troubleshooting and verification than I have listed here so just ask and I'll tell you if we've done it.4.5KViews0likes7Comments
modem goes up and down
I have had 3 cox tech visits. tested and rebuit connections from street and all splitters replaced by coxtech. Now scheduled for a 4th visit. Called support - they cant see returns from the modem. I'm told it is the modem. Im not sure - same happened on old modem. I replaced with Linksys CM3008 in Nov 16 and still happens. Router is an Orbi. I post recent summary and last 20 events from the modem log here. I think line level is 36 db? this is without countour in the chain - direct wall to modem. no splitter - although it is a tech provided splitter and last tech even built the coax cables himself to make sure they were good. I deas? I am not sure why the 4th service call will be better than last 3? Esp if no one looks at the logs. Not enjoying having to chose between countour or internet - want to have both at same time. 18 year Cox customer here! DOCSIS Overview Network Access Permitted IP Address 10.73.45.139 Subnet Mask 255.255.240.0 Gateway IP 10.73.32.1 DHCP Lease Time D: 07 H: 00 M: 00 S: 00 Downstream Overview Port ID Frequency (Hz) Modulation Signal strength (dBmV) Signal noise ratio (dB) Octets Correcteds Uncorrectables Channel ID 1 795000000 256QAM -0.847 37.093 2955993571 1597 621 3 2 783000000 256QAM -0.359 37.093 2955987673 197 642 1 3 789000000 256QAM -1.150 37.093 2956010846 235 609 2 4 801000000 256QAM -1.388 37.093 2956021960 955 606 4 5 807000000 256QAM -1.476 37.636 2955997473 271 703 5 6 813000000 256QAM -1.631 37.636 2955998789 126 654 6 7 819000000 256QAM -1.988 37.356 2956007829 211 632 7 8 825000000 256QAM -1.925 37.093 2956007015 223 764 8 Reset FEC Counters Upstream Overview Port ID Frequency (Hz) BandWidth (Hz) Modulation Type DOCSIS Mode Signal Strength (dBmV) Channel ID 1 10000000 6400000 64QAM ATDMA 57.000 --- 2 30400195 6400000 64QAM ATDMA 51.000 34.1KViews0likes9CommentsPacket loss & High Pings 9PM - 10AM
This issue just recently started occurring or became blatantly obvious in the past 5 days. Rubber banding in online games and occasionally getting disconnected anywhere from 5-20 seconds. Sometimes from just from party chats and sometimes from matches. I ran pingtest.net to a few different servers during this time frame and got anywhere from 5-50% packet loss with pings around 300-400 with 400-500 jitter. http://www.pingtest.net/result/152756719.png Also I will have extreme fluctuations in my upload speeds during this time.I have T3 & T4 timeouts and errors on my modem as well which I have been told isn't a problem. I bought this modem, SB6183, because I thought my 6141 might have been the problem. It was not. I tried direct wiring into the modem and still had the same issue. I called tech support about the issue twice. And both times they had issues seeing that it was online. Yet I was connected to the internet. When they could see the modem the power levels and SNR were good. I've been with Cox for 3 years now and everytime I have an issue like this and bug technicians about it they tell me that they will forward the ticket up but that, in a hushed voice, I shouldn't expect anything to get done. I can post any results you need to get this ** fixed!Solved3.6KViews0likes8Comments
Slow Gigablast speeds with my home pc's on ethernet connections.
I just got Gigablast and my Ethernet(LAN) speeds on three different PC's in three different places in the home never get more than the low 400's MB. The technician says I am getting 950MB from the fiber into their supplied router. He says "I need to get my PC's cleaned out." That seems like a silly answer, but I had Geek Squad to it anyway. No change. I have also upgraded my drivers on all three PC's. I used to get 150-180 MB on all my PC's with the COX high speed internet I used to have. So I have only doubled my speed in the home with Gigablast. It doesn't see worth it. Cox Level 2 support has more or less given up talking to me. For reference, one of my PC's is a 6-month oldDELL INSPIRON 5459. I used to get 180 MB on this with the old Cox Modem high speed internet through the same Ethernetconnection. The Gigablast speed seems to never get over 425 MB. Any ideas out there?3.5KViews0likes4Comments
"Up to 300Mbps" is that accurate?
I've been a customer of Comcast for many years (not by choice) and whenever I had service that advertised a speed it was usually accurate within 10%. This isn't my first time around the block with testing my internet connection, I did it wired directly to the modem using the tools provided by Cox (not the random speedtest.net location) and I am getting between 140-195Mbps. Granted this is not a horrible speed, but it is between 45-65% of what I am paying for. Believe it or not, my upload speeds are spot on. Based on this I should be on the tier below saving an additional $20/month. Or would I suffer from the same ratios on my speeds? I could do some additional trouble shooting , like taking my modem downstairs to where the cable comes in the house and unplugging everything, but I really don't want to go through the hassle if this is the best it is going to be.3.3KViews0likes3Comments
Low Upload speeds.
basically through exhaustive testing on multiplecomputers routers and switchs i still only receive 6-9mbps upload on testmy.net and real uploads to youtube google cloud and dropbox. My download speeds are fine, Called tier 2 support ans said its likely a issue with my sb6190 since all signal reading good and speedtest to cox and speedtest.net are fine and requested i try a new modem.
