cancel
Showing results for 
Search instead for 
Did you mean: 

High ping and Latency issues Hub 3

mitt0
Joining in

As of recent I have been having ping spikes which last approximately 2 seconds at random intervals when gaming. Typically my internet runs fine but when playing games that is when it seems to struggle

a269466f4f3f12626e271dbeb1dfe304.png

Where the spikes are shown is typically when I am playing games and having issues with my connection, some more extreme than others.

Contacting the helpline did not help in any way, they got me to do a speed test and as everything was fine at the time of test my internet is fine. I have gone through all the diagnostics I am aware of, I have downloaded every app I can, I have a wifi booster. I am beginning to lose hope and I am close to changing provider.

Network Log

Time Priority Description

23/01/2020 17:29:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2020 20:46:54ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2020 08:17:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2020 12:10:22ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2020 21:54:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2020 23:42:59ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 03:33:54ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 16:46:3noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 20:41:30Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 20:42:30noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 20:43:42Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 20:50:16noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 21:04:44Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2020 01:44:39noticeSW Download INIT - Via Config file
29/01/2020 01:47:46noticeSW download Successful - Via Config file
29/01/2020 07:22:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 09:50:55ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2020 06:53:9ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 03:05:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Upstream bonded channels

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

1394000215.1512064 qam6
2461999675.1512064 qam5
3326001255.1512064 qam7
4258000055.075512064 qam8

 

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

1483000000-0.237256 qam30
2187000000-3.535256 qam7
3195000000-435256 qam8
4203000000-3.935256 qam9
5211000000-3.735256 qam10
6219000000-3.736256 qam11
7227000000-3.936256 qam12
8235000000-3.736256 qam13
9243000000-3.236256 qam14
10251000000-2.536256 qam15
11259000000-2.536256 qam16
12267000000-2.536256 qam17
13275000000-2.536256 qam18
14283000000-2.236256 qam19
15291000000-1.736256 qam20
16299000000-1.236256 qam21
17307000000-137256 qam22
18315000000-0.737256 qam23
19323000000-0.736256 qam24
20443000000-0.737256 qam25
21451000000-0.737256 qam26
22459000000-0.737256 qam27
23467000000-0.737256 qam28
24475000000-0.537256 qam29

If any more information is needed please let me know! Help is needed! I'm losing hope!

Many thanks,

Alex

 

21 REPLIES 21

Hi PHB,

 

Thanks for your post and reaching out to the community forums. Are you able to advise further on your set up? Are you using a VOIP phone and is it connected by ethernet, also are you connecting through a VPN?

 

Cheers,

Corey C

2020-04-20_11-55-59.jpgHi

I have a Draytek Vigor 2860 behind the Virgin 3 configured in modem mode.  This is a typical ping from the DaryteK

Hi PHB,

 

Thanks for coming back to us. 

 

From checking the back office systems, I can see there is a congestion issue in your area. The fault reference is F007908422 and the estimated fix date for this is the 13th May 2020.

 

Kind regards,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

Malik007
Joining in

Hi 

Can someone please provide me with some support, I'm having huge issues with latency. 

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/9fb30777a3d87ee0017c532c790c6f0f44410967-03-02-2021

 

Malik007
Joining in
03/02/2021 16:16:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 13:06:27ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2021 18:13:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 09:25:37ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 01:56:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/01/2021 21:25:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/01/2021 22:37:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2021 09:25:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 19:17:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2021 21:25:33ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 18:54:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2021 09:25:33ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2021 07:38:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2021 02:31:15ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2021 01:40:0noticeSW download Successful - Via NMS
09/01/2021 01:37:38noticeSW Download INIT - Via NMS
08/01/2021 14:03:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2021 03:19:51ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/01/2021 05:36:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Upstream bonded channels

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

15370000047.3512064 qam2
23940000047512064 qam4
36030000047512064 qam1
44620000047.3512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0020
3ATDMA0030
4ATDMA0000

Downstream bonded channels

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

11390000007.537256 qam1
21470000007.437256 qam2
31550000006.837256 qam3
41630000006.837256 qam4
5171000000737256 qam5
61790000006.937256 qam6
7187000000737256 qam7
8195000000737256 qam8
9203000000737256 qam9
10211000000737256 qam10
11219000000737256 qam11
12227000000737256 qam12
132350000006.837256 qam13
142430000006.437256 qam14
152510000005.937256 qam15
162590000006.537256 qam16
172670000007.437256 qam17
182750000007.637256 qam18
19283000000837256 qam19
202910000008.137256 qam20
212990000008.337256 qam21
223070000008.337256 qam22
233150000008.537256 qam23
243230000008.537256 qam24



Downstream bonded channels

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

1Locked37.3610
2Locked37.6870
3Locked37.6700
4Locked37.32120
5Locked37.3890
6Locked37.6870
7Locked37.3890
8Locked37.38214
9Locked37.3740
10Locked37.3890
11Locked37.3680
12Locked37.3605
13Locked37.37313
14Locked37.31290
15Locked37.6860
16Locked37.3930
17Locked37.3930
18Locked37.6600
19Locked37.6740
20Locked37.3590
21Locked37.31150
22Locked37.6610
23Locked37.6570
24Locked37.6910

reddwarf4ever
Superfast
I’d you find a solution, my son has e a fly the same issue
Thanks

reddwarf4ever
Superfast

Did you find a solution, my son has exactly the same problem

thanks

@reddwarf4ever you could do worse than create your own thread for this issue to avoid confusion, but in a nutshell, if it is a case of over utilisation causing high latency issues, then, short term, there is no solution other than leaving VM and finding another supplier.