Constant small packet loss dips in SS2

[alphaomega16]

For the past week ive been getting persistent little spikes in packet loss and I am noticing it ingame.

Is there currently an issue in my area, no point in calling up as I never get anywhere and now the tech support has business hours so if my internet went completely off after 5pm there is nobody to call.

[RT123]

Hi, 

Could you please share the router logs again?

[alphaomega16]

[alphaomega16]

It wont let me post the logs, im pressing reply but nothing is happening when I paste the info, when I do get it to post please keep in mind that a hub update stopped any errors showing in upload/download window on logs.

[alphaomega16]

3.0 Downstream channels

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

25	331000000	3.8	39	QAM256	25
1	139000000	4.7	38.6	QAM256	1
2	147000000	5.1	38.6	QAM256	2
3	155000000	5.4	38.6	QAM256	3
4	163000000	5.1	38.6	QAM256	4
5	171000000	4.6	38.6	QAM256	5
6	179000000	4.5	38.6	QAM256	6
7	187000000	4.7	39	QAM256	7
8	195000000	4.4	39	QAM256	8
9	203000000	4.1	39	QAM256	9
10	211000000	4.3	39	QAM256	10
11	219000000	4.5	38.6	QAM256	11
12	227000000	5.1	39	QAM256	12
13	235000000	5.1	39	QAM256	13
14	243000000	4.9	38.6	QAM256	14
15	251000000	5.1	38.6	QAM256	15
16	259000000	5.4	38.6	QAM256	16
17	267000000	4.7	39	QAM256	17
18	275000000	3.6	38.6	QAM256	18
19	283000000	3.7	39	QAM256	19
20	291000000	4.4	39	QAM256	20
21	299000000	4.6	39	QAM256	21
22	307000000	4.2	39	QAM256	22
23	315000000	3.8	39	QAM256	23
24	323000000	3.5	39	QAM256	24
26	339000000	3.5	39	QAM256	26
27	347000000	3.3	39	QAM256	27
28	355000000	3.7	39	QAM256	28
29	363000000	3.8	38.6	QAM256	29
30	371000000	3.4	38.6	QAM256	30
31	379000000	2.9	39	QAM256	31

3.0 Downstream channels

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

25	Locked	38.983261	0	0
1	Locked	38.605377	0	0
2	Locked	38.605377	0	0
3	Locked	38.605377	0	0
4	Locked	38.605377	0	0
5	Locked	38.605377	0	0
6	Locked	38.605377	0	0
7	Locked	38.983261	0	0
8	Locked	38.983261	0	0
9	Locked	38.983261	0	0
10	Locked	38.983261	0	0
11	Locked	38.605377	0	0
12	Locked	38.983261	0	0
13	Locked	38.983261	0	0
14	Locked	38.605377	0	0
15	Locked	38.605377	0	0
16	Locked	38.605377	0	0
17	Locked	38.983261	0	0
18	Locked	38.605377	0	0
19	Locked	38.983261	0	0
20	Locked	38.983261	0	0
21	Locked	38.983261	0	0
22	Locked	38.983261	0	0
23	Locked	38.983261	0	0
24	Locked	38.983261	0	0
26	Locked	38.983261	0	0
27	Locked	38.983261	0	0
28	Locked	38.983261	0	0
29	Locked	38.605377	0	0
30	Locked	38.605377	0	0
31	Locked	38.983261	0	0

[alphaomega16]

3.0 Upstream channels

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

1	36600000	40.8	5120 KSym/sec	QAM64	3
2	30100000	40.3	5120 KSym/sec	QAM64	4
3	23600000	40	5120 KSym/sec	QAM64	5
4	43100000	40.8	5120 KSym/sec	QAM64	2
5	49600000	40.8	5120 KSym/sec	QAM64	1

3.0 Upstream 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
5	ATDMA	0	0	0	0

[alphaomega16]

Network Log

Time Priority Description

Fri 03/05/2024 11:02:24	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 03/05/2024 05:23:02	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 03/05/2024 03:44:56	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 15:52:29	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 15:15:13	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 08:01:17	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 06:56:59	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 03:48:16	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 03:37:56	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 02:50:42	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 02:47:56	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 02:23:44	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/05/2024 01:58:05	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/04/2024 23:25:15	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Martin_N]

Hi alphaomega16,

Thank you for your post. We're sorry to hear about the issues you've been having. 

How have they been since your last post?

^Martin

[alphaomega16]

The same, constant dips in packet loss and it has been noticeable in games.

I power cycled the superhub and it didn't take long for it to crop up again

The big red block was just an issue that crops up every now and then, changing flood detection status sorts it out til it happens again.

[Akua_A]

Sorry to hear the issue is ongoing @alphaomega16  In this case, we have sent you a private message to best look into this for you. Please keep an eye out for an envelope at the top right corner of your Forum page. Let me know if you have any issues locating this.
Thanks,

[Megan_L]

Hi Alphaomega16,

Thanks for chatting with me and Akua in your private messages, we've explored all avenues to get this issue resolved and we are happy to say that no further issues are outstanding on our side after the recent engineer visit 🤗 Plus, the BMQ graph you sent to us looked a lot more stable than the earlier graphs you sent. 

Due to this we are satisfied with the outcome and happy to say all issues are resolved on our side.

With that being said though, we would recommend looking at your own devices to see if there are any issues on your side that may be causing a problem. 

The wider community here on the Forums would be happy to help with this, plus we can guide you on other aspects as long as it's not 3rd party equipment 🙂

Please feel free to explain the current issues you're facing on your side now that we've resolved everything else.

Thanks,

Meg