Packet loss or spikes in games and Discord since hub 4

[Bluer]

Hi everyone,

We recently changed to gig1 and hub 4 and ever since I've been getting Apex Legends reporting packet loss (I also notice players teleporting) for a few seconds every minute or so and at the same time it happens I hear people in Discord missing parts of words, although they never report my voice being strange to them so presumably it's all inbound? Unfortunately I don't know how to test it on different systems since none of them are appropriate for gaming or voice chat, but I've tried the thinkbroadband BQM graphs and none of them show any packet loss specifically.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/24da6c1d5f79365c7610697073bba8676b73ab63

If there is anything I can do on my system that could be causing it as well please let me know and I'll try it. I've disabled the firewall on the hub and it made no difference. Thanks in advance.

Below are my router stats:

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status	Online	DOCSIS 3.1
Primary downstream channel	Locked	SC-QAM
DOCSIS 3.0 channels	31	4
DOCSIS 3.1 channels	1	0

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status	Online	DOCSIS 3.1
Primary downstream channel	Locked	SC-QAM
DOCSIS 3.0 channels	31	4
DOCSIS 3.1 channels	1	0

3.0 Upstream channels

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

1	60300000	48.3	5120 KSym/sec	64QAM	1
2	53700000	48.3	5120 KSym/sec	64QAM	2
3	39400000	48.3	5120 KSym/sec	64QAM	4
4	46200000	47.8	5120 KSym/sec	64QAM	3

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_STDMA	0	0	1	0
2	US_TYPE_STDMA	0	0	1	0
3	US_TYPE_STDMA	0	0	0	0
4	US_TYPE_STDMA	0	0	0	0

Network Log

Time Priority Description

Thu 01/01/1970 00:01:19	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 02/07/2022 15:39:47	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 02/07/2022 15:42:53	6	SW Download INIT - Via Config file cmreg-vmdg640-bbt076-b.cm
Sat 02/07/2022 15:44:06	6	SW download Successful - Via Config file
Sat 02/07/2022 15:46:42	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 02/07/2022 15:49:52	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 02/07/2022 16:14:35	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 09/07/2022 18:00:46	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 13/07/2022 05:12:06	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 13/07/2022 16:05:40	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 14/07/2022 10:05:31	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 17/07/2022 07:38:45	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/07/2022 15:26:56	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 27/07/2022 12:55:29	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:20	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 29/07/2022 12:51:12	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/08/2022 00:53:18	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/08/2022 11:22:21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/08/2022 23:13:01	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/08/2022 06:54:49	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Daniel

[Adduxi]

You need to post all the stats for Download including the 3.1 stuff.

Your BQM and 3.0 Upstream all look fine.

How are you connecting btw, wired or wireless ?

[Bluer]

Hi Adduxi,

Apologies, I thought I had but I must have not copied it properly.

I have ethernet in so I am wired.

3.0 Downstream channels

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

25	330750000	-1.6	40.4	QAM256	25
6	178750000	-0.5	40.9	QAM256	6
7	186750000	-0.5	40.4	QAM256	7
8	194750000	-0.6	40.4	QAM256	8
9	202750000	-0.4	40.4	QAM256	9
10	210750000	-0.4	40.4	QAM256	10
11	218750000	-0.6	40.9	QAM256	11
12	226750000	-0.4	40.9	QAM256	12
13	234750000	-0.5	40.9	QAM256	13
14	242750000	-0.4	40.4	QAM256	14
15	250750000	-0.5	40.9	QAM256	15
16	258750000	-0.6	40.4	QAM256	16
17	266750000	-0.6	40.9	QAM256	17
18	274750000	-0.2	40.9	QAM256	18
19	282750000	-0.1	40.9	QAM256	19
20	290750000	-0.3	40.4	QAM256	20
21	298750000	-0.7	40.4	QAM256	21
22	306750000	-1.2	40.4	QAM256	22
23	314750000	-1.5	40.9	QAM256	23
24	322750000	-1.6	40.4	QAM256	24
26	338750000	-1.5	40.4	QAM256	26
27	346750000	-1.5	40.4	QAM256	27
28	354750000	-1.4	40.4	QAM256	28
29	362750000	-1.3	40.9	QAM256	29
30	370750000	-1	40.4	QAM256	30
31	378750000	-1.3	40.4	QAM256	31
32	386750000	-1.3	40.9	QAM256	32
33	394750000	-1.2	40.9	QAM256	33
34	402750000	-1.3	40.4	QAM256	34
35	410750000	-1.3	40.4	QAM256	35
36	514750000	-0.3	40.9	QAM256	36

3.0 Downstream channels

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

25	Locked	40.366287	0	0
6	Locked	40.946209	0	0
7	Locked	40.366287	0	0
8	Locked	40.366287	1	0
9	Locked	40.366287	0	0
10	Locked	40.366287	0	0
11	Locked	40.946209	0	0
12	Locked	40.946209	0	0
13	Locked	40.946209	0	0
14	Locked	40.366287	0	0
15	Locked	40.946209	0	0
16	Locked	40.366287	0	0
17	Locked	40.946209	0	0
18	Locked	40.946209	0	0
19	Locked	40.946209	0	0
20	Locked	40.366287	0	0
21	Locked	40.366287	0	0
22	Locked	40.366287	0	0
23	Locked	40.946209	0	0
24	Locked	40.366287	0	0
26	Locked	40.366287	0	0
27	Locked	40.366287	0	0
28	Locked	40.366287	0	0
29	Locked	40.946209	0	0
30	Locked	40.366287	0	0
31	Locked	40.366287	0	0
32	Locked	40.946209	0	0
33	Locked	40.946209	0	0
34	Locked	40.366287	0	0
35	Locked	40.366287	0	0
36	Locked	40.946209	0	0

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

37

94

4K

1840

QAM4096

416

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

37

Locked

43

-1.6

695064280

8

[Matthew_ML · Accepted solution]

Hey Bluer, thank you for reaching out and I am sorry to hear you are having some issues with Packet loss.

Thank you for confirming you are using a wired connection is this only happening when you are gaming or does it happen in general?  

I would like to run some in-depth tests with you via PM, please can you look out for the purple envelope. Thanks