Menu
Reply
dilky2002
  • 4
  • 0
  • 0
Tuning in
236 Views
Message 1 of 6
Flag for a moderator

High latency since upgrading to a better package

We recently moved to the 350mbps package and while the speed stays normally above 300mbps, games have been unplayable with the lag I get most days. Not really sure what I can do.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1fc09f7263693088ed8a885834854fe3bfb8f642

 

 

Tags (1)
0 Kudos
Reply
carl_pearce
  • 4.73K
  • 402
  • 706
Superstar
211 Views
Message 2 of 6
Flag for a moderator

Re: High latency since upgrading to a better package


@dilky2002 wrote:

We recently moved to the 350mbps package and while the speed stays normally above 300mbps, games have been unplayable with the lag I get most days. Not really sure what I can do.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1fc09f7263693088ed8a885834854fe3bf... 

It's a terrible BQM:

carl_pearce_0-1611874617500.png

 

Could you access your router using http://192.168.0.1/ or http://192.168.100.1 for modem mode. Log in, select the 'Advanced settings / Tools / Network status' option and paste your 'Downstream', 'Upstream', and 'Network Log' tabs? Please copy/paste this data as text, split between multiple posts (Sometimes you have to click 'Post' twice due to an error message).

dilky2002
  • 4
  • 0
  • 0
Tuning in
195 Views
Message 3 of 6
Flag for a moderator

Re: High latency since upgrading to a better package

Downstream bonded channels

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

14190000000.240256 qam36
2235000000040256 qam13
32430000000.240256 qam14
4251000000040256 qam15
5259000000040256 qam16
6267000000040256 qam17
7275000000040256 qam18
82830000000.440256 qam19
92910000000.240256 qam20
102990000000.540256 qam21
113070000000.440256 qam22
123150000000.540256 qam23
133230000000.740256 qam24
14331000000140256 qam25
153390000000.740256 qam26
163470000000.440256 qam27
173550000000.240256 qam28
18363000000-0.240256 qam29
19371000000040256 qam30
20379000000-0.240256 qam31
21387000000040256 qam32
22395000000040256 qam33
23403000000040256 qam34
244110000000.440256 qam35



Downstream bonded channels

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

1Locked40.340
2Locked40.360
3Locked40.350
4Locked40.920
5Locked40.340
6Locked40.350
7Locked40.940
8Locked40.930
9Locked40.360
10Locked40.970
11Locked40.950
12Locked40.340
13Locked40.920
14Locked40.960
15Locked40.350
16Locked40.330
17Locked40.960
18Locked40.970
19Locked40.940
20Locked40.3130
21Locked40.960
22Locked40.350
23Locked40.950
24Locked40.350
0 Kudos
Reply
dilky2002
  • 4
  • 0
  • 0
Tuning in
194 Views
Message 4 of 6
Flag for a moderator

Re: High latency since upgrading to a better package

Upstream bonded channels

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

15370004146.5512064 qam2
23940007046.5512064 qam4
34620000246.5512064 qam3
46030006346.5512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network LogTime Priority Description
29/01/2021 00:20:55noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 00:20:49Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:55:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:54:8criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:44:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:43:8criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:35:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:35:17Warning!B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:34:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:28:21criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:27:42Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:27:36criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:27:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:27:36criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:27:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:09:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:09:24Warning!B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:08:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:02:53criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 03:02:14Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
Andruser
  • 5.51K
  • 966
  • 2.27K
Very Insightful Person
Very Insightful Person
136 Views
Message 5 of 6
Flag for a moderator

Re: High latency since upgrading to a better package

There's a lot of timeouts in the log, but power and noise levels look OK: BQM looks as though there may be over-utilisation, but I can't see why that would occur because of a speed increase.  User @jem101 knows more about these things than I do and may be able to comment.

Was the lag there before you upgraded, and if so, how long has it been going on, and what motivated you to upgrade?

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
dilky2002
  • 4
  • 0
  • 0
Tuning in
109 Views
Message 6 of 6
Flag for a moderator

Re: High latency since upgrading to a better package

Before the upgrade just before Christmas i would only really get drops in speed, not latency spikes. We got the upgrade because we were offered sports channels for good value.

From what i remember though i didn't lag when we first upgraded, only really since the new year

0 Kudos
Reply