cancel
Showing results for 
Search instead for 
Did you mean: 

Poor latency

fenixriot
On our wavelength

D3C4F0D0-B487-492E-9C1A-E93EC6E613A3.jpeg

 

 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?

9 REPLIES 9

Adduxi
Very Insightful Person
Very Insightful Person

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

fenixriot
On our wavelength

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1451000000-138256 qam40
22670000000.738256 qam17
32750000000.538256 qam18
42830000000.938256 qam19
52910000000.738256 qam20
62990000000.738256 qam21
73070000000.938256 qam22
83150000000.538256 qam23
93230000000.538256 qam24
103310000000.238256 qam25
11339000000038256 qam26
123470000000.238256 qam27
13355000000-0.238256 qam28
14363000000-0.238256 qam29
15371000000038256 qam30
16379000000-0.438256 qam31
17387000000-0.238256 qam32
18395000000-0.438256 qam33
19403000000-0.738256 qam34
20411000000-0.738256 qam35
21419000000-138256 qam36
22427000000-0.938256 qam37
23435000000-1.238256 qam38
24443000000-1.538256 qam39



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors

1Locked38.61
2Locked38.97
3Locked38.66
4Locked38.98
5Locked38.97
6Locked38.610
7Locked38.65
8Locked38.912
9Locked38.97
10Locked38.65
11Locked38.620
12Locked38.97
13Locked38.910
14Locked38.916
15Locked38.99
16Locked38.923
17Locked38.920
18Locked38.914
19Locked38.65
20Locked38.920
21Locked38.920
22Locked38.918
23Locked38.622
24Locked38.99

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
15369995246.5512064 qam2
23939998646.5512064 qam4
34620004346.5512064 qam3
46029997646.5512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log

Time Priority Description

08/05/2022 18:34:7noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/05/2022 10:59:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/05/2022 07:24:37noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2022 22:45:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2022 21:05:24noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/05/2022 07:14:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 09:40:34noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 01:20:18Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 19:44:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 07:34:26noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 04:06:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 20:24:53noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 01:01:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/04/2022 20:22:34noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/04/2022 19:10:27noticeDHCP 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:27ErrorDHCP 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:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/04/2022 23:51:12noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/04/2022 16:45:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

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.

I have rebooted the hub several times over the last week, and the errors still show up

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.

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?

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.