Extreme Latency

[MauriceMoss]

Since about mid last month my connection has become worse and worse the latency spikes have gone up and up and have become more frequent, This needs sorting its not suitable for gaming or for work calls when I have these latency spikes which are often a lot worse in the evening.

Here is the info from Network Tools on the Hub 5

Status:

Item Status Comments

Acquired Downstream Channel(Hz)	139000000	Locked
Ranged Upstream Channel(Hz)	49600000	Ranged
Provisioning State	Online	Operational

Downstream:

Downstream bonded channels

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

1	139000000	10	39	QAM 256	1
2	147000000	9.7	39	QAM 256	2
3	155000000	9.6	39	QAM 256	3
4	163000000	9.3	39	QAM 256	4
5	171000000	8.9	39	QAM 256	5
6	179000000	8.9	39	QAM 256	6
7	187000000	8.9	39	QAM 256	7
8	195000000	8.7	39	QAM 256	8
9	203000000	8.4	39	QAM 256	9
10	211000000	8.4	39	QAM 256	10
11	219000000	8.3	39	QAM 256	11
12	227000000	7.9	39	QAM 256	12
13	235000000	7.3	39	QAM 256	13
14	243000000	6.8	39	QAM 256	14
15	251000000	6.6	39	QAM 256	15
16	259000000	6.4	39	QAM 256	16
17	267000000	6.2	39	QAM 256	17
18	275000000	6.3	39	QAM 256	18
19	283000000	6.7	39	QAM 256	19
20	291000000	7.5	40	QAM 256	20
21	299000000	7.5	40	QAM 256	21
22	307000000	7.5	40	QAM 256	22
23	315000000	7.7	40	QAM 256	23
24	323000000	8	40	QAM 256	24
25	331000000	8.1	40	QAM 256	25
26	339000000	8.2	40	QAM 256	26
27	347000000	8	40	QAM 256	27
28	355000000	8.3	40	QAM 256	28
29	363000000	8.4	40	QAM 256	29
30	371000000	8.4	40	QAM 256	30
31	379000000	8.7	40	QAM 256	31

Downstream bonded channels

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

1	Locked	39	874	0
2	Locked	39	845	15
3	Locked	39	792	25
4	Locked	39	804	14
5	Locked	39	820	0
6	Locked	39	825	10
7	Locked	39	807	0
8	Locked	39	804	4
9	Locked	39	844	13
10	Locked	39	827	14
11	Locked	39	759	67
12	Locked	39	797	0
13	Locked	39	807	13
14	Locked	39	786	0
15	Locked	39	802	0
16	Locked	39	778	3
17	Locked	39	783	11
18	Locked	39	804	12
19	Locked	39	962	15
20	Locked	40	751	13
21	Locked	40	705	0
22	Locked	40	701	12
23	Locked	40	604	11
24	Locked	40	604	0
25	Locked	40	575	0
26	Locked	40	636	0
27	Locked	40	588	0
28	Locked	40	605	11
29	Locked	40	566	64
30	Locked	40	522	0
31	Locked	40	487	0

Upstream:

Upstream bonded channels

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

0	49600000	48.5	5120	QAM 64	1
1	43100000	48.5	5120	QAM 64	2
2	36600000	48.5	5120	QAM 64	3
3	30100000	48	5120	QAM 64	4
4	23600000	47.5	5120	QAM 64	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	2	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	2	0

Configuration:

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

1

Enabled

3.1

UBsgvca69834ncxv9873254k;

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

602

1200000450 bps

42600bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

601

110000274 bps

42600bytes

0 bps

42600bytes

Best Effort

Below are the BQM charts for 01/08/2023-15/08/2023

[MauriceMoss]

Network Log

Time Priority Description

15-08-2023 16:48:06	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15-08-2023 16:46:48	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15-08-2023 16:46:48	warning	Dynamic Range Window violation
14-08-2023 05:10:01	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-08-2023 05:09:17	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-08-2023 13:17:02	warning	Dynamic Range Window violation
12-08-2023 13:17:02	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-08-2023 13:17:02	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-08-2023 17:09:35	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-08-2023 17:09:11	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2023 13:21:44	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2023 13:21:33	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2023 13:21:33	warning	Dynamic Range Window violation
08-08-2023 07:11:17	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2023 07:11:06	warning	Dynamic Range Window violation
08-08-2023 07:11:06	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2023 06:27:02	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2023 06:26:31	warning	Dynamic Range Window violation
08-08-2023 06:26:31	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2023 03:56:56	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2023 03:55:04	warning	Dynamic Range Window violation
08-08-2023 03:55:04	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 05:47:03	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 05:46:51	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 05:46:51	warning	Dynamic Range Window violation
07-08-2023 05:09:11	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 05:09:04	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 04:27:05	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-08-2023 04:26:58	warning	Dynamic Range Window violation
07-08-2023 04:26:58	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-08-2023 15:06:22	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-08-2023 15:06:15	warning	Dynamic Range Window violation

[legacy1]

Might be nothing you can do but see if it happens in modem mode when you are idle

[MauriceMoss]

The hub 5 is already in modem mode as it is connect to my unif gear

[legacy1]

Ok see what happens if you rate limit download to 100Mb upload 20Mb use SFQ for QoS if the BQM still shows bad really nothing you can do.

[MauriceMoss]

Forgot to mention in first post this is a Gig1 package.

[legacy1]

Start low then go higher if lower rate limiting still shows Extreme Latency VM will have to fix it

[Ashleigh_C]

Hi there @MauriceMoss 

Thank you so much for your post and welcome back to the community forums, it's great to have you here. 

I am so sorry to hear that you have faced this issue with your service and thank you to our community for their help so far.

I can see that the Hub has been up for around a month, would you be able to try a pin hole reset? To do this push a pen etc into the reset hole and hold in for 60 seconds. 

[MauriceMoss]

Ok rebooted the hub 5, will monitor till tomorrow but doubt it will resolve it.

[carl_pearce]

Looks like oversubscription.