forumarchive,nothingtosee,
Menu
Reply
icekul
  • 5
  • 0
  • 0
Tuning in
159 Views
Message 1 of 8
Flag for a moderator

High Pings showing packet loss and high latency

Hi - I have recently been getting a lot of inconsistent speeds on the virgin media broadband 200mb connection. I have a virgin media hub 3


Ran several ping tests with various well know IP Addresses using the ping assistance on the virgin media page under advance settings >> tools and got the following statistics. .


Wanted to understand why the packet loss and why the increasing the latency with every single ping? Is there a ping where perhaps we could actually get  100% 

Sending 64bytes and running a series of 10tests for all of the below:

PING 208.67.222.222 (208.67.222.222): 64 data bytes
72 bytes from 208.67.222.222: seq=0 ttl=57 time=20.000 ms
72 bytes from 208.67.222.222: seq=1 ttl=57 time=10.000 ms
72 bytes from 208.67.222.222: seq=2 ttl=57 time=3400.000 ms
72 bytes from 208.67.222.222: seq=3 ttl=57 time=9130.000 ms
--- 208.67.222.222 ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max = 10.000/3140.000/9130.000 ms

 

PING 8.8.8.8 (8.8.8.8): 64 data bytes
72 bytes from 8.8.8.8: seq=0 ttl=117 time=20.000 ms
72 bytes from 8.8.8.8: seq=1 ttl=117 time=10.000 ms
72 bytes from 8.8.8.8: seq=2 ttl=117 time=5870.000 ms
72 bytes from 8.8.8.8: seq=3 ttl=117 time=14530.000 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max = 10.000/5107.500/14530.000 ms

PING 198.153.192.1 (198.153.192.1): 64 data bytes
72 bytes from 198.153.192.1: seq=0 ttl=58 time=10.000 ms
72 bytes from 198.153.192.1: seq=1 ttl=58 time=10.000 ms
72 bytes from 198.153.192.1: seq=2 ttl=58 time=5110.000 ms
72 bytes from 198.153.192.1: seq=3 ttl=58 time=10590.000 ms
--- 198.153.192.1 ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max = 10.000/3930.000/10590.000 ms

PING 1.1.1.1 (1.1.1.1): 64 data bytes
72 bytes from 1.1.1.1: seq=0 ttl=59 time=20.000 ms
72 bytes from 1.1.1.1: seq=1 ttl=59 time=10.000 ms
72 bytes from 1.1.1.1: seq=2 ttl=59 time=3720.000 ms
72 bytes from 1.1.1.1: seq=3 ttl=59 time=8390.000 ms
--- 1.1.1.1 ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max = 10.000/3035.000/8390.000 ms

Tags (2)
0 Kudos
Reply
tehwolf
  • 1.52K
  • 243
  • 367
Superfast
153 Views
Message 2 of 8
Flag for a moderator
Helpful Answer

Re: High Pings showing packet loss and high latency

can you set up a BQM - once set up, find the Live Graph and click "Create Sharing Link" - post that back here.

Next, browse to your hub on  http://192.168.0.1 - don't log in, click Router Status - copy/paste the tables from the Upstream, Downstream and Network Log tabs back to this thread - you'll need multiple posts for this, the info wont all fit into a single one..

icekul
  • 5
  • 0
  • 0
Tuning in
104 Views
Message 3 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

Thank you for your assistance much appreciated.

I got an email from Virgin on Friday saying my wifi has been upgraded. It appears the issues have started since that time.

Link below I had set this up Saturday. Almost appears the connection has gone downhill

https://www.thinkbroadband.com/broadband/monitoring/quality/share/279fd8c5c36f12e7ddcdaf0db8a8bae77391fad0-24-02-2021

 

Downstream Bonded Channels

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

