O

Monday, March 24th, 2025 3:57 PM

Started Unicast Maintenance Ranging - No Response received - T3 time-out

I've been dealing with connection drops for months. We've had 4 service calls but they keep saying everything is fine even though we keep getting notices from Xfinity about service disruption.  We've had every TV in the house except one and the cable modem unhooked at the box. But still we get numerous T3 and T4 errors which results in the internet drop or slowing. 

The Tech mentioned the router but I've replaced the router to test still have the same results.  Our drops correspond to when we're seeing the errors in the modem log as seen below.  

I don't know why they can't find the problem. I really don't want to switch to FIOS but I can't have unstable internet like this. 

Event Log
Status > Event Log
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Date Time   Event ID    Event Level Description
03/24/2025 07:45    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 07:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 07:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:46    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 04:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 03:04    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:46    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 02:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 18:03    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 17:59    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:50    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:35    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:26    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:23    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:22    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:21    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:16    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:13    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:12    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:10    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:03    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:02    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:23    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:18    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:18    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:16    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:15    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:14    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:13    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:36    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:32    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:32    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:31    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:30    74010100    6   "C

7 Messages

9 days ago

Today was really bad with the rain it always seems worse when it's raining. 

Event Log
Status > Event Log
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Date Time   Event ID    Event Level Description
03/24/2025 18:55    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 17:45    85000200    3   "UCD invalid or channel unusable;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 17:34    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 17:19    85000200    3   "UCD invalid or channel unusable;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 17:08    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 17:07    85000200    3   "UCD invalid or channel unusable;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 16:57    2436694061  5   "Dynamic Range Window violation"
03/24/2025 16:57    82001100    5   "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 16:56    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 10:45    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 10:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 10:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 07:45    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 07:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 07:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:46    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 04:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 03:04    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:46    74010100    6   "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; 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;"
03/24/2025 02:45    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:45    84020300    5   "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 18:03    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 17:59    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:50    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:35    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:26    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:23    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:22    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:21    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:16    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:13    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:12    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:10    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:03    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:02    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00    82000500    3   "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:23    74010100    6   "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:18    74010100    6   "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID:

Expert

 • 

109.5K Messages

9 days ago

Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

7 Messages

@EG​  Thank you here are the current stats. 

Connection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 417000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked QAM256 417000000 Hz 1.6 dBmV 44.6 dB 985 0
1 Locked QAM256 399000000 Hz 1.8 dBmV 44.7 dB 1891 25
2 Locked QAM256 405000000 Hz 1.7 dBmV 44.7 dB 1641 40
3 Locked QAM256 411000000 Hz 1.7 dBmV 44.4 dB 1188 0
5 Locked QAM256 423000000 Hz 1.4 dBmV 44.5 dB 698 0
6 Locked QAM256 429000000 Hz 1.4 dBmV 44.6 dB 772 16
7 Locked QAM256 435000000 Hz 1.4 dBmV 44.7 dB 890 0
8 Locked QAM256 441000000 Hz 1.3 dBmV 44.5 dB 648 0
9 Locked QAM256 447000000 Hz 1.5 dBmV 44.5 dB 829 3
10 Locked QAM256 453000000 Hz 1.4 dBmV 44.6 dB 673 0
11 Locked QAM256 459000000 Hz 1.5 dBmV 44.7 dB 543 0
12 Locked QAM256 465000000 Hz 1.5 dBmV 44.7 dB 373 0
13 Locked QAM256 471000000 Hz 1.5 dBmV 44.6 dB 474 0
14 Locked QAM256 477000000 Hz 1.6 dBmV 44.7 dB 314 0
15 Locked QAM256 483000000 Hz 1.5 dBmV 44.7 dB 230 0
16 Locked QAM256 489000000 Hz 1.6 dBmV 44.6 dB 330 0
17 Locked QAM256 495000000 Hz 1.5 dBmV 44.5 dB 342 0
18 Locked QAM256 501000000 Hz 1.4 dBmV 44.6 dB 429 0
19 Locked QAM256 507000000 Hz 1.3 dBmV 44.4 dB 357 0
20 Locked QAM256 513000000 Hz 1.3 dBmV 44.4 dB 275 0
21 Locked QAM256 519000000 Hz 1.1 dBmV 44.4 dB 203 0
22 Locked QAM256 525000000 Hz 1.1 dBmV 44.2 dB 188 0
23 Locked QAM256 531000000 Hz 1.0 dBmV 44.2 dB 187 13
24 Locked QAM256 537000000 Hz 0.8 dBmV 44.2 dB 184 0
25 Locked QAM256 543000000 Hz 0.8 dBmV 44.1 dB 196 0
26 Locked QAM256 549000000 Hz 0.8 dBmV 44.0 dB 160 0
27 Locked QAM256 555000000 Hz 0.9 dBmV 44.0 dB 151 0
28 Locked QAM256 561000000 Hz 1.0 dBmV 44.1 dB 110 0
29 Locked QAM256 567000000 Hz 1.1 dBmV 43.9 dB 107 0
30 Locked QAM256 573000000 Hz 1.3 dBmV 44.2 dB 66 0
31 Locked QAM256 579000000 Hz 1.5 dBmV 44.2 dB 122 0
32 Locked QAM256 585000000 Hz 1.5 dBmV 44.1 dB 62 0
193 Locked Other 690000000 Hz 1.8 dBmV 42.5 dB 1604620750 39451
194 Locked Other 957000000 Hz 0.0 dBmV 36.0 dB 1604620750 39451



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 47.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 47.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 47.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 47.0 dBmV



