Menu
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
225 Views
Message 1 of 7
Flag for a moderator

Random Latency issues

Hi all,

For the past while now I've been having constant latency and ping issues with my internet. This has been seen most in Rocket League where it tells you when you're having problems, as well as being blaring obvious when you rubber band everywhere. My ping generally sits around 28-32 however at random points of the game and random points of the day, even into 1am, I will suddenly have latency and packet loss and my ping will fluctuate between 30 and 70. This will happen about 10 times every hour but its hard to say.. It happens A LOT. 

This isn't just recently because of the COD series x downloads either, this has been so persistent I've had to move my pc to the edge of my desk facing backwards so I have the wi-fi antenna's facing the router, which is directly underneath my room. 
Ethernet is not possible period.

Speed tests tend to show my speeds being around 250-290 depending on time of day on a 350 package. 

Doing ping tests to google has shown anywhere between 17-202ms using CMD when I'm being affected by it. 
Some days I can get by without many at all to where it isn't an issue, and other days there is no point in playing because it feels like I have 300 ping.

I have tried restarting the SH and my PC but neither have an effect. I am using wifi off an Ubit Intel ax200. 

I set up a BQM before but it suddenly got disabled? Since re-enabling it I have just got a red bar which is apparently ICMP blocked, I can't find how on the SH3 to enable Advanced settings > Tools > Ping - 'WAN Ping Respond', 'Respond to ICMP echo requests sent to WAN IP' as there are no options.

When I have more issues tonight I shall get some tracert to google and pings as evidence, I haven't saved any prior. 

Doing the service checkers and everything on the website and hub apparently report no issues...

0 Kudos
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
171 Views
Message 2 of 7
Flag for a moderator

Re: Random Latency issues

Pinging google.com [216.58.210.46] with 32 bytes of data:
Reply from 216.58.210.46: bytes=32 time=28ms TTL=119
Reply from 216.58.210.46: bytes=32 time=27ms TTL=119
Reply from 216.58.210.46: bytes=32 time=24ms TTL=119
Reply from 216.58.210.46: bytes=32 time=36ms TTL=119
Reply from 216.58.210.46: bytes=32 time=28ms TTL=119
Reply from 216.58.210.46: bytes=32 time=33ms TTL=119
Reply from 216.58.210.46: bytes=32 time=31ms TTL=119
Reply from 216.58.210.46: bytes=32 time=244ms TTL=119
Reply from 216.58.210.46: bytes=32 time=26ms TTL=119
Reply from 216.58.210.46: bytes=32 time=25ms TTL=119
Reply from 216.58.210.46: bytes=32 time=23ms TTL=119
Reply from 216.58.210.46: bytes=32 time=19ms TTL=119
Reply from 216.58.210.46: bytes=32 time=32ms TTL=119
Reply from 216.58.210.46: bytes=32 time=30ms TTL=119
Reply from 216.58.210.46: bytes=32 time=41ms TTL=119
Reply from 216.58.210.46: bytes=32 time=36ms TTL=119
Reply from 216.58.210.46: bytes=32 time=32ms TTL=119
Reply from 216.58.210.46: bytes=32 time=28ms TTL=119
Reply from 216.58.210.46: bytes=32 time=44ms TTL=119
Reply from 216.58.210.46: bytes=32 time=35ms TTL=119
Reply from 216.58.210.46: bytes=32 time=31ms TTL=119
Reply from 216.58.210.46: bytes=32 time=28ms TTL=119
Reply from 216.58.210.46: bytes=32 time=18ms TTL=119
Reply from 216.58.210.46: bytes=32 time=37ms TTL=119
Reply from 216.58.210.46: bytes=32 time=29ms TTL=119
Reply from 216.58.210.46: bytes=32 time=25ms TTL=119
Reply from 216.58.210.46: bytes=32 time=37ms TTL=119
Reply from 216.58.210.46: bytes=32 time=33ms TTL=119
Reply from 216.58.210.46: bytes=32 time=36ms TTL=119
Reply from 216.58.210.46: bytes=32 time=26ms TTL=119

