on 08-06-2022 20:27
Afternoon,
It seems like im getting issues with high ping randomly while my friends experience no issue at all.
I have the Hub 3.0, would it be worth buying a new router ?
on 09-06-2022 13:48
BQM :
https://www.thinkbroadband.com/broadband/monitoring/quality/share/150a49b184bd76131da0ad5771f79340483e585a-09-06-2022
<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/150a49b184bd76131da0ad5771f79340483e585a-09-06-2022">My Broadband Ping</a>
10-06-2022 15:13 - edited 10-06-2022 15:14
Your BQM is showing either, a lot of noise on the line, or over utilisation. A new Router will not cure any of those faults.
Post the power levels, Pre and PostRS errors and network log from the Hub. Once done we can comment.
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 10-06-2022 15:25
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.4 | 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.2 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 62 | 0 |
2 | Locked | 38.9 | 77 | 0 |
3 | Locked | 38.6 | 76 | 0 |
4 | Locked | 38.6 | 96 | 0 |
5 | Locked | 38.6 | 84 | 0 |
6 | Locked | 38.6 | 73 | 13 |
7 | Locked | 38.9 | 49 | 0 |
8 | Locked | 38.6 | 68 | 0 |
9 | Locked | 38.6 | 59 | 0 |
10 | Locked | 38.9 | 76 | 0 |
11 | Locked | 38.9 | 70 | 0 |
12 | Locked | 38.9 | 57 | 0 |
13 | Locked | 38.6 | 65 | 0 |
14 | Locked | 38.6 | 62 | 0 |
15 | Locked | 38.6 | 45 | 0 |
16 | Locked | 38.6 | 68 | 0 |
17 | Locked | 38.6 | 65 | 0 |
18 | Locked | 38.6 | 87 | 34 |
19 | Locked | 38.6 | 64 | 0 |
20 | Locked | 37.6 | 97 | 0 |
21 | Locked | 37.6 | 108 | 0 |
22 | Locked | 38.6 | 87 | 0 |
23 | Locked | 38.6 | 117 | 0 |
24 | Locked | 38.6 | 97 | 0 |
Time Priority Description
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; |
30/05/2022 00: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; |
30/05/2022 00:41:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/05/2022 23:11:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/05/2022 12:41:11 | 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; |
26/05/2022 12:41:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/05/2022 19:30:28 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/05/2022 00:41:11 | 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; |
on 10-06-2022 18:35
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 |
1 | ATDMA | 0 | 0 | 3 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 4 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
https://www.thinkbroadband.com/broadband/monitoring/quality/share/d854996cd9c16adca7cf3c9e9d4bbb58b6810e5a
on 13-06-2022 09:00
Hi BrandonViM,
Thank you for your posts and welcome to our forums 🙂
I am sorry you are having some packet loss and ping spikes.
I have checked our systems and you are affected by a congestion outage, the estimated fix date for this is 08 JUL 2022 15:10.
Thanks,
Zoie