on 17-12-2021 01:07
Hello!
This is a bit of a double question, apologies.
Firstly I've been having awful ping spikes making any gaming impossible at peak times (don't fancy playing between 12-7am) for the past 2 weeks. Before this I noticed less frequent ping issues but more than on my old hub 3.
Secondly my WiFi pod boosters can barely give me speeds of between 20-100mb, even when plugged in right next to the router to test.
I think I'm armed with a couple days worth of BQMs, but I'm assuming people will need more information to help meaningfully, happy to post whatever is required.
Thanks
😊
Answered! Go to Answer
on 17-12-2021 07:13
I'll leave pod or booster issues to others, as they're not something I know about, and my preferred wifi solution is to take all of it out of VM's hands and do the job properly, but that costs money.
On the connection quality, there's a couple of things - first the possible impact of the latest work from home guidance which means that whilst this lasts there's a lot more problems (for some areas) on the upstream side of VM's network, creating latency problems that affect gamers, any Teams/Zoom/Skype types of use, and live streaming. There's not much VM can do about that, as its a result of the network not being designed for this pattern of usage, and changing that would take far longer than the current issues will last. VM are improving capacity all the time, but it's a long, slow technically complicated task, and not something they can suddenly accelerate or deliver to every affected area.
The second thing is that it looks to me like the power levels may be out, as the DOCSIS 3.1 power level looks to me far too high relative to the D 3.0 channels, and those are a bit variable to boot. This can be addressed, but I'm not sure whether the Fisher Price diagnostics that VM use will recognise that pattern of power level problems, and if they don't you'll need a staff member who can interpret the numbers - wait and see what the forum staff have to say.
on 17-12-2021 02:03
Cable Modem StatusItemStatusCommentsCable Modem Status
Primary downstream channel
Channel OverviewDownstreamUpstreamDOCSIS 3.0 channels
DOCSIS 3.1 channels
on 17-12-2021 02:04
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 1.4 | 39 | QAM256 | 25 |
1 | 139000000 | 1.8 | 40.4 | QAM256 | 1 |
2 | 147000000 | 1.7 | 40.4 | QAM256 | 2 |
3 | 155000000 | 1.8 | 40.4 | QAM256 | 3 |
4 | 163000000 | 1.6 | 40.4 | QAM256 | 4 |
5 | 171000000 | 1.6 | 40.4 | QAM256 | 5 |
6 | 179000000 | 1.6 | 40.9 | QAM256 | 6 |
7 | 187000000 | 1.7 | 40.4 | QAM256 | 7 |
8 | 195000000 | 2.1 | 40.4 | QAM256 | 8 |
9 | 203000000 | 2.2 | 40.4 | QAM256 | 9 |
10 | 211000000 | 2.4 | 40.4 | QAM256 | 10 |
11 | 219000000 | 2.4 | 40.4 | QAM256 | 11 |
12 | 227000000 | 2.3 | 40.4 | QAM256 | 12 |
13 | 235000000 | 2.3 | 40.9 | QAM256 | 13 |
14 | 243000000 | 2.1 | 40.4 | QAM256 | 14 |
15 | 251000000 | 1.9 | 40.4 | QAM256 | 15 |
16 | 259000000 | 2.2 | 40.4 | QAM256 | 16 |
17 | 267000000 | 2.5 | 40.9 | QAM256 | 17 |
18 | 275000000 | 3 | 40.4 | QAM256 | 18 |
19 | 283000000 | 2.6 | 40.4 | QAM256 | 19 |
20 | 291000000 | 2 | 40.4 | QAM256 | 20 |
21 | 299000000 | 1.9 | 40.4 | QAM256 | 21 |
22 | 307000000 | 2 | 40.4 | QAM256 | 22 |
23 | 315000000 | 2.2 | 40.9 | QAM256 | 23 |
24 | 323000000 | 2.2 | 40.4 | QAM256 | 24 |
26 | 339000000 | 1.6 | 40.4 | QAM256 | 26 |
27 | 347000000 | 1.3 | 40.4 | QAM256 | 27 |
28 | 355000000 | 1.2 | 40.4 | QAM256 | 28 |
29 | 363000000 | 1.1 | 39 | QAM256 | 29 |
30 | 371000000 | 1.5 | 40.4 | QAM256 | 30 |
31 | 379000000 | 1.5 | 40.4 | QAM256 | 31 |
on 17-12-2021 02:05
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 40.366287 | 0 | 0 |
2 | Locked | 40.366287 | 0 | 0 |
3 | Locked | 40.366287 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.366287 | 0 | 0 |
6 | Locked | 40.946209 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.946209 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
159 | 96 | 4K | 1880 | QAM4096 | 392 |
159 | Locked | 43 | 3.4 | 242651773 | 0 |
on 17-12-2021 02:06
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 40 | 5120 KSym/sec | 64QAM | 1 |
2 | 25800000 | 40 | 5120 KSym/sec | 64QAM | 4 |
3 | 32600000 | 40 | 5120 KSym/sec | 64QAM | 3 |
4 | 39400000 | 40 | 5120 KSym/sec | 64QAM | 2 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cxv9873254k;fg87dsfd;kfoA,.iy |
SFID | 18540 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 18539 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
on 17-12-2021 02:24
I'm having the same issues, as are apparently a good chunk of the customer base judging from the amount of posts I'm seeing on the forums.
I really do hope they can sort the issues out for me, gaming has been so useful to connect with people since I'm more compromised health wise and avoid leaving the house unnecessarily due to current events.
Think I'll be taking this to the press with how widespread the issues are, I've already been talking with a few editors about it.
on 17-12-2021 02:36
Time Priority Description
Tue 19/10/2021 16:03:32 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 20/10/2021 09:48:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 23/10/2021 04:03:32 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 23/10/2021 04:03:32 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 25/10/2021 14:34:31 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 26/10/2021 01:24:36 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 27/10/2021 21:18:54 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 27/10/2021 21:18:55 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 29/10/2021 20:56:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 30/10/2021 10:49:57 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 01/11/2021 12:09:15 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 03/11/2021 21:32:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 03/11/2021 21:32:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 03/11/2021 23:25:54 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 08/11/2021 17:01:59 | 4 | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 08/11/2021 17:02:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 08/11/2021 17:02:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 10/11/2021 11:25:16 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 11/11/2021 13:16:59 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 11/11/2021 13:16:59 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 13/11/2021 14:39:23 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 14/11/2021 17:54:27 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 14/11/2021 17:54:28 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 15/11/2021 15:48:20 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 16/11/2021 03:28:39 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/11/2021 16:51:22 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/11/2021 16:51:23 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 20/11/2021 01:45:56 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 21/11/2021 23:53:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 21/11/2021 23:53:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 22/11/2021 07:08:29 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 25/11/2021 11:53:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 25/11/2021 11:53:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 26/11/2021 12:01:28 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 28/11/2021 23:53:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 28/11/2021 23:53:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 29/11/2021 16:59:05 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 02/12/2021 11:53:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 02/12/2021 11:53:01 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 04/12/2021 23:31:36 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 05/12/2021 23:53:01 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 05/12/2021 23:53:02 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 06/12/2021 21:59:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 07/12/2021 20:14:12 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 10/12/2021 10:03:39 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 10/12/2021 10:03:40 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 11/12/2021 05:12:33 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/12/2021 11:28:29 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 17-12-2021 07:13
I'll leave pod or booster issues to others, as they're not something I know about, and my preferred wifi solution is to take all of it out of VM's hands and do the job properly, but that costs money.
On the connection quality, there's a couple of things - first the possible impact of the latest work from home guidance which means that whilst this lasts there's a lot more problems (for some areas) on the upstream side of VM's network, creating latency problems that affect gamers, any Teams/Zoom/Skype types of use, and live streaming. There's not much VM can do about that, as its a result of the network not being designed for this pattern of usage, and changing that would take far longer than the current issues will last. VM are improving capacity all the time, but it's a long, slow technically complicated task, and not something they can suddenly accelerate or deliver to every affected area.
The second thing is that it looks to me like the power levels may be out, as the DOCSIS 3.1 power level looks to me far too high relative to the D 3.0 channels, and those are a bit variable to boot. This can be addressed, but I'm not sure whether the Fisher Price diagnostics that VM use will recognise that pattern of power level problems, and if they don't you'll need a staff member who can interpret the numbers - wait and see what the forum staff have to say.
on 19-12-2021 12:56
Hello @akashmash,
Welcome to the community, thanks for posting.
I am sorry for the issues with your broadband.
Are you using any 3rd party devices?
Many thanks,
New around here? To find out more about the Community check out our Getting Started guide
on 19-12-2021 13:16
Hi Hayley,
Nope, Hub 4 + 2 wifi pods. Seeing people post very similar issues to mine on the forums and elsewhere daily now, getting worried that it's not something that you can fix quickly.