Official Employee

 • 

2.4K Messages

Hello, @OliverM3

 

Could you please send our team a direct message with your full name and full address? To send a direct message:

1. In the top right corner, you'll see a little chat icon near the bell icon. Click the direct message icon

2. Click the "New message" (pencil and paper) icon

3. In the 'To' line, type "Xfinity Support" there. A drop-down list appears. Select "Xfinity Support" from that list (an "Xfinity Support" graphic replaces the "To:" line)

4. Type your message in the text area near the bottom of the window

5. Press Enter to send it. An official employee, such as myself or whoever is first available, will respond. Thanks!

 

 

 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

7 Messages

sent the info as requested 

Expert

 • 

109.5K Messages

9 days ago

The signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) / an upstream channel / return path impairment somewhere.


There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and check those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

7 Messages

@EG​ Thank you so much we've been dealing with this for so long now.  Let me know if I can provide anything else. 

(edited)

Expert

 • 

109.5K Messages

9 days ago

@OliverM3 

My pleasure !!

7 Messages

@EG​ 

current status while experiencing issues lots of uncorrectables showing

Procedure Status Comment
Acquire Downstream Channel 417000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked QAM256 417000000 Hz 1.5 dBmV 44.7 dB 5129 315
1 Locked QAM256 399000000 Hz 1.7 dBmV 44.8 dB 11737 547
2 Locked QAM256 405000000 Hz 1.6 dBmV 44.8 dB 9599 364
3 Locked QAM256 411000000 Hz 1.6 dBmV 44.5 dB 7094 260
5 Locked QAM256 423000000 Hz 1.3 dBmV 44.7 dB 3272 123
6 Locked QAM256 429000000 Hz 1.3 dBmV 44.6 dB 4196 185
7 Locked QAM256 435000000 Hz 1.3 dBmV 44.6 dB 4556 154
8 Locked QAM256 441000000 Hz 1.2 dBmV 44.6 dB 3080 127
9 Locked QAM256 447000000 Hz 1.4 dBmV 44.6 dB 3987 122
10 Locked QAM256 453000000 Hz 1.3 dBmV 44.6 dB 3880 115
11 Locked QAM256 459000000 Hz 1.4 dBmV 44.7 dB 2661 104
12 Locked QAM256 465000000 Hz 1.4 dBmV 44.7 dB 2346 64
13 Locked QAM256 471000000 Hz 1.4 dBmV 44.7 dB 2445 81
14 Locked QAM256 477000000 Hz 1.5 dBmV 44.7 dB 2087 98
15 Locked QAM256 483000000 Hz 1.5 dBmV 44.6 dB 1210 53
16 Locked QAM256 489000000 Hz 1.4 dBmV 44.4 dB 1586 24
17 Locked QAM256 495000000 Hz 1.4 dBmV 44.6 dB 1660 58
18 Locked QAM256 501000000 Hz 1.3 dBmV 44.5 dB 1843 30
19 Locked QAM256 507000000 Hz 1.3 dBmV 44.6 dB 1989 88
20 Locked QAM256 513000000 Hz 1.2 dBmV 44.5 dB 1462 52
21 Locked QAM256 519000000 Hz 1.0 dBmV 44.3 dB 1246 35
22 Locked QAM256 525000000 Hz 1.0 dBmV 44.4 dB 1096 7
23 Locked QAM256 531000000 Hz 0.9 dBmV 44.3 dB 1087 15
24 Locked QAM256 537000000 Hz 0.8 dBmV 44.2 dB 904 12
25 Locked QAM256 543000000 Hz 0.8 dBmV 44.2 dB 745 0
26 Locked QAM256 549000000 Hz 0.8 dBmV 44.1 dB 807 0
27 Locked QAM256 555000000 Hz 0.8 dBmV 44.0 dB 635 0
28 Locked QAM256 561000000 Hz 1.0 dBmV 44.1 dB 485 0
29 Locked QAM256 567000000 Hz 1.0 dBmV 44.0 dB 453 1
30 Locked QAM256 573000000 Hz 1.2 dBmV 44.2 dB 404 0
31 Locked QAM256 579000000 Hz 1.4 dBmV 44.4 dB 528 0
32 Locked QAM256 585000000 Hz 1.4 dBmV 44.3 dB 353 0
193 Locked Other 690000000 Hz 1.8 dBmV 42.5 dB 2369650440 599458
194 Locked Other 957000000 Hz 0.0 dBmV 36.0 dB 2369650440 599458



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 52.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 56.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 52.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 51.0 dBmV



Current System Time: Wed Mar 26 15:34:57 2025

(edited)

Expert

 • 

109.5K Messages

7 days ago

Your latest post shows that the upstream power has spiked up to being too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

Here's some things that you can try. In an effort to try to obtain better connection quality, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

7 Messages

@EG​ I hope comcast used good splitters they replaced the two since I had everything unhooked but the tv and cable modem everything else has been disconnected. 

forum icon

New to the Community?

Start Here