Menu
Reply
Grumpydad
  • 5
  • 0
  • 0
Joining in
302 Views
Message 1 of 8
Flag for a moderator

Latentcy *ping* issues

Hello all,  i'm having issues with my internet. I only use it for gaming on a wired connection and pay for the 500mb package. 

 

While playing games i'm finding my internet is ridiculously unstable i will go from anywhere 9-30ms ping up to the 100s.  even dropping out for microseconds. 

Doing speed checks i can see my internet is all over the place; if i'm lucky i might get near the 500mb i pay for but usually sitting in the 200-400 region with a latency between 9-45ms.

if i time the internet check perfectly I get a a true indication that is causing all my pain while gaming with a latency somewhere between 100-200 and internet not even hitting 100download.  upload being non-existent. 

 

I'm finding getting hold of someone from virgin like looking for a four leaf clover so has anybody else experienced this?  I have a feeling it may be the router which I think is the hub3. And just want some confirmation or ideas before I do the hour long *on-hold* call with customer service to get through to someone. 

0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.95K
Alessandro Volta
274 Views
Message 2 of 8
Flag for a moderator

Re: Latentcy *ping* issues

If possible can you set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the other side of the Hub, it will take a few hours to get any kind of trend showing although you should post the link straight away.

Please post a 'Live Link' to your BQM on here straight away.

Instructions for posting BQM Live Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

In the URL box paste the link you copied and in the ‘text to display’ box write My BQM then click OK - you can post the link straight away.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.95K
Alessandro Volta
273 Views
Message 3 of 8
Flag for a moderator

Re: Latentcy *ping* issues

Can you please

Type 192.168.0.1 (192.168.100.1 in Modem mode) into your browser URL bar and press enter. 

Hub 2 & 3 When the page appears DO NOT LOG IN but click ‘Check Router Status’.

Hub 4 When the page appears LOG IN then Advanced Settings > Tools > Network Status.

Copy and paste the contents of the Downstream, Upstream, Configuration and Network Log tabs onto here, if you get a yellow / straw box warning click the Post button again. Use one post for each tab if you wish.

Please do not use screen grabs.

A Guru will be along soon to decipher the info.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
0 Kudos
Reply
Grumpydad
  • 5
  • 0
  • 0
Joining in
250 Views
Message 4 of 8
Flag for a moderator

Re: Latentcy *ping* issues

Downstream; 

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

14027500002.740256 qam30
22027500005.140256 qam9
32107500004.540256 qam10
42187500004.340256 qam11
52267500004.440256 qam12
62347500004.540256 qam13
72427500004.540256 qam14
82507500004.340256 qam15
92587500004.340256 qam16
10266750000440256 qam17
112747500003.940256 qam18
122827500003.740256 qam19
132907500003.440256 qam20
142987500003.540256 qam21
15306750000340256 qam22
163147500003.240256 qam23
173227500003.540256 qam24
183307500003.440256 qam25
19370750000340256 qam26
203787500002.540256 qam27
213867500002.540256 qam28
223947500002.440256 qam29
234107500002.940256 qam31
244187500002.740256 qam32

 

Upstream; 

 

Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
16029998640.3512064 qam1
23940000441.8512064 qam4
34619999841.8512064 qam3
45370001740.3512064 qam2


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Configuration;

 

General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
dJKDHSUBsgvca69834ncxv987



Primary Downstream Service Flow
SFID13812
Max Traffic Rate575000000
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow
SFID13811
Max Traffic Rate38520000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

Network Log

 

Network LogTime Priority Description
31/12/2020 23:20:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2020 23:20:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2020 17:05:13criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 11:20:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 11:20:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2020 09:36:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 23:20:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 23:20:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 19:38:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 11:20:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 11:20:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/12/2020 11:24:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2020 13:51:38Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2020 13:51:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2020 13:51:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2020 13:51:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2020 13:51:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/12/2020 14:02:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2020 23:20:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2020 23:20:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.95K
Alessandro Volta
245 Views
Message 5 of 8
Flag for a moderator

Re: Latentcy *ping* issues

Can you post the second table from the Downstream tab and a link to your BQM please.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
0 Kudos
Reply
Grumpydad
  • 5
  • 0
  • 0
Joining in
236 Views
Message 6 of 8
Flag for a moderator

Re: Latentcy *ping* issues

Hello, below is everything on the downstream tab. I've got the BQM Running but has only be doing so for an hour. Wouldn't it be better to leave it for a few more hours to get more data or would you prefer it now?

 

May I also ask what your looking for & what the information tells you?   I'm interested to learn a little more about this sort of stuff

 

Downstream bonded channels

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

14027500002.740256 qam30
2202750000540256 qam9
32107500004.440256 qam10
42187500004.340256 qam11
52267500004.440256 qam12
62347500004.540256 qam13
72427500004.540256 qam14
82507500004.140256 qam15
92587500004.140256 qam16
102667500003.940256 qam17
112747500003.740256 qam18
122827500003.740256 qam19
132907500003.440256 qam20
142987500003.440256 qam21
15306750000340256 qam22
163147500003.240256 qam23
173227500003.540256 qam24
183307500003.240256 qam25
193707500002.940256 qam26
203787500002.540256 qam27
213867500002.440256 qam28
223947500002.240256 qam29
234107500002.740256 qam31
244187500002.540256 qam32



Downstream bonded channels

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

1Locked40.950
2Locked40.980
3Locked40.370
4Locked40.980
5Locked40.960
6Locked40.9100
7Locked40.350
8Locked40.950
9Locked40.920
10Locked40.980
11Locked40.340
12Locked40.380
13Locked40.3110
14Locked40.9200
15Locked40.9210
16Locked40.9210
17Locked40.350
18Locked40.950
19Locked40.320
20Locked40.350
21Locked40.980
22Locked40.960
23Locked40.3120
24Locked40.9140
0 Kudos
Reply
Grumpydad
  • 5
  • 0
  • 0
Joining in
230 Views
Message 7 of 8
Flag for a moderator

Re: Latentcy *ping* issues

0 Kudos
Reply
Grumpydad
  • 5
  • 0
  • 0
Joining in
203 Views
Message 8 of 8
Flag for a moderator

Re: Latentcy *ping* issues

Please see the updated BQM graph 

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/36c7646eb9096372da13a72ef30de92ec414af72
0 Kudos
Reply