Packet loss whilst gaming

[HungryHarry117]

Hello,

Last night I was unable to play my game (World of Warcraft) on my PC for very long before my connection dropped and it kicked me out of the game. This happened repeatedly. I was connected to voice chat over discord as well. I live in a shared house and they were both gaming/streaming as well but neither of them had any internet issues. It was very frustrating intermittent packet loss.

I believe our package is 200mbps/month, and whilst I am further away than my flat mates, I am not too far and on the same floor as our router. I connect to our 5G signal wirelessly.

I ran a BQM since last night and these were my results. Though I am not sure how to interpret it:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/738cd6f4fd1a8728f0474b20d2528280c30007e1-13-10-2022 

I'd be very grateful if anyone has any tips on what I can do to avoid my connection dropping, even during times of heavy traffic as I forsee this remaining the same. I think our package should be able to handle it, but maybe there is a booster or something I should buy, just to cover my room? Or is there a way I can prioritise certain connections over others?

Thanks in advance for your help!

[Adduxi]

Post the power levels, Pre and PostRS errors and network log from the Hub.

Once done we can comment.

[HungryHarry117]

Thanks for your reply! I am hoping these are the logs you mean:

Downstream bonded channels

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

1	139000000	17.1	38	256 qam	1
2	147000000	17	40	256 qam	2
3	155000000	16.8	40	256 qam	3
4	163000000	16.1	38	256 qam	4
5	171000000	16.1	38	256 qam	5
6	179000000	16.1	38	256 qam	6
7	187000000	16.3	40	256 qam	7
8	195000000	16	40	256 qam	8
9	203000000	15.9	40	256 qam	9
10	211000000	15.5	38	256 qam	10
11	219000000	15.5	40	256 qam	11
12	227000000	15.3	38	256 qam	12
13	235000000	15	38	256 qam	13
14	243000000	14.9	40	256 qam	14
15	251000000	14.9	40	256 qam	15
16	259000000	14.5	40	256 qam	16
17	267000000	14.5	40	256 qam	17
18	275000000	14.1	40	256 qam	18
19	283000000	14	40	256 qam	19
20	291000000	14	38	256 qam	20
21	299000000	13.8	40	256 qam	21
22	307000000	13	38	256 qam	22
23	315000000	12.5	38	256 qam	23
24	323000000	12.3	38	256 qam	24

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

1	Locked	38.6	4	0
2	Locked	40.3	5	0
3	Locked	40.3	4	0
4	Locked	38.9	1	0
5	Locked	38.9	7	0
6	Locked	38.9	5	0
7	Locked	40.3	6	0
8	Locked	40.9	5	0
9	Locked	40.3	5	0
10	Locked	38.9	5	0
11	Locked	40.9	8	0
12	Locked	38.9	17	0
13	Locked	38.9	6	0
14	Locked	40.3	5	0
15	Locked	40.3	4	0
16	Locked	40.3	7	0
17	Locked	40.3	4	0
18	Locked	40.3	4	0
19	Locked	40.9	4	0
20	Locked	38.9	13	0
21	Locked	40.3	5	0
22	Locked	38.9	4	0
23	Locked	38.9	6	0
24	Locked	38.9	6	0

Upstream bonded channels

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

1	39399564	37.5	5120	64 qam	4
2	46199860	39.3	5120	64 qam	3
3	32599863	36.3	5120	64 qam	5
4	25799971	35.2	5120	16 qam	6

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[HungryHarry117]

Network Log

Time Priority Description

14/10/2022 08:08:41	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2022 08:04:0	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2022 17:05:49	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2022 17:00:27	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2022 07:30:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2022 01:26:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/10/2022 08:33:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2022 13:26:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2022 02:04:24	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2022 01:26:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2022 07:38:22	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2022 20:59:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2022 13:26:44	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/10/2022 21:01:59	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/09/2022 01:26:44	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 18:54:58	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2022 01:26:44	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/09/2022 16:34:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/09/2022 13:26:44	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Nathan_B]

Hi there @HungryHarry117, welcome to our forum and thanks for your post.

Sorry to see that you have been having issues with packet loss, I have checked our system and cannot see anything that would be causing this. As this is the case it would be best to pop you over a PM to check this further.

Regards

Nathan

[legacy1]

Your upstream is likely glitching causing packets to be buffered in the modem till it tries again.