Menu
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
870 Views
Message 1 of 10
Flag for a moderator

High Loaded Latency

Hi all,

I have recently found that while online gaming (League/Wow) I have been receiving intermittent spikes in my latency making games unplayable. This has been occurring for around a month and I have noticed whenever completing a speed test my speed is showing as around 240Mbps with unload ping as 11ms, upload ping as 21ms but the loaded showing as 441ms.

The only amended to setup is receiving a Hub4. I have tested this on both wired and wireless devices and receive the same results. Saw some other posts linked think broadband test which I have added below.

https://www.thinkbroadband.com/_assets/speedtest/button/1639130475720505955.png
<a href="https://www.thinkbroadband.com/speedtest/1639130475720505955"><img alt="My Broadband Speed Test" src="https://www.thinkbroadband.com/_assets/speedtest/button/1639130475720505955-mini.png" /></a>

 

Any advice much appreciated.

Tags (1)
0 Kudos
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
853 Views
Message 2 of 10
Flag for a moderator

Re: High Loaded Latency

Saw some posts requesting BQM and Network Status data so posting below.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0c9b678e073dc1541ee9865305e420b9efc4ff8b

 

0 Kudos
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
851 Views
Message 3 of 10
Flag for a moderator

Re: High Loaded Latency

3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
5 171000000 1.9 39 QAM256 5
1 139000000 2.7 38.6 QAM256 1
2 147000000 2.6 38.6 QAM256 2
3 155000000 2.7 38.6 QAM256 3
4 163000000 2.4 39 QAM256 4
6 179000000 1.5 39 QAM256 6
7 187000000 1.3 38.6 QAM256 7
8 195000000 1.2 38.6 QAM256 8
9 203000000 1.2 38.6 QAM256 9
10 211000000 1.1 39 QAM256 10
11 219000000 0.6 38.6 QAM256 11
12 227000000 0.2 38.6 QAM256 12
13 235000000 0 38.6 QAM256 13
14 243000000 0.1 39 QAM256 14
15 251000000 0.3 39 QAM256 15
16 259000000 0.8 38.6 QAM256 16
17 267000000 0.8 39 QAM256 17
18 275000000 0.6 38.6 QAM256 18
19 283000000 0.4 38.6 QAM256 19
20 291000000 0.6 38.6 QAM256 20
21 299000000 0.8 38.6 QAM256 21
22 307000000 1 39 QAM256 22
23 315000000 1.2 39 QAM256 23
24 323000000 1.2 38.6 QAM256 24
25 331000000 1.1 38.6 QAM256 25
26 339000000 1 39 QAM256 26
27 347000000 1.1 38.6 QAM256 27
28 355000000 0.7 38.6 QAM256 28
29 363000000 0.5 38.6 QAM256 29
30 371000000 0.6 38.6 QAM256 30
31 379000000 0.6 39 QAM256 31


3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
5 Locked 38.983261 0 0
1 Locked 38.605377 0 0
2 Locked 38.605377 0 0
3 Locked 38.605377 0 0
4 Locked 38.983261 0 0
6 Locked 38.983261 0 0
7 Locked 38.605377 0 0
8 Locked 38.605377 0 0
9 Locked 38.605377 0 0
10 Locked 38.983261 0 0
11 Locked 38.605377 0 0
12 Locked 38.605377 0 0
13 Locked 38.605377 0 0
14 Locked 38.983261 0 0
15 Locked 38.983261 0 0
16 Locked 38.605377 0 0
17 Locked 38.983261 0 0
18 Locked 38.605377 0 0
19 Locked 38.605377 0 0
20 Locked 38.605377 0 0
21 Locked 38.605377 0 0
22 Locked 38.983261 0 0
23 Locked 38.983261 0 0
24 Locked 38.605377 0 0
25 Locked 38.605377 0 0
26 Locked 38.983261 0 0
27 Locked 38.605377 0 0
28 Locked 38.605377 0 0
29 Locked 38.605377 0 0
30 Locked 38.605377 0 0
31 Locked 38.983261 0 0


3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
41 96 4K 1880 QAM4096 424


3.1 Downstream channels
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
41 Locked 40 1.1 197224256 0
0 Kudos
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
849 Views
Message 4 of 10
Flag for a moderator

Re: High Loaded Latency

3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 60300000 36.5 5120 KSym/sec 64QAM 1
2 39400000 35.3 5120 KSym/sec 64QAM 4
3 46200000 35.5 5120 KSym/sec 64QAM 3
4 53700000 35.8 5120 KSym/sec 64QAM 2


3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 US_TYPE_STDMA 0 0 1 0
2 US_TYPE_STDMA 0 0 0 0
3 US_TYPE_STDMA 0 0 0 0
4 US_TYPE_STDMA 0 0 0 0

General Configuration
Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cmreg-vmdg640-bbt060-b.cm


Primary Downstream Service Flow
SFID
142800
Max Traffic Rate
230000061
Max Traffic Burst
42600
Min Traffic Rate
0


Primary Upstream Service Flow
SFID
142799
Max Traffic Rate
22000061
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort
0 Kudos
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
849 Views
Message 5 of 10
Flag for a moderator

Re: High Loaded Latency

Network Log
Time Priority Description
Mon 22/11/2021 16:13:34 6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; 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 22/11/2021 16:13:38 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:13:41 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:14:02 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:14:23 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:40 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:45 6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 27; 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 22/11/2021 16:17:46 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:46 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:46 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:46 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:49 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:53 6 CM-STATUS message sent. Event Type Code: 23; Chan ID: 41; 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 22/11/2021 16:17:54 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:17:57 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:18:02 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 16:18:07 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:47 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:52 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:52 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:52 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:53 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:22:56 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:23:03 6 CM-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;
Mon 22/11/2021 17:23:07 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:23:10 6 CM-STATUS message sent. Event Type Code: 23; Chan ID: 41; 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 22/11/2021 17:23:12 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:23:16 6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 17:23:30 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:16:25 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:32:40 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:32:45 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:32:46 6 CM-STATUS message sent. Event Type Code: 21; Chan ID: 41; 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 22/11/2021 23:32:46 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:32:48 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 23:33:07 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 02:57:01 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 04:08:17 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 28/11/2021 04:34:35 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 28/11/2021 08:45:34 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/11/2021 08:08:01 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/11/2021 13:30:06 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 01/12/2021 16:34:35 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 01/12/2021 18:13:39 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 03/12/2021 00:33:04 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 05/12/2021 20:33:47 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Adduxi
  • 6.09K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
827 Views
Message 6 of 10
Flag for a moderator

Re: High Loaded Latency

Stats look okay, but your log shows a number of SYNC timeouts.  Maybe noise on the Upstream?  One for VM to investigate.

You need to setup a BQM, not the speedtests.   www.thinkbroadband.com/ping

Once done we can comment on that as well, but it will take several hours to populate.

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
JonAl
  • 10
  • 0
  • 0
Joining in
824 Views
Message 7 of 10
Flag for a moderator

Re: High Loaded Latency

Thanks for reply,

BQM was setup also above.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0c9b678e073dc1541ee9865305e420b9ef...

I don't know if it needs 24 hours or what but that was the "live link".

0 Kudos
Reply
JonAl
  • 10
  • 0
  • 0
Joining in
821 Views
Message 8 of 10
Flag for a moderator

Re: High Loaded Latency

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0c9b678e073dc1541ee9865305e420b9ef...

sorry link cut off for some reason. This should be the correct BQM link
0 Kudos
Reply
Tom_F
  • 4.22K
  • 250
  • 537
Forum Team (Retired)
Forum Team (Retired)
754 Views
Message 9 of 10
Flag for a moderator

Re: High Loaded Latency

Hi JonAl, thanks for getting in touch.

 

Really sorry to hear about the problems you've had with your broadband, I wasn't able to run any checks using your forum info alone on this occasion - please get back to me via PM (the purple envelope icon) and we'll take a closer look into it for you.

 

Tom

0 Kudos
Reply
Tom_F
  • 4.22K
  • 250
  • 537
Forum Team (Retired)
Forum Team (Retired)
719 Views
Message 10 of 10
Flag for a moderator

Re: High Loaded Latency

Thanks for getting back to me @JonAl, I've arranged an engineer visit which you will find confirmation of online (virg.in/myVM) and can reschedule from there if needed as well.

 

Please let us know how you get on, or if there's anything else we can help with. 

 

Tom

0 Kudos
Reply