Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Constant daily high latency

ckck
Joining in

on ‎09-12-2021 00:35

Hello, as many others in these forums I am experiencing latency variation and high latency when doing anything gaming related. 

I have tried many solutions, changing cables, getting a 3rd party router (UDM), resets, restarts etc. etc. with no resolution yet. 

I've setup a BQM graph linked here: 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b58650c0fddfe157f34371a822007defa6...

Whenever I contact VM it's always a local fault in the area or they can't see anything wrong (that they say is resolved soon after), but there is clearly an issue when it's very single day when using the internet for gaming or similar that the latency spikes. 

I should note I have the hub 4, currently running in modem mode, but doesn't make any difference if in router mode or not. 

0 Kudos
18 REPLIES 18

Adduxi
Very Insightful Person
Very Insightful Person

on ‎09-12-2021 10:39

Unfortunately Thinkbroadband had an issue with the BQM monitors and we'll have to wait for 24 hours to see your populated shared graph.

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

ckck
Joining in
In response to Adduxi

on ‎09-12-2021 22:06

Yeah I see, it seems to be back now and shows some history, is there no way of sharing days back in time of the graph? The history now is not as bad as it has been but still.
0 Kudos

Adduxi
Very Insightful Person
Very Insightful Person
In response to ckck

on ‎10-12-2021 10:01

@ckck wrote:
Yeah I see, it seems to be back now and shows some history, is there no way of sharing days back in time of the graph? The history now is not as bad as it has been but still.

BQM's are stored but AFAIK yon can't share your history, but you can post snapshots from the historical data.

However, your circuit looks like it's affected by minor over utilisation in your area, as it's quiet in the night time and busy over the evening.

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

ckck
Joining in
In response to Adduxi

on ‎10-12-2021 10:04

Hi again. 

Thanks for answering. 
Here is a screenshot of a more normal day:

ckck_1-1639130625946.png

 

Still looks like over utilization to me, is there any way of fixing this? 

 

0 Kudos

hortonj88
Fibre optic
In response to ckck

‎12-12-2021 08:29 - edited ‎12-12-2021 08:29

If it's utilisation then it's a fault out of your control or the forum teams.

 

Forum team will just keep giving you a date that gets pushed back.



Utilisation faults can take years to get fixed and there's no guarantee the fixes last very long.


Your best option would be to terminate and go onto FTTC or FTTP if it's available to you.

Sure FTTC download speeds are slower but the latency is way more stable and consistent which is what matters.



********************************************************
Left Virgin Media in 2020 after being fobbed off one too many times about over utilisation.


Now: BT FTTP 900/110 connected an ASUS RT-AC86U router.


https://www.speedtest.net/result/12098955842.png

Andrew-G
Alessandro Volta
In response to hortonj88

on ‎12-12-2021 09:10

Agree it looks like over-utilisation, but there are occasionally faults that only become apparent when the network is busy, so you might want to post the hub's stats for Downstream, Upstream, Network log, and we might find a resolvable fault. 

0 Kudos

ckck
Joining in
In response to Andrew-G

on ‎13-12-2021 00:04

Thank you. 

I have booked an appointment with a technician to come around Wednesday so have a look at the issue. Hopefully he might be able to do something, but my hopes are not high. 

What exactly do you need of info, just everything that is shown under the Downstream, Upstream and Networklog pages under the menu item "Network status"? 

I will add it in a new response as it exceeds the 20k character limit. 



0 Kudos

ckck
Joining in
In response to Andrew-G

on ‎13-12-2021 00:08

Here are the downstream info, next post is the upstream and network log.

Downstream page: 

3.0 Downstream channels

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

41627500009.739QAM2564
113875000010.739QAM2561
214675000010.238.6QAM2562
31547500009.939QAM2563
51707500009.439QAM2565
61787500009.339QAM2566
71867500009.439QAM2567
81947500009.638.6QAM2568
92027500009.739QAM2569
102107500009.839QAM25610
112187500001039QAM25611
1222675000010.239QAM25612
1323475000010.139QAM25613
142427500001039QAM25614
1525075000010.139QAM25615
1625875000010.439QAM25616
1726675000010.438.6QAM25617
1827475000010.339QAM25618
1928275000010.539QAM25619
2029075000010.838.6QAM25620
2129875000011.439QAM25621
2230675000011.239QAM25622
2331475000011.339QAM25623
2432275000010.939QAM25624
2533075000010.839QAM25625
263387500001139QAM25626
2734675000011.239QAM25627
2835475000011.139QAM25628
2936275000011.639QAM25629
3037075000011.739QAM25630
3137875000011.738.6QAM25631

3.0 Downstream channels

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

4Locked38.98326100
1Locked38.98326100
2Locked38.60537700
3Locked38.98326100
5Locked38.98326100
6Locked38.98326100
7Locked38.98326100
8Locked38.60537700
9Locked38.98326100
10Locked38.98326100
11Locked38.98326100
12Locked38.98326100
13Locked38.98326100
14Locked38.98326100
15Locked38.98326100
16Locked38.98326100
17Locked38.60537700
18Locked38.98326100
19Locked38.98326100
20Locked38.60537700
21Locked38.98326100
22Locked38.98326100
23Locked38.98326100
24Locked38.98326100
25Locked38.98326100
26Locked38.98326100
27Locked38.98326100
28Locked38.98326100
29Locked38.98326100
30Locked38.98326100
31Locked38.60537700

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159964K1880QAM4096759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159Locked3915.7248176744819

 

0 Kudos

ckck
Joining in
In response to ckck

on ‎13-12-2021 00:08

3.0 Upstream channels

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

139400000415120 KSym/sec64QAM4
232600000415120 KSym/sec64QAM5
34620000040.85120 KSym/sec64QAM3
45370000040.85120 KSym/sec64QAM2

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0020
4US_TYPE_STDMA0000

 

 

Network Log

Time Priority Description

Fri 05/11/2021 06:00:486CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 06/11/2021 02:15:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 07/11/2021 10:24:184DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 07/11/2021 10:24:186DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 08/11/2021 10:03:283No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 08/11/2021 12:20:446CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 10/11/2021 22:17:334DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 10/11/2021 22:17:336DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 10/11/2021 23:46:333No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 11/11/2021 20:14:075MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 11/11/2021 20:26:255DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/11/2021 21:15:434DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/11/2021 21:15:446DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/11/2021 11:25:263No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 04:16:414DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 04:16:416DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 07:59:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 09:38:376CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 20:28:265MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 20:40:435DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 19/11/2021 03:48:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 00:22:254DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 00:22:256DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 23/11/2021 17:20:343No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 08:49:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 08:49:346DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 09:05:385Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 09:06:146CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 26/11/2021 19:38:063No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/11/2021 04:38:175MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/11/2021 04:50:335DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/11/2021 08:33:533No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/11/2021 13:47:596CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 29/11/2021 18:43:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
Top