on 11-06-2022 13:37
Good Afternoon,
Hoping someone could take a look at the below and sus out the issue ?
Is this overutilisation or an issue with the Puma Chipset ?
https://www.thinkbroadband.com/broadband/monitoring/quality/share/d854996cd9c16adca7cf3c9e9d4bbb58b6810e5a
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 195000000 | 2.7 | 38 | 256 qam | 8 |
2 | 139000000 | 5.1 | 38 | 256 qam | 1 |
3 | 147000000 | 4.5 | 38 | 256 qam | 2 |
4 | 155000000 | 3.7 | 38 | 256 qam | 3 |
5 | 163000000 | 3.5 | 38 | 256 qam | 4 |
6 | 171000000 | 3.2 | 38 | 256 qam | 5 |
7 | 179000000 | 3 | 38 | 256 qam | 6 |
8 | 187000000 | 2.9 | 38 | 256 qam | 7 |
9 | 203000000 | 2.5 | 38 | 256 qam | 9 |
10 | 211000000 | 2.4 | 38 | 256 qam | 10 |
11 | 219000000 | 2.4 | 38 | 256 qam | 11 |
12 | 227000000 | 2.2 | 38 | 256 qam | 12 |
13 | 235000000 | 2 | 38 | 256 qam | 13 |
14 | 243000000 | 2 | 38 | 256 qam | 14 |
15 | 251000000 | 2 | 38 | 256 qam | 15 |
16 | 259000000 | 2 | 38 | 256 qam | 16 |
17 | 267000000 | 1.9 | 38 | 256 qam | 17 |
18 | 275000000 | 1.7 | 38 | 256 qam | 18 |
19 | 283000000 | 1.5 | 38 | 256 qam | 19 |
20 | 291000000 | 1.2 | 37 | 256 qam | 20 |
21 | 299000000 | 1.2 | 37 | 256 qam | 21 |
22 | 307000000 | 0.9 | 38 | 256 qam | 22 |
23 | 315000000 | 1 | 38 | 256 qam | 23 |
24 | 323000000 | 1.4 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 75 | 14 | |
2 | Locked | 38.9 | 97 | 0 | |
3 | Locked | 38.6 | 92 | 0 | |
4 | Locked | 38.6 | 108 | 0 | |
5 | Locked | 38.9 | 88 | 0 | |
6 | Locked | 38.6 | 81 | 13 | |
7 | Locked | 38.6 | 80 | 0 | |
8 | Locked | 38.6 | 81 | 0 | |
9 | Locked | 38.6 | 73 | 0 | |
10 | Locked | 38.6 | 80 | 0 | |
11 | Locked | 38.9 | 83 | 0 | |
12 | Locked | 38.6 | 80 | 0 | |
13 | Locked | 38.6 | 68 | 0 | |
14 | Locked | 38.6 | 68 | 0 | |
15 | Locked | 38.6 | 57 | 0 | |
16 | Locked | 38.6 | 73 | 0 | |
17 | Locked | 38.6 | 74 | 0 | |
18 | Locked | 38.9 | 107 | 34 | |
19 | Locked | 38.6 | 84 | 0 | |
20 | Locked | 37.6 | 110 | 0 | |
21 | Locked | 37.3 | 130 | 0 | |
22 | Locked | 38.6 | 94 | 0 | |
23 | Locked | 38.6 | 123 | 0 | |
24 | Locked | 38.9 | 103 | 0 |
on 11-06-2022 14:16
on 11-06-2022 14:17
BQM looks like over utilisation to me. Stats generally okay although you have three downstream channels with some post RS errors which shouldn't really be there.
Check for local issues on 0800 561 0061 and ensure that all cables and connections are tight and secure and not kinked or damaged. Lastly try a 30 second pinhole reset of the hub.
on 12-06-2022 21:57
In terms of actually issue;
Completly unable to play multiplayer games, the ping spikes result in excessive rubber banding,
I.e Red Latency/Packet loss icons appear on BF1, red latency issues appear on AoE2
12/06/2022 20:53:45 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 06:40:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2022 12:34:48 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2022 00:52:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2022 14:22:15 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2022 18:28:29 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2022 13:25:32 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2022 13:25:32 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2022 18:43:51 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2022 04:53:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2022 01:25:32 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2022 01:25:32 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/06/2022 23:25:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/06/2022 14:05:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/06/2022 12:41:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/06/2022 12:41:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 06:15:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Upstream
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200026 | 46.5 | 5120 | 64 qam | 1 |
2 | 25800000 | 45 | 5120 | 64 qam | 4 |
3 | 32600000 | 46.5 | 5120 | 64 qam | 3 |
4 | 39400039 | 46.5 | 5120 | 64 qam | 2 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 3 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 5 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
on 14-06-2022 10:24
Horrendous BQM at the moment, VM will need to send a technician to sort that out. Not much you can do to fix this, you'll just have to wait for VM to do so.
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
on 16-06-2022 17:36
Hey @BrandonViM,
Welcome back to the community and thanks for taking the time to post.
I'm really sorry to hear of the issues that you're having with your connection, I have looked into this and can see that there is currently congestion issues in your area, this has been logged under ticket number F009865331 and the current estimated fix time for this issue is 15.10 on 8th July. We are working on some upgrades to support the increased demand for our services in your area. When completed, any slow broadband speeds and buffering on TiVo apps you may be experiencing (particularly at peak times) will be resolved.
Regards,
Steven_L