Menu
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,305 Views
Message 1 of 139
Flag for a moderator

High Latency on 200MB

Since March I've been having high ping spikes.  These have been ranging from 100ms to over 14000ms as seen below. Gaming is a no go and using my work VOIP phone is a pain as is keep cutting out.  I even had an engineer out today and the issue is still not resolved. 

Talking to customer services and Tech support is useless and noone seems to understand the issue grrrrrrrrr 😞   Spoke to a 'Manager' as was told it was due to the IP address, and that they would change the ext IP address, and that this would take 1 hour to complete.  3 hours later I'm still stuck with the same IP address and the same issues.  (Not even sure if changing the IP address would have made a difference anyway).

The ping results were taken from within the VM router settings.

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=30.000 ms
72 bytes from 8.8.8.8: seq=2 ttl=117 time=4180.000 ms
72 bytes from 8.8.8.8: seq=3 ttl=117 time=8560.000 ms
72 bytes from 8.8.8.8: seq=4 ttl=117 time=13180.000 ms
72 bytes from 8.8.8.8: seq=5 ttl=117 time=13000.000 ms
72 bytes from 8.8.8.8: seq=6 ttl=117 time=13520.000 ms
72 bytes from 8.8.8.8: seq=7 ttl=117 time=13640.000 ms
72 bytes from 8.8.8.8: seq=8 ttl=117 time=14010.000 ms
72 bytes from 8.8.8.8: seq=9 ttl=117 time=13600.000 ms
72 bytes from 8.8.8.8: seq=10 ttl=117 time=13430.000 ms
72 bytes from 8.8.8.8: seq=11 ttl=117 time=13830.000 ms
72 bytes from 8.8.8.8: seq=12 ttl=117 time=13710.000 ms
72 bytes from 8.8.8.8: seq=13 ttl=117 time=13990.000 ms
72 bytes from 8.8.8.8: seq=14 ttl=117 time=13000.000 ms
72 bytes from 8.8.8.8: seq=15 ttl=117 time=12270.000 ms
72 bytes from 8.8.8.8: seq=16 ttl=117 time=11700.000 ms
72 bytes from 8.8.8.8: seq=17 ttl=117 time=10740.000 ms
72 bytes from 8.8.8.8: seq=18 ttl=117 time=9800.000 ms
72 bytes from 8.8.8.8: seq=19 ttl=117 time=9420.000 ms
72 bytes from 8.8.8.8: seq=20 ttl=117 time=9820.000 ms
72 bytes from 8.8.8.8: seq=21 ttl=117 time=9820.000 ms
72 bytes from 8.8.8.8: seq=22 ttl=117 time=9850.000 ms
72 bytes from 8.8.8.8: seq=23 ttl=117 time=9900.000 ms
72 bytes from 8.8.8.8: seq=24 ttl=117 time=9920.000 ms
72 bytes from 8.8.8.8: seq=25 ttl=117 time=9680.000 ms
72 bytes from 8.8.8.8: seq=26 ttl=117 time=9970.000 ms
72 bytes from 8.8.8.8: seq=27 ttl=117 time=9910.000 ms
72 bytes from 8.8.8.8: seq=28 ttl=117 time=9910.000 ms
72 bytes from 8.8.8.8: seq=29 ttl=117 time=9950.000 ms
72 bytes from 8.8.8.8: seq=30 ttl=117 time=9970.000 ms
72 bytes from 8.8.8.8: seq=31 ttl=117 time=9940.000 ms
72 bytes from 8.8.8.8: seq=32 ttl=117 time=9460.000 ms
72 bytes from 8.8.8.8: seq=33 ttl=117 time=10300.000 ms
72 bytes from 8.8.8.8: seq=34 ttl=117 time=10140.000 ms
72 bytes from 8.8.8.8: seq=35 ttl=117 time=10500.000 ms
72 bytes from 8.8.8.8: seq=36 ttl=117 time=10340.000 ms
72 bytes from 8.8.8.8: seq=37 ttl=117 time=10440.000 ms
72 bytes from 8.8.8.8: seq=38 ttl=117 time=10230.000 ms
72 bytes from 8.8.8.8: seq=39 ttl=117 time=10140.000 ms
72 bytes from 8.8.8.8: seq=40 ttl=117 time=10390.000 ms
72 bytes from 8.8.8.8: seq=41 ttl=117 time=9880.000 ms
72 bytes from 8.8.8.8: seq=42 ttl=117 time=10020.000 ms
72 bytes from 8.8.8.8: seq=43 ttl=117 time=10170.000 ms
--- 8.8.8.8 ping statistics ---
50 packets transmitted, 44 packets received, 12% packet loss
round-trip min/avg/max = 20.000/10370.000/14010.000 ms

