15-10-2021 15:52 - edited 15-10-2021 15:55
I've just gotten broadband in my new home and I just want to make sure everything seems ok with my latency. I noticed my ping in online games is a tad higher than others I've seen. I've setup a BQM and had it running for the day. I can see a big spike at 12pm which I'm unsure about but I also noticed my ping seems to sit around 25ms. This seems a little higher from what I've seen from others in the UK on Virgin Media. Any other information needed to see if my connection I'll be happy to send through. Thanks!
on 15-10-2021 16:28
Looks normal to me. The minimum latency is partly driven by your location - how much signal processing goes on on your local circuit (typically related to distance from head of the local coax network) and how far you are geographically from the Thinkbroadband test servers, which I seem to recall are in London. There's also an overhead depending on internet traffic routing, which can vary depending on a multitude of factors.
All things considered the minimum and average latency are pretty good, your main concern is ping spiking. There's one or two visible, but at the implied rate of peaks they aren't anything to worry about.
on 15-10-2021 17:32
Thanks for the information! I've run speed tests to servers close to me and I get around 20-30ms which seems weird to me but I'm not very knowledgeable on the issue. Is there any way to check if my routing is good or if there's a way to lower my latency?
on 15-10-2021 20:25
Internet traffic routing can be deduced from a tracert command in Windows, but you'd have to rely on others to explain the details it will produce. Even if that shows up a slow hop, there's nothing a customer can do to change that because traffic routing is all handled by network wizards hidden so deep in the bowels of VM that they've never met a customer, and have only heard of daylight as an unproven rumour. Sometimes network changes occur that we don't see and your latency may improve, but that's a bit of straw clutching.
In terms of thing you could do for improving your latency, nothing obvious that I can see. SOMETIMES the Hub 4 that's provided for 1 Gbps contracts produces better and lower latency than a Hub 3, but not reliably so. I'd not recommend taking a 1 Gig contract in the hope of improving your ping.
If a few ms are really important, then an Openreach VDSL connection would usually save you a few ms compared to VM, but I'm unconvinced the difference would be material for most gamers, other than those whose VM connection is subject to congestion problems. Considering that your minimum response time to an on-screen stimulus is 250ms, shaving 4-9ms of your average latency (and thus half of that off the ping) isn't going to be perceivable.
on 28-10-2021 12:59
I've been keeping an eye on the BQM and I've noticed there's a bit of dropped packets at the top and I was wondering if this is something that needs fixing or not.
on 29-10-2021 09:20
Packet loss is always a bad thing. And your BQM is currently showing some very unhealthy spikes around 4:45pm and 5:15pm yesterday.
Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts.
on 30-10-2021 13:55
Here are my Hub stats:
1 | 331000000 | 3.5 | 40 | 256 qam | 25 |
2 | 203000000 | 2 | 40 | 256 qam | 9 |
3 | 211000000 | 1.7 | 40 | 256 qam | 10 |
4 | 219000000 | 1.7 | 40 | 256 qam | 11 |
5 | 227000000 | 1.9 | 40 | 256 qam | 12 |
6 | 235000000 | 1 | 40 | 256 qam | 13 |
7 | 243000000 | 1.4 | 40 | 256 qam | 14 |
8 | 251000000 | 1.7 | 40 | 256 qam | 15 |
9 | 259000000 | 2 | 40 | 256 qam | 16 |
10 | 267000000 | 3 | 40 | 256 qam | 17 |
11 | 275000000 | 2.5 | 40 | 256 qam | 18 |
12 | 283000000 | 2.7 | 40 | 256 qam | 19 |
13 | 291000000 | 3.4 | 40 | 256 qam | 20 |
14 | 299000000 | 2.9 | 40 | 256 qam | 21 |
15 | 307000000 | 2.7 | 40 | 256 qam | 22 |
16 | 315000000 | 2 | 40 | 256 qam | 23 |
17 | 323000000 | 2.2 | 40 | 256 qam | 24 |
18 | 339000000 | 3.7 | 40 | 256 qam | 26 |
19 | 347000000 | 4 | 40 | 256 qam | 27 |
20 | 355000000 | 3.7 | 40 | 256 qam | 28 |
21 | 363000000 | 3.2 | 40 | 256 qam | 29 |
22 | 371000000 | 3.7 | 40 | 256 qam | 30 |
23 | 379000000 | 3.5 | 40 | 256 qam | 31 |
24 | 387000000 | 3.5 | 40 | 256 qam | 32 |
1 | Locked | 40.3 | 233 | 0 |
2 | Locked | 40.9 | 243 | 1 |
3 | Locked | 40.3 | 218 | 1 |
4 | Locked | 40.3 | 259 | 2 |
5 | Locked | 40.3 | 279 | 1 |
6 | Locked | 40.3 | 312 | 0 |
7 | Locked | 40.9 | 329 | 0 |
8 | Locked | 40.9 | 262 | 2 |
9 | Locked | 40.3 | 229 | 0 |
10 | Locked | 40.9 | 267 | 0 |
11 | Locked | 40.3 | 212 | 0 |
12 | Locked | 40.3 | 196 | 0 |
13 | Locked | 40.3 | 241 | 0 |
14 | Locked | 40.9 | 256 | 1 |
15 | Locked | 40.3 | 287 | 7 |
16 | Locked | 40.9 | 290 | 7 |
17 | Locked | 40.3 | 260 | 1 |
18 | Locked | 40.9 | 215 | 0 |
19 | Locked | 40.9 | 159 | 0 |
20 | Locked | 40.9 | 150 | 0 |
21 | Locked | 40.9 | 127 | 0 |
22 | Locked | 40.9 | 83 | 0 |
23 | Locked | 40.3 | 117 | 0 |
24 | Locked | 40.3 | 118 | 0 |
Upstream bonded channels
1 | 25799988 | 44.3 | 5120 | 64 qam | 6 |
2 | 32600000 | 44.3 | 5120 | 64 qam | 5 |
3 | 39399964 | 44.3 | 5120 | 64 qam | 4 |
4 | 46199993 | 45.8 | 5120 | 64 qam | 3 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 30-10-2021 13:55
29/10/2021 13:56:54 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 13:54:26 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 13:54:21 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 13:54:21 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 13:54:21 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 13:54:20 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:08:42 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:06:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:06:42 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:06:41 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:39 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:33 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:33 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:33 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:31 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:31 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 12:05:28 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 10:37:33 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 10:37:33 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/10/2021 05:08:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 31-10-2021 23:08
Levels are all perfectly normal. A temporary connection problem around mid-day on 29th but otherwise all OK.
on 03-11-2021 09:08
Hi Adam13337, thanks for the message. As Jpeg1 has said, the ping looks normal, can you confirm if you are having any issues with the service since posting? ^Chris