High Loaded Latency

[dan101]

Hi all,

I have recently found that while online gaming I have been receiving intermittent spikes in my latency making games unplayable. My speed is showing as around 220Mbps with unloaded ping as 17ms, loaded ping as 427ms and latency of 195ms.

Speedtest: 

BQM: 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c7eb3e40a9a560636b94455b8bfb72b186...

 I am using Hub 3.0, tests taken on wired connection. Any advice much appreciated.

[dan101]

Network Log

Time Priority Description

30/09/2022 12:29:3	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/09/2022 13:12:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/09/2022 21:50:49	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/09/2022 00:56:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/09/2022 12:42:0	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/09/2022 22:21:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/09/2022 17:59:37	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/09/2022 15:38:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/09/2022 18:18:59	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/09/2022 15:07:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/09/2022 17:16:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 03:23:5	notice	Unit has been restored to factory defaults from a software issued command;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 11:09:55	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:41	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:21	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:17	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:17	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:16	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2022 10:59:16	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[dan101]

Downstream bonded channels

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

1	235000000	5.8	40	256 qam	13
2	243000000	6	40	256 qam	14
3	251000000	6.1	40	256 qam	15
4	259000000	5.9	40	256 qam	16
5	267000000	6	38	256 qam	17
6	275000000	6.4	40	256 qam	18
7	283000000	6.3	38	256 qam	19
8	291000000	5.9	38	256 qam	20
9	299000000	6.1	38	256 qam	21
10	307000000	6.5	40	256 qam	22
11	315000000	6.4	38	256 qam	23
12	323000000	6.3	38	256 qam	24
13	331000000	6.5	38	256 qam	25
14	339000000	6.6	38	256 qam	26
15	347000000	6.4	40	256 qam	27
16	355000000	6.1	40	256 qam	28
17	363000000	6.4	40	256 qam	29
18	371000000	6.3	40	256 qam	30
19	379000000	6	38	256 qam	31
20	387000000	5.9	38	256 qam	32
21	395000000	6.3	40	256 qam	34
22	403000000	6.1	38	256 qam	35
23	411000000	6	38	256 qam	36
24	419000000	6	40	256 qam	37

Downstream bonded channels

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

1	Locked	40.9	161	0
2	Locked	40.3	64	0
3	Locked	40.3	97	0
4	Locked	40.3	67	0
5	Locked	38.6	84	0
6	Locked	40.3	70	0
7	Locked	38.9	95	0
8	Locked	38.9	114	0
9	Locked	38.9	88	0
10	Locked	40.9	69	0
11	Locked	38.9	63	0
12	Locked	38.6	179	0
13	Locked	38.9	89	0
14	Locked	38.9	55	0
15	Locked	40.3	56	0
16	Locked	40.3	76	0
17	Locked	40.3	52	0
18	Locked	40.3	92	0
19	Locked	38.9	83	0
20	Locked	38.9	87	0
21	Locked	40.3	53	0
22	Locked	38.9	74	0
23	Locked	38.9	66	0
24	Locked	40.3	94	0

[dan101]

Upstream bonded channels

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

1	32600000	43.8	5120	64 qam	5
2	53700000	42.5	5120	64 qam	2
3	46200000	42.8	5120	64 qam	3
4	39400000	43.3	5120	64 qam	4

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[dan101]

Cable Modem Status

Item Status Comments

Acquired Downstream Channel (Hz)	235000000	Locked
Ranged Upstream Channel (Hz)	32600000	Locked
Provisioning State	Online

[dan101 · Accepted solution]

Okay so ping issue was resolved by myself. I was using router alongside with hub (hub was in modem mode) and the issue was something called “Bufferbloat”. Fixed by setting up QoS on my router with manual bandwidth limitation (I’ve set to 95% of my real bandwidth). Now pings and stuff is in area of 30-50 and is good enough for me!

[Adduxi]

Thanks for sharing your findings around QoS.  Some users don't like using QoS as it reduces the download speeds, but if it makes for a stable line, that's a better bet.

[Zach_R]

Hi @dan101,

Thank you for your posts and welcome to our community forums. We're here to help.

I'm very sorry to hear of the problems you've been experiencing with your connection recently. However, I'm glad to hear that this as now been resolved for you.

Please do let us know if there's anything more that we can assist you with.

Thanks,