cancel
Showing results for 
Search instead for 
Did you mean: 

Increased ping times - what is normal / acceptable?

Bilbomacuser
Tuning in

We are on the 350 plan (which when we signed up was the fastest service, for gamers) and we have typically had a ping of around 8-12 ms.  Recently I’ve noticed it to be 18-20ms.   We are still getting good speeds - of around 360 mbps up and 36 mbps down.  The hub 3 is in modem only mode.

The cover of the brown box outside regularly falls of and I keep replacing it - should the box be replaced, and could this be causing issues?

There are some errors showing on the status page:

17/07/2021 23:34:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 20:50:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 20:50:24criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 20:50:24criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 19:23:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2021 19:13:5ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2021 14:21:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/07/2021 05:41:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 14:30:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 09:20:59Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 09:20:57criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 09:20:57Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 08:42:29criticalReceived 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/2021 08:38:8Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 08:38:3criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 08:38:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 08:38:2criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/07/2021 19:51:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/07/2021 02:39:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2021 20:53:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00460
2ATDMA0000
3ATDMA0000
4ATDMA0000
Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.690
2Locked37.6310
3Locked37.6160
4Locked37.6240
5Locked37.6530
6Locked37.6560
7Locked37.3270
8Locked37.3250
9Locked37.6180
10Locked37.3240
11Locked37.6270
12Locked37.6160
13Locked37.6350
14Locked37.370
15Locked37.6340
16Locked37.6300
17Locked37.6230
18Locked37.3300
19Locked37.3470
20Locked37.3310
21Locked37.3350
22Locked36.6560
23Locked36.6980
24Locked36.32720

 

13 REPLIES 13

legacy1
Alessandro Volta

@Ayisha_B wrote:

I have taken a look at the account but have been unable to run through all the diagnostics as you are currently in Modem mode. 


What ones can you run and what ones can't you run? a simple ping the the modem and look at Docsis status is enough short from being able to ping the WAN IP. 

---------------------------------------------------------------

@legacy1 I've done all the checks I needed to now and have responded to the OP.

 

Thank you 😄

Ayisha_B
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


Thanks for the reply. 

just to be clear - we aren’t aware of an outage at our end, is this something that is just affecting performance (ie ping times) rather than the whole service being down?

 

thanks. 

Hi @Bilbomacuser,

 

You may notice performance issues yes but this should improve when services have been restored. 

 

Please monitor and keep us posted.

Ayisha_B
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs