on 13-01-2022 21:22
Hi All,
I've been struggling with high latency for months, maybe even years to be honest. We are on the 600mb package and generally speeds are fine but I have a lot of issues when gaming and I also work from home so Teams calls are also an issue at times. We've had various engineers come out who never appear to find anything and we've had multiple aspects of our infrastructure changed to no avail. Below is the last 2 days from the broadband quality monitor:
I've had this running for a while so there's a lot more evidence of +200ms response times. Any advice on what could be the issue? I'll post the upstream, downstream and network log in separate messages
on 13-01-2022 21:24
1 | 195000000 | 2.9 | 37 | 256 qam | 8 |
2 | 139000000 | 3.7 | 37 | 256 qam | 1 |
3 | 147000000 | 3.2 | 37 | 256 qam | 2 |
4 | 155000000 | 3.2 | 37 | 256 qam | 3 |
5 | 163000000 | 3.2 | 37 | 256 qam | 4 |
6 | 171000000 | 3.2 | 37 | 256 qam | 5 |
7 | 179000000 | 3 | 37 | 256 qam | 6 |
8 | 187000000 | 3 | 37 | 256 qam | 7 |
9 | 203000000 | 2.7 | 37 | 256 qam | 9 |
10 | 211000000 | 2.7 | 37 | 256 qam | 10 |
11 | 219000000 | 2.5 | 37 | 256 qam | 11 |
12 | 227000000 | 2.2 | 37 | 256 qam | 12 |
13 | 235000000 | 2 | 37 | 256 qam | 13 |
14 | 243000000 | 1.9 | 37 | 256 qam | 14 |
15 | 251000000 | 2 | 37 | 256 qam | 15 |
16 | 259000000 | 2.2 | 37 | 256 qam | 16 |
17 | 267000000 | 2.4 | 37 | 256 qam | 17 |
18 | 275000000 | 2.4 | 37 | 256 qam | 18 |
19 | 283000000 | 2.4 | 37 | 256 qam | 19 |
20 | 291000000 | 3 | 37 | 256 qam | 20 |
21 | 299000000 | 3.2 | 37 | 256 qam | 21 |
22 | 307000000 | 3.2 | 37 | 256 qam | 22 |
23 | 315000000 | 3 | 37 | 256 qam | 23 |
24 | 323000000 | 3.4 | 38 | 256 qam | 24 |
1 | Locked | 37.3 | 2454 | 128 |
2 | Locked | 37.3 | 5289 | 228 |
3 | Locked | 37.6 | 3427 | 121 |
4 | Locked | 37.3 | 2436 | 251 |
5 | Locked | 37.6 | 2046 | 46 |
6 | Locked | 37.3 | 1983 | 69 |
7 | Locked | 37.3 | 2374 | 13 |
8 | Locked | 37.3 | 2594 | 0 |
9 | Locked | 37.3 | 1517 | 20 |
10 | Locked | 37.3 | 1311 | 0 |
11 | Locked | 37.3 | 7926 | 0 |
12 | Locked | 37.3 | 981 | 0 |
13 | Locked | 37.3 | 1253 | 0 |
14 | Locked | 37.6 | 980 | 2 |
15 | Locked | 37.3 | 983 | 16 |
16 | Locked | 37.3 | 750 | 0 |
17 | Locked | 37.3 | 854 | 12 |
18 | Locked | 37.6 | 772 | 0 |
19 | Locked | 37.3 | 920 | 0 |
20 | Locked | 37.6 | 643 | 0 |
21 | Locked | 37.3 | 688 | 0 |
22 | Locked | 37.6 | 578 | 11 |
23 | Locked | 37.6 | 580 | 26 |
24 | Locked | 38.6 | 422 | 0 |
on 13-01-2022 21:24
1 | 60300000 | 48.5 | 5120 | 64 qam | 1 |
2 | 39400000 | 48 | 5120 | 64 qam | 4 |
3 | 46200000 | 48.5 | 5120 | 64 qam | 3 |
4 | 53700000 | 48.5 | 5120 | 64 qam | 2 |
1 | ATDMA | 0 | 0 | 12 | 0 |
2 | ATDMA | 0 | 0 | 13 | 0 |
3 | ATDMA | 0 | 0 | 11 | 0 |
4 | ATDMA | 0 | 0 | 12 | 0 |
on 13-01-2022 21:25
13/01/2022 21:04:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/01/2022 21:03:42 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/01/2022 13:20:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/01/2022 02:48:14 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/01/2022 02:48:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/01/2022 00:54:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/01/2022 14:48:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/01/2022 14:48:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/01/2022 03:51:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/01/2022 02:48:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/01/2022 02:48:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/01/2022 11:17:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/2022 14:48:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/2022 14:48:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/12/2021 04:20:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/12/2021 02:48:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/12/2021 02:48:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/12/2021 21:14:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/12/2021 14:48:12 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/12/2021 14:48:12 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 13-01-2022 21:29
Not sure if the images I added have upload correctly so I've generated a link for yesterdays BQM:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/5baef4e98dc5d21861f8a207fb3ab314b83696ca-12-01-2022
on 13-01-2022 21:43
Nothing unusual in the network log, downstream power's OK, but too many uncorrectable (post-RS) errors, upstream power's good, but far too many timeouts. I'd wait and see what staff advise, because the BQM looks noisy (which can be fixed) but also to have some characteristics that could be over-utilisation (which generally isn't fixed in any reasonable time scale).
on 16-01-2022 15:45
Hi jamiehunt90,
Thanks for posting and welcome to our community 🙂
I'm sorry to see you're having some issues with your connection,
I've been able to locate your account using your forum details, and can see some of the hubs levels are out of specification. This is something that I'll need to arrange an engineer for.
I'll need a few details from you first, so I've popped you over a private message (purple envelope, top right hand corner)
Alex_Rm
on 04-11-2022 21:31
It's been a while since I posted this and following multiple changes, I'm still struggling with latency issues. The engineer which came out found no issues but suggested we had too many devices (approx. 20) and the Hub3 was not powerful enough so we would likely require a better router. I went out and bought a pair of Asus ZenWiFi AX (XT8) routers which improved the overall Wi-Fi however did not resolve the latency problems. We've since been upgraded to the Hub4 on the Gig1 plan and again still have high latency. I'm currently connected from my PC directly to the Hub4 in modem mode and a simple ping to google.com is all over the place:
I believe over the years we have had every piece of infrastructure change at the property (some multiple times) so is it likely that the issue resides in the cabinet at the end of the street? If so is this something that Virgin would look to investigate? Or is it purely down to limits in the area for shared bandwidth?
on 04-11-2022 23:04
on 07-11-2022 13:39
Hi jamiehunt90,
Thanks for your post and for coming back to us with an update. We're sorry to hear your issues with latency are continuing.
Checking things this end, it looks as though several of your downstream power levels are too high. We won't be able to fix this remotely so I would like to arrange for an engineer to come to take a look at this for you.
I just need to confirm the address to ensure we are booking the visit on the correct account. I have sent you a private message regarding this. Just click on the little plum envelope at the top right-hand side of the page to access your inbox.
Thanks,