on 19-12-2021 15:13
Hello all,
Just after some quick help. I have been monitoring my connection on thinkbroadband and notice a maximum latency spike every hour without fail. Can someone explain what this means and if its ok as I also monitor some other family members connections and I do not see the same happen on their graphs.
Thank you.
Answered! Go to Answer
on 19-12-2021 17:12
on 19-12-2021 16:23
As you are using a Hub 5. note it's still on trial and by invite only, so expect unusual things.
Having said that, try a pinhole reset to force down the latest firmware, just in case.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
19-12-2021 16:33 - edited 19-12-2021 16:38
Thanks for the reply.
Yes I am on the Hub 5 so do understand its in trial, maybe this issue/non issue will help VM staff on here.
I have done a reset a few times, the current software version on the hub is:
Software version : LG-RDK_2.23.11-2106.14
If it helps the info from the hub is as follows:
Item Status Comments
Acquired Downstream Channel(Hz) | 331000000 | Locked |
Ranged Upstream Channel(Hz) | 46200000 | Ranged |
Provisioning State | Online | Operational |
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 4 | 41 | QAM 256 | 25 |
2 | 139000000 | 5.3 | 41 | QAM 256 | 1 |
3 | 147000000 | 5.2 | 41 | QAM 256 | 2 |
4 | 155000000 | 5.1 | 41 | QAM 256 | 3 |
5 | 163000000 | 5.2 | 41 | QAM 256 | 4 |
6 | 171000000 | 4.9 | 41 | QAM 256 | 5 |
7 | 179000000 | 4.8 | 41 | QAM 256 | 6 |
8 | 187000000 | 4.8 | 42 | QAM 256 | 7 |
9 | 195000000 | 5 | 42 | QAM 256 | 8 |
10 | 203000000 | 4.9 | 42 | QAM 256 | 9 |
11 | 211000000 | 5 | 42 | QAM 256 | 10 |
12 | 219000000 | 4.7 | 41 | QAM 256 | 11 |
13 | 227000000 | 4.7 | 42 | QAM 256 | 12 |
14 | 235000000 | 4.5 | 41 | QAM 256 | 13 |
15 | 243000000 | 4.1 | 41 | QAM 256 | 14 |
16 | 251000000 | 3.6 | 41 | QAM 256 | 15 |
17 | 259000000 | 3.1 | 41 | QAM 256 | 16 |
18 | 267000000 | 2.8 | 41 | QAM 256 | 17 |
19 | 275000000 | 2.7 | 41 | QAM 256 | 18 |
20 | 283000000 | 3.3 | 41 | QAM 256 | 19 |
21 | 291000000 | 3.8 | 41 | QAM 256 | 20 |
22 | 299000000 | 4.2 | 41 | QAM 256 | 21 |
23 | 307000000 | 4.1 | 41 | QAM 256 | 22 |
24 | 315000000 | 4.2 | 41 | QAM 256 | 23 |
25 | 323000000 | 4 | 41 | QAM 256 | 24 |
26 | 339000000 | 3.8 | 41 | QAM 256 | 26 |
27 | 347000000 | 3.9 | 41 | QAM 256 | 27 |
28 | 355000000 | 4 | 41 | QAM 256 | 28 |
29 | 363000000 | 4.3 | 41 | QAM 256 | 29 |
30 | 371000000 | 4.2 | 41 | QAM 256 | 30 |
31 | 379000000 | 4 | 41 | QAM 256 | 31 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 41 | 0 | 20 |
2 | Locked | 41 | 0 | 29 |
3 | Locked | 41 | 0 | 25 |
4 | Locked | 41 | 0 | 18 |
5 | Locked | 41 | 0 | 26 |
6 | Locked | 41 | 0 | 49 |
7 | Locked | 41 | 0 | 13 |
8 | Locked | 42 | 0 | 24 |
9 | Locked | 42 | 0 | 18 |
10 | Locked | 42 | 0 | 13 |
11 | Locked | 42 | 0 | 21 |
12 | Locked | 41 | 0 | 11 |
13 | Locked | 42 | 0 | 21 |
14 | Locked | 41 | 0 | 25 |
15 | Locked | 41 | 0 | 23 |
16 | Locked | 41 | 0 | 21 |
17 | Locked | 41 | 0 | 21 |
18 | Locked | 41 | 0 | 29 |
19 | Locked | 41 | 0 | 17 |
20 | Locked | 41 | 0 | 34 |
21 | Locked | 41 | 0 | 25 |
22 | Locked | 41 | 0 | 22 |
23 | Locked | 41 | 0 | 30 |
24 | Locked | 41 | 0 | 24 |
25 | Locked | 41 | 0 | 25 |
26 | Locked | 41 | 0 | 33 |
27 | Locked | 41 | 0 | 25 |
28 | Locked | 41 | 0 | 28 |
29 | Locked | 41 | 0 | 29 |
30 | Locked | 41 | 0 | 19 |
31 | Locked | 41 | 0 | 19 |
19-12-2021 16:34 - edited 19-12-2021 16:36
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 40.8 | 5120 | QAM 64 | 3 |
2 | 39400000 | 40.5 | 5120 | QAM 64 | 4 |
3 | 32600000 | 40.3 | 5120 | QAM 64 | 5 |
4 | 25800000 | 40.3 | 5120 | QAM 64 | 6 |
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 |
General Configuration
Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed |
1 |
Enabled |
3.1 |
cmreg-vmdg660-bbt076-b.cm |
Primary Downstream Service Flow
SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
148708 |
1230000450 bps |
42600 bytes |
0 bps |
Primary Upstream Service Flow
SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
148707 |
55000270 bps |
42600 bytes |
0 bps |
42600 bytes |
Best Effort |
on 19-12-2021 16:35
Network Log
Time Priority Description
09-12-2021 16:20:25 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:57:57 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:56:00 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:55:53 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
09-12-2021 15:55:47 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:55:10 | critical | DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:54 | critical | DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:53 | critical | DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:45 | critical | DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:44 | critical | DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:43 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:40 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:40 | critical | DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:40 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:38 | notice | Honoring MDD; IP provisioning mode = IPv4 |
09-12-2021 15:54:34 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:54:25 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-12-2021 15:46:24 | critical | Cable Modem Reboot from SNMP |
on 19-12-2021 16:57
on 19-12-2021 17:12
on 19-12-2021 17:30
on 21-12-2021 18:31
Hi tdbegley28,
Thanks for your post and apologies to hear you were having an issue with latency spikes.
I'm glad to hear that with the help of the Community, you've been able to locate the source of the latency.
If you continue to have issues after disabling the tests on your third party router, let us know.
Thanks,