Menu
Reply
  • 2
  • 0
  • 1
stoddy1989
Settling in
134 Views
Message 1 of 8
Flag for a moderator

Random Ping Spikes

I have seen some similar post but also wanted to get mine checked out too. My issue is as follows 

On average I get around 16-25ms ping but every 30 seconds I get a spike from 100-200ms causing gaming to jitter.

I have attached my ping test to google dns servers and also my router stats. 

My current setup is Superhub 3.0 in Modem mode plugged into an archer TPlink C3200 I on average get 25Mbps download speeds hope this helps.

 

Downstream bonded channels Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID

1306750000-2.440.9256 qam14
2322750000-240.3256 qam16
3314750000-240.3256 qam15
4298750000-2.738.9256 qam13
5290750000-338.6256 qam12
6282750000-3.238.9256 qam11
7274750000-3.240.3256 qam10
8266750000-338.9256 qam9
9258750000-2.740.3256 qam8
10250750000-3.240.3256 qam7
11242750000-338.9256 qam6
12234750000-2.938.9256 qam5
13226750000-2.940.3256 qam4
14218750000-2.540.3256 qam3
15210750000-240.3256 qam2
16202750000-240.3256 qam1

 

Cable Modem Status Item Status Comments

Acquired Downstream Channel(Hz)
306750000
Locked
Ranged Upstream Channel(Hz)
39400000
Locked
Provisioning State
Online

 

Upstream bonded channels Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

239400000ATDMA53.316 qam64000005120
146200000ATDMA53.316 qam64000005120

Network Log Date And Time Error Number Event Description

2017-03-24 22:09:32.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:09:32.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:09:32.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:09:38.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:09:52.0082000400Received 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;
2017-03-24 22:16:16.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:18:20.0068000100DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-24 22:19:00.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:02:56.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:02:57.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:02:57.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:02:57.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:03:03.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:03:32.0082000400Received 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;
2017-03-29 23:08:12.0084020100Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:08:26.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:12:48.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:12:49.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:15:00.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-29 23:15:39.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

ping google DNSping google DNS

0 Kudos
Reply
  • 9.88K
  • 323
  • 854
legacy1
Hero
105 Views
Message 2 of 8
Flag for a moderator

Re: Random Ping Spikes

  • 39
  • 0
  • 8
Stoddy27
On our wavelength
74 Views
Message 3 of 8
Flag for a moderator

Re: Random Ping Spikes

Hi

 

When you say known issue  what is the known issue ? 

 

Thanks in advance.

0 Kudos
Reply
  • 39
  • 0
  • 8
Stoddy27
On our wavelength
74 Views
Message 4 of 8
Flag for a moderator

Re: Random Ping Spikes

thanks for your reponse when you say this is a known problem - what is the known problem ? Is it a problem with the modem ?

0 Kudos
Reply
  • 577
  • 10
  • 50
DarkBahamut
Fibre optic
68 Views
Message 5 of 8
Flag for a moderator

Re: Random Ping Spikes

It's an issue with the chipset running too much work on it's CPU, then when a maintenance job runs it take priority and causes packet handling to be delay. There is a firmware fix coming, but no confirmed dates for it to be rolled out yet. I'd expect likely a couple of months at least till a full public rollout happens realistically.

  • 39
  • 0
  • 8
Stoddy27
On our wavelength
62 Views
Message 6 of 8
Flag for a moderator

Re: Random Ping Spikes

Thanks DarkBahamut - I can't believe I was not informed when I called up about this and was made to feel like it was my internal equipment. 

 

Does anyone know if I can plug my old SH2 in and it will work or would VM have to change something at their end ?

0 Kudos
Reply
  • 577
  • 10
  • 50
DarkBahamut
Fibre optic
58 Views
Message 7 of 8
Flag for a moderator

Re: Random Ping Spikes

First line support on the phone isn't very good unfortunately. For more technical issues like this they often don't really know what's going on. I even see forum support (which is often far more competent) even still trying to send engineers to people that are clearly just suffering from the SH3 firmware issue. There seems to be an unwillingness to actually say that the hardware has an issue, even though it long since been confirmed by the manufacturers of the equipment.

If you wish to swap modems you will need to contact VM over the phone as the modems are registered so only the one linked to your account will provision onto the network. Depending on what package you are on they may resist, but it seems most people do manage to get support to swap the modems over.

Just one consideration to have is that using a SH2 may lead to other issues. It only connects to 8 channels and therefore is more susceptible to utilisation issues and reduced speeds during peak hours (this is why VM want more people on the SH3). If your area has historically been free of congestion faults then it might not effect you too much, but if you area has load issues then you may find peak speeds - and in turn latency even worse in the evenings. 

  • 39
  • 0
  • 8
Stoddy27
On our wavelength
53 Views
Message 8 of 8
Flag for a moderator

Re: Random Ping Spikes




DarkBahamut wrote:

First line support on the phone isn't very good unfortunately. For more technical issues like this they often don't really know what's going on. I even see forum support (which is often far more competent) even still trying to send engineers to people that are clearly just suffering from the SH3 firmware issue. There seems to be an unwillingness to actually say that the hardware has an issue, even though it long since been confirmed by the manufacturers of the equipment.

If you wish to swap modems you will need to contact VM over the phone as the modems are registered so only the one linked to your account will provision onto the network. Depending on what package you are on they may resist, but it seems most people do manage to get support to swap the modems over.

Just one consideration to have is that using a SH2 may lead to other issues. It only connects to 8 channels and therefore is more susceptible to utilisation issues and reduced speeds during peak hours (this is why VM want more people on the SH3). If your area has historically been free of congestion faults then it might not effect you too much, but if you area has load issues then you may find peak speeds - and in turn latency even worse in the evenings. 


Perfect - My area is usually not too badly affected by slow downs so I may give it ago once again thanks for your quick response I believe firmware has been released now for the PUMA chipset lets hope its rolled out fast.

Really annoying playing online games.

0 Kudos
Reply