New Contributor
•
12 Messages
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; |
Related Content
Closed
4
0
Closed
2
0
Closed
10
0
Closed
2
0
Closed
1
0

thehollowaytape
New Contributor
•
12 Messages
I can't make it through a single game of Overwatch without getting disconnected. This is absolutely infuriating. The last time I had this issue was on Thanksgiving weekend. I am off work this week and was looking forward to relaxing and being able to play games online, and here's what I get. $75 a month to not be able to use the internet. Last time I had this issue I was literally able to play more reliably using my phone as a hotspot than I was using my home internet. Something is wrong here.
0
0
thehollowaytape
New Contributor
•
12 Messages
This just occured:
http://i.imgur.com/rJnBiQW.png
0
0
ChrisL
Former Moderator
•
7.1K Messages
I'm not seeing the modem online when I check from this end. Are there any cable splitters you can try bypassing and seeing if that helps?
0
0
thehollowaytape
New Contributor
•
12 Messages
I unplugged the modem overnight. There are no splitters, I went and looked in the box last night. Just a ground and cables (reused DirecTV coax cable).
0
0
ChrisL
Former Moderator
•
7.1K Messages
I do see the modem back online now with good signal levels but it is reporting lots of power adjustments trying to maintain sync. Do you have the modem plugged into a power strip with a lot of other devices? It may be helpful try connecting to a different power source and see if that makes a difference.
0
0
thehollowaytape
New Contributor
•
12 Messages
It is plugged into a three-way splitter. I'll try plugging it into its own outlet and report back.
0
0
thehollowaytape
New Contributor
•
12 Messages
@ChrisL
I didn't have many major issues yesterday, but the issues are back today. I have the modem plugged into it's own outlet with nothing else, and my router is plugged into its own outlet as well. The PC I am running PingPlotter on is connected to the router with a brand new CAT 6 cable. I have connected directly to the modem and these issues still occur, it is nothing to do with the router. Here is another PingPlotter screenshot from a few moments ago.
http://i.imgur.com/JaALW48.png
Current System Time: Wed Jan 04 13:18:32 2017
0
0
thehollowaytape
New Contributor
•
12 Messages
@ChrisL
Some more info:
1 days 10h:37m:19s
0
0
ChrisL
Former Moderator
•
7.1K Messages
You could also try seeing if the modem works better on a different cable outlet. Otherwise it may be time to see about having a technician come out and troubleshoot further.
0
0
thehollowaytape
New Contributor
•
12 Messages
@ChrisL
I do not have another outlet hooked up here. Almost every time I get these drops I'm getting a Dynamic Range Violation, which from what I can gather is the modem having to exceed power specs to maintain upstream sync.
http://i.imgur.com/GAtFxRV.png
Dynamic Range Window violation
0
0
thehollowaytape
New Contributor
•
12 Messages
@ChrisL
I had a technician out here in November, and he pulled the DirecTV filter/splitter off inside of the box and said it was fixed. I left him a detailed note of the issue and I highly doubt he even read it. I was at work when this occurred and my housemate said he was here for 10 minutes tops. I have looked in the box and now it's just a straight connection between the wire coming from the pole to the wire going to my cable modem, the only thing in between is the coax grounding block and a wire going from that to ground. I have only lived in this house since Sept 2015. Is it possible that there have always been issues at this house and that is why the people who lived here before had DirecTV?
I just want reliable internet. I pay monthly for this and should not have to suffer through constant disconnects and internet issues when I am paying for this service, it is not being given to me for free or by charity. I play games with other Cox customers and my internet is dropping as they continue to stay in the game and play. Something is wrong here, whether it be something at the headend, the wire coming from my house to the pole, the coax drop to my modem, I do not know. But I would appreciate having someone who actually knows what they're doing and troubleshooting properly, instead of a subcontractor who is here to do literally as little work as he can possibly do. I work 9-5 Monday through Friday and cannot be here to babysit someone who doesn't want to do their job, and with this problem being intermittent it makes it even worse because I won't always be able to replicate it outside of the information that I have cataloged here in this thread.
0
0
mkb914
New Contributor
•
2 Messages
I'm having similar problems, and for about the same length of time. My friends in Starcraft II are getting mad that I keep dropping connection in the middle of matches, and it extends to other devices as well... I have reset my modem and router numerous times, both by unplugging from the wall and through Cox website.
After seeing PingPlotter, I gave it a shot to see if I could capture what I am experiencing. Sure enough, there are multiple service interruptions in a 10 minute window.
0
0
Becky
Moderator
•
4.3K Messages
Please let us know how the service call goes, and if you continue to have any issues after the tech leaves. We'll stay on top of this for you!
0
0
Becky
Moderator
•
4.3K Messages
I'm glad to see that you, too, have a service call scheduled so an on-site technician can take a closer look at your connectivity. Please let us know how it goes!
0
0
thehollowaytape
New Contributor
•
12 Messages
@Becky
The tech came out and replaced the coax going from the modem to the wall, and also fixed a bad piece of coax behind the wall plate. I will continue to monitor to see if this has rectified the issue.
0
0