Menu
Reply
NeilRG42
  • 64
  • 1
  • 6
Dialled in
604 Views
Message 1 of 25
Flag for a moderator

Ping Spikes / Packet Loss

Hi guys - Over the past 2 weeks I have been experiencing high ping spikes and packet loss.

My ping to BBC.co.uk (as an example) can spike up to 400ms for a period of 10 seconds and then return back to 20ms. I have a 300mb connection, wired directly to the SuperHub.

I guess this is down to the VM network being saturated due to everyone being at home. Nevertheless, I would appreciate it if you could look into my issues.

I am in Area 31 (Bracknell).

Thanks,

Neil.

0 Kudos
Reply
Kippies
  • 12.44K
  • 859
  • 3.72K
Very Insightful Person
Very Insightful Person
576 Views
Message 2 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Go to 192.168.0.1 in your browser, or 192.168.100.1 if in modem mode

 

Do NOT LOG IN

 

hub31.jpg

 

Post your upstream, downstream and network metrics from your HUB.

 

shub32.png

 

 

 

Screen captures are nice, C&P will do though.

 

Someone will get a look for you.

 

 

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

NeilRG42
  • 64
  • 1
  • 6
Dialled in
534 Views
Message 3 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Here we go;

Downstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
14430000003.540256 qam5
24110000003.738256 qam1
34190000003.940256 qam2
44270000003.740256 qam3
54350000003.740256 qam4
6451000000340256 qam6
74590000002.538256 qam7
84670000002.740256 qam8
9475000000240256 qam9
104830000002.740256 qam10
114910000002.540256 qam11
124990000002.940256 qam12
135070000002.540256 qam13
145150000002.740256 qam14
155230000001.938256 qam15
165310000002.540256 qam16
175390000002.238256 qam17
185470000002.238256 qam18
195550000002.440256 qam19
205630000002.238256 qam20
215710000001.738256 qam21
225790000001.538256 qam22
235870000001.238256 qam23
245950000000.538256 qam24

 

Downstream bonded channels    
ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked40.372180
2Locked38.953820
3Locked40.359510
4Locked40.369930
5Locked40.372940
6Locked40.380800
7Locked38.9103760
8Locked40.9110820
9Locked40.3134400
10Locked40.9142600
11Locked40.3162460
12Locked40.3183030
13Locked40.3179700
14Locked40.3206180
15Locked38.9228080
16Locked40.3254440
17Locked38.9289700
18Locked38.6303850
19Locked40.3304390
20Locked38.9312940
21Locked38.6381860
22Locked38.9434850
23Locked38.9436620
24Locked38.6560310

 

Upstream bonded channels     
ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
1393999934.025512064 qam4
2462000094.175512064 qam3
3536999914.025512064 qam2
4602999474.025512064 qam1
      
      
Upstream bonded channels     
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log  
TimePriorityDescription
04/04/2020 21:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/04/2020 21:22Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01Warning!ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/04/2020 05:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/04/2020 04:17noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/04/2020 04:17ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/04/2020 00:21ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/04/2020 20:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/04/2020 12:32ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/04/2020 04:01criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/03/2020 20:47ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 22:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:18Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:18Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:16criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:13Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2020 01:13Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Kippies
  • 12.44K
  • 859
  • 3.72K
Very Insightful Person
Very Insightful Person
529 Views
Message 4 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

The spread of power levels isnt great, and theres a lot of  PRERS errors.

Do a tracert to BBC.co.uk

Take the first IP that responds (usually the second on the tracert)

Run a continuous ping to it for a bit and see what happens.

 

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

NeilRG42
  • 64
  • 1
  • 6
Dialled in
516 Views
Message 5 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Firstly - thanks for your help! Results of tracert  and continuous ping are as follows;

So my tracert to BBC.co.uk is as follows;

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 62 ms 23 ms 29 ms 10.8.28.1
3 24 ms 74 ms 64 ms winn-core-2b-xe-832-0.network.virginmedia.net [62.253.122.197]
4 * * * Request timed out.
5 24 ms 64 ms 35 ms eislou2-ic-3-ae0-0.network.virginmedia.net [94.174.238.226]
6 14 ms 16 ms 18 ms 157.52.127.6
7 21 ms 20 ms 27 ms 151.101.0.81

Continuous ping to 10.8.28.1 results in timeouts.

Continuous ping to hop 3;

C:\Users\Gaming> ping 62.253.122.177 -t

Pinging 62.253.122.177 with 32 bytes of data:
Reply from 62.253.122.177: bytes=32 time=95ms TTL=62
Reply from 62.253.122.177: bytes=32 time=13ms TTL=62
Reply from 62.253.122.177: bytes=32 time=25ms TTL=62
Reply from 62.253.122.177: bytes=32 time=48ms TTL=62
Reply from 62.253.122.177: bytes=32 time=76ms TTL=62
Reply from 62.253.122.177: bytes=32 time=30ms TTL=62
Reply from 62.253.122.177: bytes=32 time=114ms TTL=62
Reply from 62.253.122.177: bytes=32 time=14ms TTL=62
Reply from 62.253.122.177: bytes=32 time=89ms TTL=62
Reply from 62.253.122.177: bytes=32 time=100ms TTL=62
Reply from 62.253.122.177: bytes=32 time=61ms TTL=62
Reply from 62.253.122.177: bytes=32 time=181ms TTL=62
Reply from 62.253.122.177: bytes=32 time=78ms TTL=62
Reply from 62.253.122.177: bytes=32 time=19ms TTL=62
Reply from 62.253.122.177: bytes=32 time=110ms TTL=62
Reply from 62.253.122.177: bytes=32 time=68ms TTL=62
Reply from 62.253.122.177: bytes=32 time=72ms TTL=62
Reply from 62.253.122.177: bytes=32 time=11ms TTL=62
Reply from 62.253.122.177: bytes=32 time=17ms TTL=62
Reply from 62.253.122.177: bytes=32 time=20ms TTL=62

0 Kudos
Reply
Kippies
  • 12.44K
  • 859
  • 3.72K
Very Insightful Person
Very Insightful Person
497 Views
Message 6 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Most likely a fault on your segment. Ill flag for staff, see if we can get an engineer visit arranged.

 

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

NeilRG42
  • 64
  • 1
  • 6
Dialled in
468 Views
Message 7 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Hi Kippies,

Thank you so much for your help on this, it's really appreciated. Should I expect contact from someone at VM on this forum regarding an Engineer visit?

 

0 Kudos
Reply
Corey_C
  • 3.43K
  • 185
  • 269
Forum Team
Forum Team
461 Views
Message 8 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Hi NeilRG42,

 

Thanks from posting and @Kippies for flagging. Will send you a PM now.

 

Cheers,

Corey C

Corey_C
  • 3.43K
  • 185
  • 269
Forum Team
Forum Team
415 Views
Message 9 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Cheers NeilRG42,

 

I've got the job scheduled for you. I've PM'ed you the time/date. You can also view/reschedule this appointment online here virg.co/TzKOI

 

Thanks,

Corey C

NeilRG42
  • 64
  • 1
  • 6
Dialled in
413 Views
Message 10 of 25
Flag for a moderator

Re: Ping Spikes / Packet Loss

Thanks, Corey!

Fantastic service! Cheers guys!

0 Kudos
Reply