Menu
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
338 Views
Message 1 of 16
Flag for a moderator

Latency problems at nights

For the last few weeks I have experience massive spikes in ping .  After around 7pm at night I cannot do much as the ping shoots through the roof with ping around 350 and jitter around 40.  Tried using mesh system and putting my HUB4 into modem mode still the same.  Tried wifi and ethernet connection , still the same.   Does not seem to be modem or router problems as only happens after a certain time each day.  Can someone please have a look I am running out of patience for the price I pay for 1gig and  its useless.

Tags (1)
0 Kudos
Reply
paultechy
  • 19.74K
  • 1.74K
  • 4.32K
Very Insightful Person
Very Insightful Person
326 Views
Message 2 of 16
Flag for a moderator
Helpful Answer

Re: Latency problems at nights

would suggest setting up https://www.thinkbroadband.com/broadband/monitoring/quality to monitor the performance, to see how bad it is..
Would need to check the signal levels if could go to http://192.168.0.1 or if using modem mode http://192.168.100.1 clicking router status top right or bottom of page depending on hub [no need to login - depending on hub] and if could copy/paste the downstream, upstream, network log, don't worry about the formatting we can easily read it.. try and avoid using screen shots..

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
jbrennand
  • 22.33K
  • 2.4K
  • 3.98K
Very Insightful Person
Very Insightful Person
325 Views
Message 3 of 16
Flag for a moderator

Re: Latency problems at nights

Can you set up a BQM so we can see the issue...
__________________________________

Set up a free and secure “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph” (as per instructions on the TB website) when it starts to develop.

https://www.thinkbroadband.com/broadband/monitoring/quality

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router +2 Airport Express's. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
323 Views
Message 4 of 16
Flag for a moderator

Re: Latency problems at nights

Cheers here they are

3.0 Downstream channels

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

253310000004.69999740.366287QAM25625
11390000007.09999840.366287QAM2561
21470000007.00000040.366287QAM2562
31550000007.00000040.366287QAM2563
41630000006.59999840.366287QAM2564
51710000006.09999840.366287QAM2565
61790000005.69999740.366287QAM2566
71870000005.69999740.366287QAM2567
81950000005.69999740.366287QAM2568
92030000005.50000040.366287QAM2569
102110000005.40000240.366287QAM25610
112190000005.59999840.946209QAM25611
122270000005.19999740.946209QAM25612
132350000005.00000040.366287QAM25613
142430000004.90000240.366287QAM25614
152510000004.90000238.605377QAM25615
162590000005.09999840.946209QAM25616
172670000005.09999840.366287QAM25617
182750000005.30000340.366287QAM25618
192830000005.50000040.366287QAM25619
202910000005.19999740.946209QAM25620
212990000005.40000240.366287QAM25621
223070000004.80000340.366287QAM25622
233150000004.80000340.366287QAM25623
243230000004.50000040.366287QAM25624
263710000004.00000040.366287QAM25626
273790000003.59999840.366287QAM25627
283870000003.59999840.366287QAM25628
293950000003.40000238.983261QAM25629
304030000003.40000240.366287QAM25630
314110000003.20000140.366287QAM25631
0 Kudos
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
322 Views
Message 5 of 16
Flag for a moderator

Re: Latency problems at nights

3.0 Upstream channels

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

13260000046.2705995120 KSym/sec64QAM5
23940000046.5205995120 KSym/sec64QAM4
34620000046.5205995120 KSym/sec64QAM3
42580000046.0205995120 KSym/sec64QAM6



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
320 Views
Message 6 of 16
Flag for a moderator

Re: Latency problems at nights

Network Log

Time Priority Description

Thu Feb 11 14:53:59 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb 14 12:13:29 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Feb 17 03:56:44 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Feb 18 00:13:30 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:20 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 20 18:28:36 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 20 19:57:13 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 22:46:08 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb 23 15:56:11 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Feb 25 17:59:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb 28 08:51:23 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 1 05:59:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 1 15:28:42 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 4 17:59:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 8 00:48:09 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 8 05:59:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 10 07:22:01 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 10 09:15:04 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 11 15:41:13 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 12 19:37:22 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 17 13:24:48 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 18 23:35:04 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 20 04:21:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 20 14:08:56 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 23 06:20:08 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 23 06:20:39 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 26 18:20:09 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 27 01:14:10 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 27 15:26:55 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 30 17:53:26 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 5 16:57:13 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Apr 6 13:06:50 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 7 04:43:39 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 7 21:34:08 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 8 12:27:31 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 8 21:49:30 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 8 23:31:03 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Apr 10 21:27:53 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:19 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 11 09:44:42 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 11 10:58:53 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 11 21:16:25 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 11; 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;
Sun Apr 11 21:16:27 20213SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 11 21:16:28 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 11 21:16:43 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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;
0 Kudos
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
144 Views
Message 7 of 16
Flag for a moderator

Re: Latency problems at nights

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d5d0ef1b482dace170a7bad25934711ad193c1db-19-04-2021
0 Kudos
Reply
tehwolf
  • 2.11K
  • 363
  • 523
Problem sorter
140 Views
Message 8 of 16
Flag for a moderator

Re: Latency problems at nights


@WinkieB wrote:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/d5d0ef1b482dace170a7bad25934711ad193c1db-19-04-2021

what mesh system do you have, it looks like it's blocking ICMP requests which means the BQM just shows a block of red.. if it's a TP Link Deco then i don't believe that it's a configurable option, so to get a BQM up and running you'll need to put the hub back into router mode (and set the BQM up again, since that'll give you a different public IP address).  If it's a different model, it may be something you can enable.. 

0 Kudos
Reply
WinkieB
  • 9
  • 0
  • 0
Tuning in
132 Views
Message 9 of 16
Flag for a moderator

Re: Latency problems at nights

It is a deco.  Never had problems before but will see if I can remove it for a while 

0 Kudos
Reply
jbrennand
  • 22.33K
  • 2.4K
  • 3.98K
Very Insightful Person
Very Insightful Person
110 Views
Message 10 of 16
Flag for a moderator

Re: Latency problems at nights

TP-Link borked the "respond to pings" option in a recent firmware update to some units (I know that was the case for the Deco M4) and it couldn't actually be selected. Check whether that is the case or that it has been reinstated more recently

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router +2 Airport Express's. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply