Menu
Reply
Psyh0sis
  • 7
  • 0
  • 0
Tuning in
785 Views
Message 1 of 12
Flag for a moderator

Frustrating high latency for a couple of months now

Is this another over-utilisation issue? I've been constantly getting unstable ping for a couple of months now affecting my calls and gaming. Had the engineer come in a few weeks ago to fix a faulty actuator but the original problems still seems to be there. All the coax cables are secure and did a router reset last evening as well shown by the red line around 8pm in the graph. Also in area 31 as well

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2a59707d422f40cccf73e298f7803da52a...

0 Kudos
Reply
Andrew-G
  • 8.12K
  • 1.35K
  • 3.68K
Very Insightful Person
Very Insightful Person
778 Views
Message 2 of 12
Flag for a moderator
Helpful Answer

Re: Frustrating high latency for a couple of months now

It could involve over-utilisation, but the appalling trace between 12:30 am and 8 am suggests there's a lot more to it than that.  Post the hub's status data (as text, not screenshots) for Downstream, Upstream, Network log and we'll pick through the entrails for any signs from the gods.  

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

Psyh0sis
  • 7
  • 0
  • 0
Tuning in
766 Views
Message 3 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

Downstream bonded channels

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

14990000005.338256 qam12
24750000005.938256 qam9
34830000005.538256 qam10
44910000005.538256 qam11
55070000005.638256 qam13
65150000005.638256 qam14
75230000005.638256 qam15
8531000000638256 qam16
95390000005.538256 qam17
105470000005.438256 qam18
115550000004.838256 qam19
125630000005.538256 qam20
135710000005.438256 qam21
145790000006.138256 qam22
15587000000638256 qam23
165950000006.138256 qam24
176030000005.338256 qam25
186110000005.138256 qam26
196190000004.638256 qam27
206270000005.338256 qam28
216350000005.438256 qam29
226430000005.938256 qam30
236510000005.938256 qam31
246590000005.638256 qam32



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.900
2Locked38.6110
3Locked38.6110
4Locked38.980
5Locked38.900
6Locked38.600
7Locked38.600
8Locked38.950
9Locked38.960
10Locked38.960
11Locked38.600
12Locked38.960
13Locked38.600
14Locked38.960
15Locked38.600
16Locked38.960
17Locked38.600
18Locked38.960
19Locked38.600
20Locked38.950
21Locked38.610
22Locked38.6100
23Locked38.9150
24Locked38.610
0 Kudos
Reply
Psyh0sis
  • 7
  • 0
  • 0
Tuning in
762 Views
Message 4 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

16030007340.5512064 qam1
23939998840.5512064 qam4
34620000440.5512064 qam3
45369998340.5512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
Psyh0sis
  • 7
  • 0
  • 0
Tuning in
760 Views
Message 5 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

Network Log

Time Priority Description

30/12/2020 17:50:0noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2020 20:51:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2020 18:22:32noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2020 18:22:25Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2020 17:49:14noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 05:06:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 00:17:34noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 00:17:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 13:33:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 12:17:33noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 12:17:33ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 01:44:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 00:17:32noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 00:17:32ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/12/2020 03:32:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2020 15:56:17noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2020 15:56:17ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/12/2020 06:56:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2020 19:38:54noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2020 19:38:54ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Andrew-G
  • 8.12K
  • 1.35K
  • 3.68K
Very Insightful Person
Very Insightful Person
707 Views
Message 6 of 12
Flag for a moderator
Helpful Answer

Re: Frustrating high latency for a couple of months now

Unfortunately there's nothing obviously wrong in the hub's stats (as that's usually an easy fix).  My guess is an area SNR fault, but because of the disjointed way that VM's systems work, the automated fault status reporting isn't going to be much use to you.  Sometimes it helps, often it doesn't.  I'll flag this for a staff member to advise - if it is a known fault there should be a fix date, if it isn't known hopefully they can get it passed on to the field technicians to investigate.

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

Psyh0sis
  • 7
  • 0
  • 0
Tuning in
702 Views
Message 7 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

I'm having a technician come round next wednesday, would that be of any help to the problems i'm having? In any case, what would be the next best step forward regarding this?

 

0 Kudos
Reply
Andrew-G
  • 8.12K
  • 1.35K
  • 3.68K
Very Insightful Person
Very Insightful Person
696 Views
Message 8 of 12
Flag for a moderator
Helpful Answer

Re: Frustrating high latency for a couple of months now

All you can do is wait and see.  Some of the field technicians are excellent and really get the full picture and would be able to understand what the BQM is showing (you may need to explain the BQM to them, accepting the joys of social distancing).  Others may just go through the motions of checking the hub's SNR and power levels, and regard that as an adequate job.

Be suspicious if they replace your hub - that's usually a cop-out when they don't know what's wrong, because it would be quite exceptional for a hub to be displaying normal stats yet be implicated in worsening latency.  As I say, my money's on an area fault of some type.

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

Psyh0sis
  • 7
  • 0
  • 0
Tuning in
676 Views
Message 9 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

Here's another graph from yesterday which was a bit better but there was still some crazy unstable ping spikes between 6-8pm, was wondering if you could spot any other trends here. In the case one would want to switch ISPs, is there any you would recommend for better latency?

https://www.thinkbroadband.com/broadband/monitoring/quality/share/96537506bbecbc0f107f6d7ec07756cd00c06e50-31-12-2020

 

0 Kudos
Reply
Andrew-G
  • 8.12K
  • 1.35K
  • 3.68K
Very Insightful Person
Very Insightful Person
662 Views
Message 10 of 12
Flag for a moderator

Re: Frustrating high latency for a couple of months now

It's possible that the continuous noise implied by the BQM is disguising an over-utilisation problem.  If that is the case then the best advice has to be to change ISP, because VM's track record on over-utilisation is very disappointing.  But that's jumping the gun, and I'd wait and see what the technician can do, and if the forum staff choose to comment before making any moves.

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

0 Kudos
Reply