SInce the start of October I have a regular drop out of connectivity around 10-12:00
Doesnt last long, just the router reboots and I need to conenct again, but why is it happening and what can be done to stop?
App doesnt show any outages/issues
| 20-10-2025 11:31:57 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
| 20-10-2025 11:31:48 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 11:31:46 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 11:31:43 | notice | Honoring MDD; IP provisioning mode = IPv4 |
| 20-10-2025 11:31:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 11:31:35 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 11:31:35 | critical | Cable Modem Reboot because of - unknown |
| 20-10-2025 00:11:33 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 00:11:28 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 00:10:31 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 19-10-2025 11:15:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 19-10-2025 11:15:53 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 19-10-2025 11:15:53 | critical | Cable Modem Reboot because of - unknown |
| 18-10-2025 11:06:15 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 18-10-2025 11:06:09 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 18-10-2025 11:06:05 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 18-10-2025 11:06:03 | critical | Cable Modem Reboot because of - unknown |
| 17-10-2025 10:56:09 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 17-10-2025 10:56:04 | critical | Cable Modem Reboot because of - unknown |
| 17-10-2025 10:56:04 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 16-10-2025 10:47:03 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 16-10-2025 10:46:57 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 16-10-2025 10:46:56 | critical | Cable Modem Reboot because of - unknown |
| 15-10-2025 10:37:10 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 15-10-2025 10:37:02 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 15-10-2025 10:36:59 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 15-10-2025 10:36:57 | critical | Cable Modem Reboot because of - unknown |
| 14-10-2025 10:27:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 14-10-2025 10:27:37 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 14-10-2025 10:27:37 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 13-10-2025 21:49:25 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 13-10-2025 21:49:17 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
Please post the power levels and network log from the Hub.
Also setup a BQM to monitor/record the incoming circuit http://www.thinkbroadband.com/ping
BQM pics posted, don't know if they are approved yet
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 45.3 5120 QAM 64 1
1 43100000 45.3 5120 QAM 64 2
2 36600000 45 5120 QAM 64 3
3 30100000 44.8 5120 QAM 64 4
4 23600000 44.8 5120 QAM 64 5
3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 0 1 0
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
11 10.4 40.7 2K QAM 256
3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
11 OFDMA 208 74000000 0 0
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 139000000 2.1 38 QAM 256 1
2 219000000 2.8 39 QAM 256 11
3 227000000 2.4 39 QAM 256 12
4 235000000 2.7 39 QAM 256 13
5 243000000 3 39 QAM 256 14
6 251000000 3.6 40 QAM 256 15
7 259000000 3.6 40 QAM 256 16
8 267000000 3.8 40 QAM 256 17
9 275000000 4.2 40 QAM 256 18
10 283000000 4.4 40 QAM 256 19
11 291000000 4.4 40 QAM 256 20
12 299000000 4.5 40 QAM 256 21
13 307000000 4.3 40 QAM 256 22
14 315000000 4.3 40 QAM 256 23
15 323000000 4.1 40 QAM 256 24
16 331000000 3.9 40 QAM 256 25
17 339000000 3.8 40 QAM 256 26
18 347000000 3.9 40 QAM 256 27
19 355000000 3.7 40 QAM 256 28
20 363000000 3.7 40 QAM 256 29
21 371000000 3.5 40 QAM 256 30
22 379000000 3.4 40 QAM 256 31
23 387000000 2.9 40 QAM 256 32
24 395000000 3 40 QAM 256 33
25 403000000 3.2 40 QAM 256 34
26 411000000 3.6 41 QAM 256 35
27 419000000 3.8 41 QAM 256 36
28 427000000 4 41 QAM 256 37
29 435000000 3.8 41 QAM 256 38
30 443000000 3.8 40 QAM 256 39
31 451000000 4 41 QAM 256 40
3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38 0 0
2 Locked 39 0 0
3 Locked 39 0 0
4 Locked 39 0 0
5 Locked 39 0 0
6 Locked 40 0 0
7 Locked 40 0 0
8 Locked 40 0 0
9 Locked 40 0 0
10 Locked 40 0 0
11 Locked 40 0 0
12 Locked 40 0 0
13 Locked 40 0 0
14 Locked 40 0 0
15 Locked 40 0 0
16 Locked 40 0 0
17 Locked 40 0 0
18 Locked 40 0 0
19 Locked 40 0 0
20 Locked 40 0 0
21 Locked 40 0 0
22 Locked 40 0 0
23 Locked 40 0 0
24 Locked 40 0 0
25 Locked 40 0 0
26 Locked 41 0 0
27 Locked 41 0 0
28 Locked 41 0 0
29 Locked 41 0 0
30 Locked 40 0 0
31 Locked 41 1 0
3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
41 94 4K 1840 QAM 4096 1108
3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
41 Locked 0 3.3 78758737 0
Power levels etc all look okay, but the T3 timeouts and reboots are not. Have you checked for area faults?
Since start of October?
Yes, some faults take weeks or months to resolve.
Can almost set your watch by them
| 22-10-2025 10:51:23 | notice | Honoring MDD; IP provisioning mode = IPv4 |
| 22-10-2025 10:51:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 22-10-2025 10:51:15 | critical | Cable Modem Reboot because of - unknown |
| 22-10-2025 10:51:15 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 21-10-2025 10:41:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 21-10-2025 10:41:24 | critical | Cable Modem Reboot because of - unknown |
| 21-10-2025 10:41:24 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 10:31:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1; |
| 20-10-2025 10:31:35 | critical | Cable Modem Reboot because of - unknown |
| 20-10-2025 10:31:35 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Do you notice anything else going funny at this time? I’m wondering if it’s the mains supply, surges, drop outs ?
Evertything appears normal.
Nothing is automated around those times to start or finish
Although you say nothing is automated around those times, it's possibly a smart switch or timer/standby timer you may have forgotten about that's set to test or turn on/off in 10 minute intervals around that time period.
Good thinking.
I went through all my smart plags and found one that was 10:00am to 10:20 turn on/off
You would think if it came on/off the impact in the house would be instant and not delayed 10+mins
But I have changed the times and we await tomorrow
23rds drop out