continued below

Anonymous
Not applicable
1,299 Views
Message 2 of 139
Flag for a moderator

Re: High Latency on 200MB

Could you access your router using http://192.168.0.1/ . Don't log in, select the 'Check Router Status' option and paste your 'Downstream', 'Upstream', and 'Network Log' tabs?

0 Kudos
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,298 Views
Message 3 of 139
Flag for a moderator

Re: High Latency on 200MB

Cable Modem Status Item Status Comments

Acquired Downstream Channel (Hz)
475000000
Locked
Ranged Upstream Channel (Hz)
60300000
Locked
Provisioning State
Online
 

 

Downstream bonded channels

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

14750000003.938256 qam31
21950000006.840256 qam8
32030000006.438256 qam9
4211000000638256 qam10
5219000000638256 qam11
62270000005.938256 qam12
72350000005.640256 qam13
82430000005.638256 qam14
92510000005.538256 qam15
102590000005.638256 qam16
112670000005.540256 qam17
122750000005.338256 qam18
132830000005.438256 qam19
142910000005.338256 qam20
152990000005.538256 qam21
163070000005.540256 qam22
173150000005.538256 qam23
183230000005.640256 qam24
194270000004.538256 qam25
204350000004.138256 qam26
214430000003.738256 qam27
22451000000438256 qam28
23459000000438256 qam29
244670000003.938256 qam30



Downstream bonded channels

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

1Locked38.93570
2Locked40.3150
3Locked38.9120
4Locked38.9210
5Locked38.9290
6Locked38.9140
7Locked40.3320
8Locked38.9310
9Locked38.9280
10Locked38.9320
11Locked40.3340
12Locked38.9450
13Locked38.9450
14Locked38.9500
15Locked38.9480
16Locked40.3670
17Locked38.9770
18Locked40.3580
19Locked38.91990
20Locked38.92260
21Locked38.62410
22Locked38.93110
23Locked38.93120
24Locked38.93304

 

Upstream bonded channels

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

1603000003.925512064 qam1
2394000123.775512064 qam4
3462000003.925512064 qam3
4537000003.925512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA000

0

 

 

0 Kudos
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,295 Views
Message 4 of 139
Flag for a moderator

Re: High Latency on 200MB

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
9834ncxv9873254k;fg87dsfd;kfoA



Primary Downstream Service Flow

SFID674
Max Traffic Rate230000061
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID673
Max Traffic Rate22000061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

 

Network LogTime Priority Description
08/07/2020 14:25:40noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 14:23:45Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 12:53:45criticalReceived 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;
08/07/2020 12:52:51Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 12:52:49criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 12:52:49Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 12:52:49criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 12:52:44Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:24:37criticalReceived 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;
08/07/2020 07:24:12Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:24:8criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:23:34criticalReceived 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;
08/07/2020 07:21:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:33criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:31criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:21:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2020 07:20:39criticalReceived 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;



 

0 Kudos
Reply
Anonymous
Not applicable
1,294 Views
Message 5 of 139
Flag for a moderator

Re: High Latency on 200MB

All the above looks ok (Within spec), other than your ping response!

Is this in router or modem mode?

0 Kudos
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,289 Views
Message 6 of 139
Flag for a moderator

Re: High Latency on 200MB

Hi Carl,

Its in Router Mode. Also have tried factory resetting the router but no luck.

wakar.
0 Kudos
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,285 Views
Message 7 of 139
Flag for a moderator

Re: High Latency on 200MB

<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/52a2bed7c92de764494755192c64a5db77e37e85-08-07-2020"><img alt="My Broadband Ping - Home" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/52a2bed7c92de764494755192c64a5db77e37e85-08-07-2020.png" /></a>
0 Kudos
Reply
Anonymous
Not applicable
1,282 Views
Message 8 of 139
Flag for a moderator

Re: High Latency on 200MB

One trick I found to change IP is to put the router in modem mode, leave it to reboot. It will get a different IP.

You can then put it back in router mode however you should keep the new IP!

Remember that when you put the hub in modem mode the local IP will change to 192.168.100.1.

0 Kudos
Reply
waarif
  • 68
  • 1
  • 2
On our wavelength
1,279 Views
Message 9 of 139
Flag for a moderator

Re: High Latency on 200MB

OK thanks i will try that now.

0 Kudos
Reply
Anonymous
Not applicable
1,276 Views
Message 10 of 139
Flag for a moderator

Re: High Latency on 200MB

Note the point above about local IP changing!

0 Kudos
Reply