Menu
Reply
PhilDuck
  • 6
  • 0
  • 1
Tuning in
457 Views
Message 1 of 11
Flag for a moderator

Huge ping spikes while gaming

Sometime around October 2021 my internet went down for just over a day. I was told on the phone they had recevied calls from others in the area and someone would be fixing it which they did. Since then I have had huge ping spikes in games most noteably Rocket League where its makes the game literally unplayable at times.

I use a Wired Connection & have also replaced all ethernet cables just incase, also done the basic stuff like restarting the router etc.

I have called twice to get this sorted but haven't gotten anywhere. The first guy I spoke to changed my wifi settings (still not sure why as I mentioned it was happening on a wired connection). So I had to spend an hour resetting all my alexa devices after that.

Second person I spoke to said something about noise and sending a ping or something to my deivce which could take 48 hours but I still have the problem. Included below are the thinkbroadband graphs.

Thinkbroadband graph & live link + router status infomation I see other people post but if there's anything else you need let me know.

TBB.png

https://www.thinkbroadband.com/broadband/monitoring/quality/share/89d47fa5ea723f1e7b2675dfbd57b56865...

Downstream bonded channels

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

14110000000.938256 qam1
24190000000.938256 qam2
34270000000.238256 qam3
44350000000.438256 qam4
5443000000-0.238256 qam5
64510000000.238256 qam6
7459000000038256 qam7
84670000000.538256 qam8
9475000000038256 qam9
104910000000.238256 qam11
114990000000.238256 qam12
125070000000.238256 qam13
135150000000.238256 qam14
145230000000.438256 qam15
15531000000038256 qam16
165390000000.238256 qam17
17547000000038256 qam18
185550000000.538256 qam19
195630000000.238256 qam20
205710000000.238256 qam21
21579000000038256 qam22
22587000000038256 qam23
235950000000.438256 qam24



Downstream bonded channels

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

1Locked38.656909723949
2Locked38.941391117548
3Locked38.936139418576
4Locked38.633146746272
5Locked38.630554317018
6Locked38.624115746189
7Locked38.621778437180
8Locked38.620030143669
9Locked38.622368016232
10Locked38.620055923577
11Locked38.619881522418
12Locked38.620179543607
13Locked38.613848622455
14Locked38.910862623487
15Locked38.610104842178
16Locked38.97805440534
17Locked38.96443439564
18Locked38.64819934633
19Locked38.63960738949
20Locked38.63785733662
21Locked38.62692532451
22Locked38.62359731209
23Locked38.62115429758

 

Upstream bonded channels

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

13940000044.5512064 qam4
24620000045512064 qam3
35370000045.5512064 qam2
46030000046512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00280
2ATDMA00180
3ATDMA00250
4ATDMA00340

 

Tags (1)
0 Kudos
Reply
PhilDuck
  • 6
  • 0
  • 1
Tuning in
456 Views
Message 2 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Network Log

Time Priority Description

14/01/2022 12:45:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2022 09:15:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2022 00:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2022 00:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:52:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 23:49:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 00:33:30noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 00:33:30ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 21:36:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 12:33:28noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 12:33:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 10:03:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 00:33:28noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 00:33:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/12/2021 13:09:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 12:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 12:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2021 23:08:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Hayley_S
  • 3.9K
  • 129
  • 255
Forum Team (Retired)
Forum Team (Retired)
377 Views
Message 3 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Hello @PhilDuck,

Welcome, thanks for posting.

I am sorry for any issues with your Hub.

I located your account, I can see you have not rebooted your Hub in a very long time. Can you please do this for me? 

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
PhilDuck
  • 6
  • 0
  • 1
Tuning in
367 Views
Message 4 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Hi Hayley,

Thanks for the reply.

I restarted my router twice a few weeks after the problem occured (so late october) once was using the interface on the 192.168.0.1 and once was just fully unplugging it from the wall for 30 seconds. I have rebooted it again for you though.

 

Adduxi
  • 6.09K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
348 Views
Message 5 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

That BQM is indicative I think of a noisy line.  Check the PostRS errors after you reboot your Hub.  If the numbers rise rapidly, there is an issue and a VM technician will need to fix it.  Ideally there should be no PostRS errors at all.

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
PhilDuck
  • 6
  • 0
  • 1
Tuning in
342 Views
Message 6 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Thanks for the reply!

I had a look and since the reboot yesterday i've had 19PostRS errors.

Posted all the logs again.

Downstream bonded channels

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

