Low Level Packet Loss

[jonnymc4]

Hi

As the subject alludes to, I am having constant low level packet loss. I play online games and this is affecting my gameplay. I've had this for around a week now, with no day better than the other.

Today

Tuesday and the previous week with packet loss

Prior to the issue

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	5
DOCSIS 3.1 channels	1	1

3.0 Downstream channels

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

2	146750000	6.000000	40.946209	QAM256	2
1	138750000	6.300003	40.946209	QAM256	1
3	154750000	6.000000	40.366287	QAM256	3
4	162750000	5.599998	40.366287	QAM256	4
5	170750000	5.300003	40.366287	QAM256	5
6	178750000	5.000000	40.366287	QAM256	6
7	186750000	4.900002	40.946209	QAM256	7
8	194750000	5.000000	40.366287	QAM256	8
9	202750000	5.300003	40.366287	QAM256	9
10	210750000	5.599998	40.946209	QAM256	10
11	218750000	5.800003	40.366287	QAM256	11
12	226750000	6.300003	40.366287	QAM256	12
13	234750000	6.500000	40.946209	QAM256	13
14	242750000	6.800003	40.946209	QAM256	14
15	250750000	6.699997	40.366287	QAM256	15
16	258750000	6.800003	40.946209	QAM256	16
17	266750000	6.699997	40.946209	QAM256	17
18	274750000	6.500000	40.946209	QAM256	18
19	282750000	6.300003	40.946209	QAM256	19
20	290750000	6.300003	40.946209	QAM256	20
21	298750000	6.699997	40.946209	QAM256	21
22	306750000	6.699997	40.366287	QAM256	22
23	314750000	6.500000	40.946209	QAM256	23
24	322750000	6.199997	40.946209	QAM256	24
25	330750000	6.400002	40.946209	QAM256	25
26	338750000	6.699997	40.366287	QAM256	26
27	346750000	6.800003	40.946209	QAM256	27
28	354750000	6.699997	40.366287	QAM256	28
29	362750000	6.599998	40.366287	QAM256	29
30	370750000	6.699997	40.946209	QAM256	30
31	378750000	6.699997	40.946209	QAM256	31

3.0 Downstream channels

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

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

[jonnymc4]

3.1 Downstream channels

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

159

96

4K

1840

QAM4096

759

3.1 Downstream channels

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

159

Locked

42

7.5

1546348851

49

3.0 Upstream channels

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

1	30100000	48.020599	5120 KSym/sec	64QAM	4
2	23600000	48.020599	5120 KSym/sec	64QAM	5
3	36600000	48.020599	5120 KSym/sec	64QAM	3
4	43100000	47.020599	5120 KSym/sec	64QAM	2
5	49600000	47.020599	5120 KSym/sec	64QAM	1

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_ATDMA	0	0	0	0
2	US_TYPE_ATDMA	0	0	0	0
3	US_TYPE_ATDMA	0	0	0	0
4	US_TYPE_ATDMA	0	0	0	0
5	US_TYPE_ATDMA	0	0	0	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10.0

40.5

2K

QAM32

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

6

OFDMA

200

53.9

1

0

[jonnymc4]

General Configuration

Network access	true
Maximum Number of CPEs	1
Baseline Privacy	true
DOCSIS Mode	3.1
Config file	;kfoA,.iyewrkldJKDHSUBsgvca69

Primary Downstream Service Flow

SFID	1285
Max Traffic Rate	1200000450
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	12416
Max Traffic Rate	55000270
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	16320
Scheduling Type	bestEffort

Network Log

[jonnymc4]

Network Log

Time Priority Description

Fri Jan 27	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;
Fri Jan 27	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 27	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 Jan 27	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 27	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 Jan 26	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 26	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 Jan 26	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 26	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 26	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 Jan 26	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 25	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 25	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 25	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 25	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 25	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;
Wed Jan 25	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 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;
Tue Jan 24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 24	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;
Tue Jan 24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 24	6	CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 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;
Tue Jan 24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 24	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;
Tue Jan 24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 23	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;
Mon Jan 23	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 23	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 23	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 23	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 Jan 23	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 23	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;
Mon Jan 23	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 22	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 22	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 22	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;
Sun Jan 22	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 22	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;
Sat Jan 21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	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 Jan 21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	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;
Sat Jan 21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 21	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Travis_M]

Hi @jonnymc4

Thanks for posting on our community forum and sorry to hear about the issue with your broadband.

I am going to drop you a private message now to collect some more information and investigate further, please keep an eye on your inbox for a message from myself.

Regards

[jonnymc4]

Hi Travis,

Thank you for the reply and DM. The BQM was disabled over the weekend (not sure why), however this morning there does appear to be a significant improvement in the low level packet loss. I'll keep an eye open over the next few days and get back in touch if there are any further issues.

Jonny

[Matthew_ML]

Hey jonnymc4, thank you for reaching out and I am sorry to see you are still having some connection issues.

Please do feel free to reach out to my colleague Travis over PM anytime you want over this. Thanks