Contributor
•
54 Messages
T3 timeouts
This doesn't look good, to me, at all. Indicative of upstream equipment failures, perhaps?
Tue Jan 27 17:02:01 2026 (Notice (6)) CM-STATUS message sent. Event Type Code: 8; Chan ID: 2; 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 27 17:01:55 2026 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 27 17:01:50 2026 (Critical (3)) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 27 17:01:50 2026 (Critical (3)) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 27 17:01:50 2026 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
EG
Expert
•
115.7K Messages
2 hours ago
Are you actually experiencing any connection problems, or are you just focusing on the error log entries ?
0
0
XfinityBrianH
Official Employee
•
2K Messages
2 hours ago
Thanks for checking back in with us to let us know about the errors you are seeing. T3 timeouts can be inactive of many issues, including equipment failure. An acceptable number of T3 timeouts per day is ideally fewer than a dozen. I when I check your modem status I am only showing 10 timeouts over the last 7 days.
2
0