Hub 3.0 in modem mode
Every month or so, I notice ping spikes while working from home. Upon checking the BMQ you can see it's terrible.
192.168.100.1 is inaccessible - like the web server is down or something.
When I manually reboot the Hub 3.0, everything seems to start working again. I can now access 192.168.100.1
Is this really expected, I must manually reboot the router this often?
Try checking with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.
Post the power levels, Pre and PostRS errors and network log from the Hub.
Also run a wired speed test on www.samknows.com/realspeed and post the results.
Once done we can comment.
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 23600000 46.3 5120 64 qam 11
2 36600000 47 5120 64 qam 6
3 49600000 47 5120 64 qam 4
4 30100000 46.8 5120 64 qam 8
5 43100000 47.3 5120 64 qam 5
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
5 ATDMA 0 0 0 0
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 195000000 -2.5 40 256 qam 8
2 179000000 -2 38 256 qam 6
3 187000000 -2.2 40 256 qam 7
4 203000000 -2.2 40 256 qam 9
5 211000000 -2.7 40 256 qam 10
6 219000000 -2.5 40 256 qam 11
7 227000000 -2.5 40 256 qam 12
8 235000000 -3.2 38 256 qam 13
9 243000000 -3.2 38 256 qam 14
10 251000000 -3 40 256 qam 15
11 259000000 -3.2 38 256 qam 16
12 267000000 -2.9 40 256 qam 17
13 275000000 -3.2 40 256 qam 18
14 283000000 -3 40 256 qam 19
15 291000000 -3.4 38 256 qam 20
16 299000000 -3 38 256 qam 21
17 307000000 -2.9 40 256 qam 22
18 315000000 -3.2 40 256 qam 23
19 323000000 -3.2 40 256 qam 24
20 331000000 -3.7 38 256 qam 25
21 339000000 -4 38 256 qam 26
22 347000000 -3.7 40 256 qam 27
23 355000000 -4.2 38 256 qam 28
24 363000000 -4.4 38 256 qam 29
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 5 0
2 Locked 38.9 5 0
3 Locked 40.3 5 0
4 Locked 40.9 5 0
5 Locked 40.9 6 0
6 Locked 40.9 4 0
7 Locked 40.3 5 0
8 Locked 38.9 0 0
9 Locked 38.9 5 0
10 Locked 40.3 5 0
11 Locked 38.9 6 0
12 Locked 40.3 5 0
13 Locked 40.3 6 0
14 Locked 40.3 5 0
15 Locked 38.9 6 0
16 Locked 38.6 5 0
17 Locked 40.3 0 0
18 Locked 40.3 5 0
19 Locked 40.3 4 0
20 Locked 38.9 0 0
21 Locked 38.9 0 0
22 Locked 40.3 5 0
23 Locked 38.6 7 0
24 Locked 38.9 14 0
Time Priority Description
09/12/2025 12:38:25 notice LAN login Success;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
09/12/2025 09:58:57 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
08/12/2025 18:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
05/12/2025 19:14:41 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
05/12/2025 06:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
03/12/2025 22:01:38 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
01/12/2025 18:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
29/11/2025 11:00:19 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
28/11/2025 06:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
25/11/2025 14:11:31 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
24/11/2025 18:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
23/11/2025 07:40:27 critical No Ranging Response received - T3 time-out;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
21/11/2025 06:02:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[REDACTED-CM-MAC];CMTS-MAC=[REDACTED-CMTS-MAC];CM-QOS=1.1;CM-VER=3.0;
Been fine since I rebooted the hub at 12:45pm yesterday...
Why was the hub struggling and requiring a reboot?