Ping statistics for 216.58.210.46:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 244ms, Average = 37ms

C:\Users\harry>tracert google.com

Tracing route to google.com [216.58.210.46]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 ^C
C:\Users\harry>
C:\Users\harry>tracert www.google.com

Tracing route to www.google.com [216.58.212.228]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * ^C
C:\Users\harry>tracert www.google.co.uk

Tracing route to www.google.co.uk [216.58.213.3]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 51 ms 48 ms 85 ms ber01s14-in-f3.1e100.net [216.58.213.3]

Trace complete.

Currently this is what I'm getting at the moment, literally unplayable from 22:30 

0 Kudos
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
166 Views
Message 3 of 7
Flag for a moderator

Re: Random Latency issues

Downstream bonded channels

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

12990000003.236256 qam21
2139000000335256 qam1
31470000002.535256 qam2
41550000002.735256 qam3
51630000002.736256 qam4
61710000002.536256 qam5
71790000002.536256 qam6
81870000002.736256 qam7
91950000002.736256 qam8
102030000002.536256 qam9
112110000002.536256 qam10
122190000002.536256 qam11
132270000002.236256 qam12
142350000002.436256 qam13
152430000002.436256 qam14
162510000002.436256 qam15
172590000002.536256 qam16
182670000002.536256 qam17
192750000002.536256 qam18
202830000002.736256 qam19
21291000000337256 qam20
223070000003.436256 qam22
23315000000437256 qam23
243230000003.936256 qam24



Downstream bonded channels

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

1Locked36.3300
2Locked35.740950519
3Locked35.7589311231
4Locked35.7757501816
5Locked36.336579533
6Locked36.31449162
7Locked36.3588945
8Locked36.36090
9Locked36.3520
10Locked36.3590
11Locked36.3780
12Locked36.6580
13Locked36.3840
14Locked36.3560
15Locked36.3590
16Locked36.3290
17Locked36.6400
18Locked36.6290
19Locked36.6220
20Locked36.6290
21Locked37.3200
22Locked36.6380
23Locked37.3260
24Locked36.635

0

Upstream bonded channels

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

16029998344.5512064 qam1
23940000043512064 qam4
34620000044.5512064 qam3
45370003444.5512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0030
2ATDMA0010
3ATDMA0010
4ATDMA0010



0 Kudos
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
165 Views
Message 4 of 7
Flag for a moderator

Re: Random Latency issues

Network Log

Time Priority Description

13/11/2020 23:17:17noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/11/2020 23:17:12Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/11/2020 04:39:1noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/11/2020 04:39:0ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/11/2020 17:26:8noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/11/2020 00:39:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/11/2020 00:15:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/11/2020 21:40:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/11/2020 21:36:32noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/11/2020 21:36:22Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2020 19:52:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/11/2020 11:37:49noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/11/2020 11:37:49ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/11/2020 06:31:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/11/2020 13:40:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2020 21:15:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2020 10:13:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2020 03:14:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2020 03:14:20criticalReceived 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;
06/11/2020 03:14:11criticalDHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Sadly I got all this info about 30 mins after the above tracert timeouts, tracert after this was giving me 

C:\Users\harry>tracert www.google.co.uk

Tracing route to www.google.co.uk [216.58.212.195]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.0.1
2 11 ms 13 ms 8 ms 10.53.34.73
3 19 ms 12 ms 17 ms croy-core-2a-xe-212-0.network.virginmedia.net [81.96.225.237]
4 * * * Request timed out.
5 18 ms 22 ms 11 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 20 ms 12 ms 11 ms 74-14-250-212.static.virginm.net [212.250.14.74]
7 13 ms 12 ms 13 ms 108.170.246.161
8 18 ms 21 ms 17 ms 209.85.252.181
9 15 ms 17 ms 10 ms ams16s21-in-f3.1e100.net [216.58.212.195]

Trace complete.
Bet I'm not lagging anymore...

0 Kudos
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
118 Views
Message 5 of 7
Flag for a moderator

Re: Random Latency issues

Got this today during some spikes in the game.