14027500002.238256 qam30
2202750000537256 qam9
32107500004.637256 qam10
42187500004.538256 qam11
52267500004.337256 qam12
62347500004.137256 qam13
7242750000437256 qam14
82507500004.137256 qam15
9258750000437256 qam16
10266750000438256 qam17
112747500003.738256 qam18
122827500003.738256 qam19
132907500003.538256 qam20
142987500003.938256 qam21
15306750000338256 qam22
163147500003.238256 qam23
173227500002.938256 qam24
18330750000338256 qam25
193707500002.938256 qam26
203787500002.738256 qam27
213867500002.538256 qam28
22394750000238256 qam29
234107500001.738256 qam31
244187500001.938256 qam32



Downstream bonded channels

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

1Locked38.630
2Locked37.6550
3Locked37.6340
4Locked38.6150
5Locked37.6130
6Locked37.6100
7Locked37.6110
8Locked37.6110
9Locked37.670
10Locked38.690
11Locked38.690
12Locked38.680
13Locked38.6120
14Locked38.9200
15Locked38.6230
16Locked38.9170
17Locked38.640
18Locked38.6110
19Locked38.930
20Locked38.690
21Locked38.980
22Locked38.9150
23Locked38.6150
24Locked38.9150

 

0 Kudos
Reply
icekul
  • 5
  • 0
  • 0
Tuning in
99 Views
Message 4 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

Upstream bonded channels

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

14620000039.5512064 qam11
23940000039.5512064 qam12
35370000039.5512064 qam10
46030016339.5512064 qam9



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
icekul
  • 5
  • 0
  • 0
Tuning in
98 Views
Message 5 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

Network Log

Time Priority Description

22/02/2021 13:50:36noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2021 23:35:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2021 18:38:46noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2021 19:08:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2021 17:47:45noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2021 17:47:45ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2021 16:38:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2021 05:47:45noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2021 05:47:45ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2021 04:55:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/02/2021 17:47:45noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/02/2021 17:47:45ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/02/2021 21:24:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2021 05:58:11noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2021 05:58:11ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2021 14:43:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2021 07:38:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2021 07:38:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2021 17:41:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2021 16:37:18noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
tehwolf
  • 1.52K
  • 243
  • 367
Superfast
97 Views
Message 6 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

yeah so your BQM looks about perfect 

Nothing wrong with any of your power levels etc. they are all within spec and the logs look pretty clean too..

There have been one or two other comments about worse performance since the upgrade - i don't honestly have much to suggest - it's possible there's a bug in the new firmware that's causing issues, but it's a bit early to say on that..

might be worth doing a full reset of the hub and see how it behaves then - when the hub is switched on, depress the reset button on the back using a paperclip/sim tool for a full, timed, 60 seconds. Do not switch the hub off after doing this, leave it alone for 10 mins to recover and start working again..  

icekul
  • 5
  • 0
  • 0
Tuning in
27 Views
Message 7 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

Hi - thanks for the help so far. 

Tried the router reset and nothing really changed. Same ping tests and same results more or less. 

I have a friend in the vicinity (approx 700m away) with virgin media + same hub 3.0 and software version is the same as well. He tried the same ping tests I ran and he got 100% results back. Which makes the issue more intriguing to me why only certain connections are impacted by these changes

Managed to get through to virgin media and after going through the usual checks they have convinced them to send an engineer out. I will use this ping metric to compare against any changes he does make given the customer service reliance appears to be on just download and upload speeds only.

According to the customer advisor my network is fine given the download and upload speeds are within range but when I pressed about why then would packet losses occur he didn't have the answer apart from engineer visit. So I had to accept it and see how this goes..

Also given the fact only some users are experiencing this issue makes me wonder is their hub 3.0 - which have the notorious puma chipsets or the actual network at fault e.g .maybe capacity issues etc

0 Kudos
Reply
legacy1
  • 15.4K
  • 659
  • 1.51K
Alessandro Volta
18 Views
Message 8 of 8
Flag for a moderator

Re: High Pings showing packet loss and high latency

Its likely down to the firmware...🤐

---------------------------------------------------------------
0 Kudos
Reply