on 03-05-2023 12:45
I'm getting frequent low-level packet loss with spikes of 100% which I observe during playing games like Valorant (which has a packet loss meter). The BQM I've setup confirms this too, though its timing isn't picking up the high 100% spikes often.
I believe this has started occurring since the 20th of April when scheduled maintenance took place which took out all connections in our street. I could be wrong. I've restarted the router to no avail. The router is running in modem only mode. It's a hub 4. The cable was re-pulled to our home towards the end of last year so shouldn't be an issue there.
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 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
19 | 283000000 | 7.900002 | 40.946209 | QAM256 | 19 |
1 | 139000000 | 8.800003 | 40.366287 | QAM256 | 1 |
2 | 147000000 | 9.099998 | 40.366287 | QAM256 | 2 |
3 | 155000000 | 9.199997 | 40.946209 | QAM256 | 3 |
4 | 163000000 | 8.400002 | 40.366287 | QAM256 | 4 |
5 | 171000000 | 7.300003 | 40.946209 | QAM256 | 5 |
6 | 179000000 | 6.800003 | 40.366287 | QAM256 | 6 |
7 | 187000000 | 6.800003 | 40.946209 | QAM256 | 7 |
8 | 195000000 | 6.099998 | 40.366287 | QAM256 | 8 |
9 | 203000000 | 5.800003 | 40.366287 | QAM256 | 9 |
10 | 211000000 | 5.699997 | 40.366287 | QAM256 | 10 |
11 | 219000000 | 5.699997 | 40.366287 | QAM256 | 11 |
12 | 227000000 | 5.400002 | 40.366287 | QAM256 | 12 |
13 | 235000000 | 5.400002 | 40.946209 | QAM256 | 13 |
14 | 243000000 | 5.500000 | 40.946209 | QAM256 | 14 |
15 | 251000000 | 5.099998 | 40.366287 | QAM256 | 15 |
16 | 259000000 | 6.699997 | 40.366287 | QAM256 | 16 |
17 | 267000000 | 7.900002 | 40.946209 | QAM256 | 17 |
18 | 275000000 | 8.000000 | 40.946209 | QAM256 | 18 |
20 | 291000000 | 8.300003 | 40.366287 | QAM256 | 20 |
21 | 299000000 | 7.599998 | 40.946209 | QAM256 | 21 |
22 | 307000000 | 7.199997 | 40.946209 | QAM256 | 22 |
23 | 315000000 | 7.400002 | 40.946209 | QAM256 | 23 |
24 | 323000000 | 6.000000 | 40.946209 | QAM256 | 24 |
25 | 331000000 | 4.900002 | 40.366287 | QAM256 | 25 |
26 | 339000000 | 5.400002 | 40.946209 | QAM256 | 26 |
27 | 347000000 | 4.900002 | 40.366287 | QAM256 | 27 |
28 | 355000000 | 4.699997 | 40.366287 | QAM256 | 28 |
29 | 363000000 | 4.800003 | 40.946209 | QAM256 | 29 |
30 | 371000000 | 4.300003 | 40.366287 | QAM256 | 30 |
31 | 379000000 | 4.400002 | 40.946209 | QAM256 | 31 |
on 03-05-2023 12:46
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
19 | Locked | 40.946209 | 0 | 0 |
1 | Locked | 40.366287 | 0 | 0 |
2 | Locked | 40.366287 | 0 | 0 |
3 | Locked | 40.946209 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.946209 | 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.366287 | 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.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.946209 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.946209 | 0 | 0 |
22 | Locked | 40.946209 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 40.946209 | 0 | 0 |
25 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.946209 | 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.946209 | 0 | 0 |
159 | 96 | 4K | 1840 | QAM4096 | 759 |
159 | Locked | 44 | 7.7 | 11837 | 0 |
on 03-05-2023 12:46
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 49600000 | 42.270599 | 5120 KSym/sec | 64QAM | 9 |
2 | 23600000 | 41.020599 | 5120 KSym/sec | 64QAM | 13 |
3 | 30100000 | 41.020599 | 5120 KSym/sec | 64QAM | 12 |
4 | 36600000 | 41.020599 | 5120 KSym/sec | 64QAM | 11 |
5 | 43100000 | 41.520599 | 5120 KSym/sec | 64QAM | 10 |
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 |
14 | 10.0 | 36.8 | 2K | QAM128 |
14 | OFDMA | 200 | 53.9 | 0 | 0 |
on 03-05-2023 13:04
Time Priority Description
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed May | 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; |
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed May | 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; |
Wed May | 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; |
Wed May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 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; |
Tue May | 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 Jan | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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; |
Tue May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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; |
Tue May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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; |
Tue May | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue May | 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 May | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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 May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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 May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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; |
Mon May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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; |
Mon May | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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; |
Mon May | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 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; |
Mon May | 6 | US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon May | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Apr 30 | 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; |
on 05-05-2023 14:14
Hi shuurajou, thanks for the message and sorry to hear that there has been an issue with the service.
I have checked the area and cannot see any outages.
Can you confirm if there is still an issue since posting?
Would you be able to create a BQM here
Kind regards, Chris.
05-05-2023 16:26 - edited 05-05-2023 16:33
Hi Chris,
Here's a link to the live BQM I shared a screenshot of in my initial post.
The issue is still ongoing today. Though quieter this afternoon.
Here's graphs over the past week.
on 08-05-2023 11:19
Hi shuurajoou,
Thank you for your repy replies.
We have double checked the service from our side and are detecting no issues with the power levels or specifications.
Are you using an Ethernet connection on the device? If so, can you please try switching the port that is being used on the Hub?
Let us know if this helps.
Thanks,
11-05-2023 09:57 - edited 11-05-2023 09:57
Hiya,
Yes I’m using an Ethernet cable. I switched the port to port 4 at 8am this morning. Will see if it improves but BQM seems no different so far.
on 11-05-2023 21:22
do CMD by wire with
ping -n 200 194.168.4.100
see if you get loss
13-05-2023 15:08 - edited 13-05-2023 15:12
BQM still shows my issue, so I've bought 2 new cables in CAT 6a, shielded, to make sure I can rule that out. Will monitor.
However, packetlosstest.com moments after changing the cables...