Tracing route to www.google.com [216.58.204.4]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.0.1
2 11 ms 14 ms 53 ms 10.53.34.73
3 40 ms 34 ms 17 ms croy-core-2a-xe-1012-0.network.virginmedia.net [82.2.243.141]
4 * * * Request timed out.
5 27 ms 53 ms 59 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 29 ms 14 ms 22 ms 74-14-250-212.static.virginm.net [212.250.14.74]
7 87 ms 46 ms 73 ms 74.125.242.97
8 54 ms 36 ms 24 ms 64.233.175.107
9 22 ms 21 ms 21 ms lhr48s21-in-f4.1e100.net [216.58.204.4]

Trace complete.

C:\Users\harry>tracert www.google.com

Tracing route to www.google.com [216.58.204.4]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.0.1
2 20 ms 35 ms 70 ms 10.53.34.73
3 54 ms 16 ms 11 ms croy-core-2a-xe-1012-0.network.virginmedia.net [82.2.243.141]
4 * * * Request timed out.
5 25 ms 20 ms 33 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 36 ms 37 ms 22 ms 74-14-250-212.static.virginm.net [212.250.14.74]
7 41 ms 36 ms 23 ms 74.125.242.97
8 37 ms 32 ms 38 ms 64.233.175.107
9 23 ms 41 ms 22 ms lhr48s21-in-f4.1e100.net [216.58.204.4]

0 Kudos
Reply
Highlighted
  • 22
  • 0
  • 0
On our wavelength
76 Views
Message 6 of 7
Flag for a moderator

Re: Random Latency issues

Restarted my Router the other week to refresh data

So far issues are persisting and I have seen this 

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

1Locked36.6660
2Locked36.3244059
3Locked36.3124142
4Locked36.61359144
5Locked36.31850
6Locked36.32280
7Locked36.61460
8Locked36.31330
9Locked36.3520
10Locked36.6660
11Locked36.31100
12Locked36.6650
13Locked36.6860
14Locked36.3760
15Locked36.6850
16Locked36.6560
17Locked36.6530
18Locked36.6460
19Locked37.6560
20Locked36.6520
21Locked37.3360
22Locked36.6370
23Locked37.3300
24Locked36.631

0

 

I have no seen the upstream drop below 64qam and the DB level stays around 36 when I have looked.. 

I have had since 3 T3 timeouts.

0 Kudos
Reply
Highlighted
  • 4.35K
  • 739
  • 1.77K
Very Insightful Person
Very Insightful Person
15 Views
Message 7 of 7
Flag for a moderator

Re: Random Latency issues

You've been posting BQM's and stats in other people's threads - you'd be better off posting them in this thread, as it's extremely difficult to respond to multiple issues in one thread, so (as a rule) people interjecting with "I have that too" will not get a successful response.  It's your lucky day, so I will respond, it'll help others if you can post a link to a shared, live graph of your BQM here.

Judging by that BQM posted in another thread you've probably got a noise issue, which is also evident in the network log errors and the uncorrected error count (post-RS) in your downstream stats.  You've also got a collection of T3 timeouts showing against all upstream channels.  Noise issues can usually be resolved.  Something else that my eyes believed they saw in that BQM was a strong hint of marginal over-utilisation.  As it is marginal there's a fair chance that it will settle down as the game and console release season passes, and as (hopefully) the world returns to normal with less homeworking, but obviously there's no guarantees.  Because there's been a significant outbreak of over-utilisation problems, VM will struggle to address them all, and any that are deemed transient and VM hope will disappear over the next few months will certainly see no action to resolve them (and indeed, these newer instances probably aren't even formally recognised as a utilisation problem, and if that's the case won't even have a fault number).

So, if you can persuade the forum staff to look into the post-RS and upstream errors (they do look at all threads, taking several days at the moment) they may send a technician, who should be able to slice away a lot of the random spikes, but that hint of marginal utilisation is almost certainly a "wait and see" matter. With a bit of luck it will melt away, but don't enter a new fixed term contract whilst there's any connection problem continuing - and upgrading your bandwidth ("speed") won't improve latency.  Worst case is that the latency problem remains, and in that situation the only fix is a new ISP.

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