08-05-2022 15:20 - edited 08-05-2022 15:27
Latency spikes on my 350mb line are manic, the large spikes are when I have been playing online on my ps5, download speeds go up and down which is annoying but not as much as this latency issue, I see it is not just me and very widespread so will virgin actually be doing anything about it?
on 08-05-2022 17:56
That looks like an oversubcribed area, and not the same as the recent national LINX "hump".
However, post your power levels and network log for 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 08-05-2022 18:35
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 451000000 | -1 | 38 | 256 qam | 40 |
2 | 267000000 | 0.7 | 38 | 256 qam | 17 |
3 | 275000000 | 0.5 | 38 | 256 qam | 18 |
4 | 283000000 | 0.9 | 38 | 256 qam | 19 |
5 | 291000000 | 0.7 | 38 | 256 qam | 20 |
6 | 299000000 | 0.7 | 38 | 256 qam | 21 |
7 | 307000000 | 0.9 | 38 | 256 qam | 22 |
8 | 315000000 | 0.5 | 38 | 256 qam | 23 |
9 | 323000000 | 0.5 | 38 | 256 qam | 24 |
10 | 331000000 | 0.2 | 38 | 256 qam | 25 |
11 | 339000000 | 0 | 38 | 256 qam | 26 |
12 | 347000000 | 0.2 | 38 | 256 qam | 27 |
13 | 355000000 | -0.2 | 38 | 256 qam | 28 |
14 | 363000000 | -0.2 | 38 | 256 qam | 29 |
15 | 371000000 | 0 | 38 | 256 qam | 30 |
16 | 379000000 | -0.4 | 38 | 256 qam | 31 |
17 | 387000000 | -0.2 | 38 | 256 qam | 32 |
18 | 395000000 | -0.4 | 38 | 256 qam | 33 |
19 | 403000000 | -0.7 | 38 | 256 qam | 34 |
20 | 411000000 | -0.7 | 38 | 256 qam | 35 |
21 | 419000000 | -1 | 38 | 256 qam | 36 |
22 | 427000000 | -0.9 | 38 | 256 qam | 37 |
23 | 435000000 | -1.2 | 38 | 256 qam | 38 |
24 | 443000000 | -1.5 | 38 | 256 qam | 39 |
Channel Locked Status RxMER (dB) Pre RS Errors
1 | Locked | 38.6 | 1 |
2 | Locked | 38.9 | 7 |
3 | Locked | 38.6 | 6 |
4 | Locked | 38.9 | 8 |
5 | Locked | 38.9 | 7 |
6 | Locked | 38.6 | 10 |
7 | Locked | 38.6 | 5 |
8 | Locked | 38.9 | 12 |
9 | Locked | 38.9 | 7 |
10 | Locked | 38.6 | 5 |
11 | Locked | 38.6 | 20 |
12 | Locked | 38.9 | 7 |
13 | Locked | 38.9 | 10 |
14 | Locked | 38.9 | 16 |
15 | Locked | 38.9 | 9 |
16 | Locked | 38.9 | 23 |
17 | Locked | 38.9 | 20 |
18 | Locked | 38.9 | 14 |
19 | Locked | 38.6 | 5 |
20 | Locked | 38.9 | 20 |
21 | Locked | 38.9 | 20 |
22 | Locked | 38.9 | 18 |
23 | Locked | 38.6 | 22 |
24 | Locked | 38.9 | 9 |
on 08-05-2022 18:36
1 | 53699952 | 46.5 | 5120 | 64 qam | 2 |
2 | 39399986 | 46.5 | 5120 | 64 qam | 4 |
3 | 46200043 | 46.5 | 5120 | 64 qam | 3 |
4 | 60299976 | 46.5 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 08-05-2022 18:37
Time Priority Description
08/05/2022 18:34:7 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 10:59:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 07:24:37 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/05/2022 22:45:2 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/05/2022 21:05:24 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/05/2022 07:14:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 09:40:34 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 01:20:18 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 19:44:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 07:34:26 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 04:06:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 20:24:53 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/04/2022 01:01:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/04/2022 20:22:34 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/04/2022 19:10:27 | 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; |
28/04/2022 19:10:27 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/04/2022 13:26:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 23:51:12 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 16:45:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 09-05-2022 08:15
Hub status data looks completely normal (assuming the post-RS errors on the downstream that didn't get pasted are all nil) and the BQM trace looks like an over-utilisation issue. Keep an eye on the hub errors, specifically downstream post-RS, because a reboot clears the error counters - if they build up again it may be a resolvable noise problem.
If it is a utilisation problem, then sometimes VM do resolve these, some areas they don't (or do, but then sell a load more contracts and recreate the problem). Complaining and ask for tech visits won't sort out a utilisation issue, and VM may even insist there's not one by their (low) standards.
Maybe the forum staff can interrogate your hub and see something in connection data that isn't visible to us, and get get that fixed. If they can't see a fault, then based on observing how VM deal with over-utilisation, your options are to tolerate the poor latency or to get another ISP.
on 09-05-2022 08:18
I have rebooted the hub several times over the last week, and the errors still show up
on 09-05-2022 09:47
Pre-RS errors don't matter - they're corrected on the fly by the hub. It's any material number of post-RS errors that you need to worry about.
Timeout errors (T3/T4) can be trouble, but looking at the network log you posted they don't seem to be overly frequent, and on many cable connections you'll find a few crop up.
on 09-05-2022 10:14
Talking to the Virgin media team, same old, same old, being told there is an issue that will get fixed within 24 hours. Heard that so many times. What is the policy in regards finishing contract early if I’m having issues with the service?
on 09-05-2022 12:24
VM normally refuse to let customers leave without paying the big fat early termination charges, although in cases of over-utilisation and/or clear evidence of problems sometimes they'll quietly agree to release without penalty.
If you can make a good, evidence based case of repeated problems (eg BQMs showing similar poor performance over some months) then you could run it through a formal complaint, see what happens. If you get a fob-off resolution, reject the resolution and ask for a deadlock letter, and then escalate the matter to CISAS. Unless you've already got an unresolved complaint with VM that you could escalate, it would probably be six weeks to get it to CISAS. In either case, perhaps another month before they come back with an adjudication, and if in your favour you'd probably still have to give 30 days notice. So it isn't quick if VM choose to fight, depending on circumstances you might choose not to bother, and to review the situation when your fixed term ends.
If you're heading to CISAS, remember that the poor adjudicator knows nothing about your problem, may not be a gamer or techy-savvy. Explain the problem as it affects you carefully, and avoid diagnosing faults with VM's network. Although you and I may have a view on it being over-utilisation, we can't prove that unless VM have admitted it, what you should have evidence of is BQM's showing persistently poor latency at peak times, or showing unreliability, plus anecdotal experience of how this affects any reasonable uses of the connection, and some explanation of how you've tried to get VM to fix it, and the outcomes from that, along with your customer experience in trying to get them to resolve things - say as well how all this makes you feel. I think the relevant "about the problem field" on the CISAS website appears limited to about 1,900 characters including spaces, may be worth typing this out before you start any complaint. Make it easy for the adjudicator to understand the complaint and what you want out of it.