15550000000.938256 qam19
24110000000.938256 qam1
3419000000138256 qam2
44270000000.538256 qam3
54350000000.538256 qam4
6443000000038256 qam5
74510000000.438256 qam6
8459000000038256 qam7
94670000000.538256 qam8
10475000000038256 qam9
114830000000.538256 qam10
124910000000.438256 qam11
134990000000.438256 qam12
145070000000.438256 qam13
155150000000.438256 qam14
165230000000.538256 qam15
175310000000.238256 qam16
185390000000.538256 qam17
195470000000.238256 qam18
205630000000.738256 qam20
215710000000.738256 qam21
225790000000.538256 qam22
235870000000.538256 qam23
245950000000.738256 qam24



Downstream bonded channels

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

1Locked38.614219
2Locked38.626340
3Locked38.917950
4Locked38.615250
5Locked38.914460
6Locked38.612630
7Locked38.910250
8Locked38.99040
9Locked38.67850
10Locked38.68620
11Locked38.67440
12Locked38.98080
13Locked38.98620
14Locked38.98280
15Locked38.95270
16Locked38.93990
17Locked38.93480
18Locked38.92750
19Locked38.61930
20Locked38.61180
21Locked38.91170
22Locked38.9850
23Locked38.6430
24Locked38.6330

 

Upstream bonded channels

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

13940000043.5512064 qam4
24620002945512064 qam3
35370002445512064 qam2
46030001245512064 qam1

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA0000

 

0 Kudos
Reply
PhilDuck
  • 6
  • 0
  • 1
Tuning in
341 Views
Message 7 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Network Log

Time Priority Description

18/01/2022 09:24:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2022 17:23:16noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2022 13:18:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2022 12:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2022 12:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2022 06:39:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2022 12:45:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2022 09:15:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2022 00:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2022 00:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:52:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:33:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 12:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 23:49:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 00:33:30noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 00:33:30ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 21:36:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 12:33:28noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 12:33:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 10:03:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Adduxi
  • 6.09K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
328 Views
Message 8 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Your BQM is still not good and even though your stats have 19 errors, just keep an eye on those.  I reckon they will rise across all channels?

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
Kath_F
  • 33.72K
  • 1.3K
  • 2.73K
Forum Team
Forum Team
300 Views
Message 9 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Hi PhilDuck, 

Thanks for coming back to us on this one and for rebooting your router. 

As the post RS errors have come back, the BQM still hasn't settled and I've seen that some of your power levels are outside of the optimal range, we are going to need an engineer to come out as we're not able to fix these remotely for you.

I just need to confirm the address to ensure we are booking the visit on the correct account. I have sent you a private message regarding this. Just click on the little plum envelope at the top right-hand side of the page to access your inbox.


Thanks,
 

Kath_F
Forum Team




New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
PhilDuck
  • 6
  • 0
  • 1
Tuning in
291 Views
Message 10 of 11
Flag for a moderator

Re: Huge ping spikes while gaming

Sent a private message over. Also while im at it, I have posted another paste of the Downstream.

As Adduxi correctly predicated the PostRS errors have been steadily rising from the reboot.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1659000000-0.238256 qam32
2475000000-0.238256 qam9
3483000000038256 qam10
44910000000.238256 qam11
54990000000.238256 qam12
65070000000.538256 qam13
75150000000.438256 qam14
85230000000.538256 qam15
9531000000038256 qam16
10539000000038256 qam17
11547000000-0.238256 qam18
125550000000.238256 qam19
135630000000.538256 qam20
145710000000.538256 qam21
155790000000.738256 qam22
165870000000.538256 qam23
175950000000.538256 qam24
186030000000.538256 qam25
196110000000.238256 qam26
20619000000038256 qam27
21627000000038256 qam28
22635000000038256 qam29
236430000000.238256 qam30
24651000000038256 qam31


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.9255027
2Locked38.64899142
3Locked38.611373403
4Locked38.94248289
5Locked38.93963462
6Locked38.62869262
7Locked38.62846139
8Locked38.61650115
9Locked38.9373780
10Locked38.98949148
11Locked38.96136129
12Locked38.65758449
13Locked38.9736296
14Locked38.9893388
15Locked38.9723171
16Locked38.6166312
17Locked38.6245956
18Locked38.991834
19Locked38.61561131
20Locked38.6644211
21Locked38.91076298
22Locked38.6569386
23Locked38.9595302
24Locked38.91112125
 
0 Kudos
Reply