SInce the start of October I have a regular drop out of connectivity around 10-12:00Doesnt 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

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.

20-10-2025 11:31:57noticeREGISTRATION COMPLETE - Waiting for Operational status20-10-2025 11:31:48noticeDS 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:46warningDHCP 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:43noticeHonoring MDD; IP provisioning mode = IPv420-10-2025 11:31:39criticalNo 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:35criticalSYNC 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:35criticalCable Modem Reboot because of - unknown20-10-2025 00:11:33criticalNo 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:28criticalNo 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:31criticalNo 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:59criticalNo 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:53criticalSYNC 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:53criticalCable Modem Reboot because of - unknown18-10-2025 11:06:15criticalSYNC 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:09criticalNo 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:05criticalSYNC 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:03criticalCable Modem Reboot because of - unknown17-10-2025 10:56:09criticalNo 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:04criticalCable Modem Reboot because of - unknown17-10-2025 10:56:04criticalSYNC 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:03criticalNo 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:57criticalSYNC 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:56criticalCable Modem Reboot because of - unknown15-10-2025 10:37:10criticalSYNC 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:02criticalNo 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:59criticalSYNC 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:57criticalCable Modem Reboot because of - unknown14-10-2025 10:27:41criticalNo 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:37criticalCable Modem Reboot because of - HW or Power-On Reset14-10-2025 10:27:37criticalSYNC 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:25criticalSYNC 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:17criticalSYNC 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

3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID0 49600000 45.3 5120 QAM 64 11 43100000 45.3 5120 QAM 64 22 36600000 45 5120 QAM 64 33 30100000 44.8 5120 QAM 64 44 23600000 44.8 5120 QAM 64 53.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts0 ATDMA 0 0 1 01 ATDMA 0 0 0 02 ATDMA 0 0 0 03 ATDMA 0 0 0 04 ATDMA 0 0 0 03.1 Upstream channelsChannel Channel Width (MHz) Power (dBmV) FFT Type Modulation11 10.4 40.7 2K QAM 2563.1 Upstream channelsChannel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts11 OFDMA 208 74000000 0 0

3.0 Downstream channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID1 139000000 2.1 38 QAM 256 12 219000000 2.8 39 QAM 256 113 227000000 2.4 39 QAM 256 124 235000000 2.7 39 QAM 256 135 243000000 3 39 QAM 256 146 251000000 3.6 40 QAM 256 157 259000000 3.6 40 QAM 256 168 267000000 3.8 40 QAM 256 179 275000000 4.2 40 QAM 256 1810 283000000 4.4 40 QAM 256 1911 291000000 4.4 40 QAM 256 2012 299000000 4.5 40 QAM 256 2113 307000000 4.3 40 QAM 256 2214 315000000 4.3 40 QAM 256 2315 323000000 4.1 40 QAM 256 2416 331000000 3.9 40 QAM 256 2517 339000000 3.8 40 QAM 256 2618 347000000 3.9 40 QAM 256 2719 355000000 3.7 40 QAM 256 2820 363000000 3.7 40 QAM 256 2921 371000000 3.5 40 QAM 256 3022 379000000 3.4 40 QAM 256 3123 387000000 2.9 40 QAM 256 3224 395000000 3 40 QAM 256 3325 403000000 3.2 40 QAM 256 3426 411000000 3.6 41 QAM 256 3527 419000000 3.8 41 QAM 256 3628 427000000 4 41 QAM 256 3729 435000000 3.8 41 QAM 256 3830 443000000 3.8 40 QAM 256 3931 451000000 4 41 QAM 256 403.0 Downstream channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors1 Locked 38 0 02 Locked 39 0 03 Locked 39 0 04 Locked 39 0 05 Locked 39 0 06 Locked 40 0 07 Locked 40 0 08 Locked 40 0 09 Locked 40 0 010 Locked 40 0 011 Locked 40 0 012 Locked 40 0 013 Locked 40 0 014 Locked 40 0 015 Locked 40 0 016 Locked 40 0 017 Locked 40 0 018 Locked 40 0 019 Locked 40 0 020 Locked 40 0 021 Locked 40 0 022 Locked 40 0 023 Locked 40 0 024 Locked 40 0 025 Locked 40 0 026 Locked 41 0 027 Locked 41 0 028 Locked 41 0 029 Locked 41 0 030 Locked 40 0 031 Locked 41 1 03.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)41 94 4K 1840 QAM 4096 11083.1 Downstream channelsChannel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)41 Locked 0 3.3 78758737 0

10AM Drop Out | Virgin Media Community

17 Replies

NE30

On our wavelength

2 months ago

Still happening

24-10-2025 11:11:46	notice	REGISTRATION COMPLETE - Waiting for Operational status
24-10-2025 11:11:36	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:34	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=ccc;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:32	notice	Honoring MDD; IP provisioning mode = IPv4
24-10-2025 11:11:28	critical	No Ranging Response received - T3 time-out;CM-MAC=c;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:24	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:22	critical	Cable Modem Reboot because of - unknown
23-10-2025 11:01:22	critical	No Ranging Response received - T3 time-out;CM-MAC=c;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
23-10-2025 11:01:17	critical	Cable Modem Reboot because of - unknown
23-10-2025 11:01:17	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

[MOD - MAC addresses removed]

Robert_P

Forum Team

2 months ago

Hello NE30,

Sorry to hear of the connection issues experienced and the regular drop outs, we appreciate you taking the time to raise this via the forums.

We've taken a look and all of the levels and specs for the Hub are within the ranges we'd expect to see, the drop out timings are very specific and to precise to be an area issue and look to be more system/hub based.

Are you aware of any changes being made or a reboot timer being set up? Have you tried removing the smart plugs completely to see if the reboot still occurs around these times?

NE30

On our wavelength

28 days ago

I have been away for a week and all timers/plugs etc. were removed as I was out of the house

28-10-2025 11:53:12	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
28-10-2025 11:53:08	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:58:30:05:ff:76;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
28-10-2025 11:53:06	critical	Cable Modem Reboot because of - unknown
27-10-2025 11:43:32	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
27-10-2025 11:43:28	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;
27-10-2025 11:43:26	critical	Cable Modem Reboot because of - unknown
26-10-2025 11:31:53	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
26-10-2025 11:31:42	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
26-10-2025 11:31:38	critical	Cable Modem Reboot because of - unknown
26-10-2025 11:31:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
25-10-2025 11:21:55	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
25-10-2025 11:21:50	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
25-10-2025 11:21:48	critical	Cable Modem Reboot because of - unknown
24-10-2025 11:11:28	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:24	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-10-2025 11:11:22	critical	Cable Modem Reboot because of - unknown
23-10-2025 11:01:22	critical	No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:01:5c:82:6a:5c;CM-QOS=1.1;CM-VER=3.1;
23-10-2025 11:01:17	critical	Cable Modem Reboot because of - unknown

Forum Discussion

10AM Drop Out

17 Replies

Related Content

Connection keeps dropping

WiFi keeps dropping out

Broadband connection keeps dropping

Internet Connection Drops

Wifi dropping - laptop drops out