| Time |
Priority |
Description |
| Wed Jul 30 07:23:25 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:23:27 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:23:36 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:24:23 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:24:30 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:24:37 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:24:41 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:25:33 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:25:46 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:26:29 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:26:40 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:26:43 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:26:51 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:27:40 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:27:45 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:27:54 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:27:56 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:28:36 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:28:50 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:28:50 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:29:01 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:29:46 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:29:55 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:30:00 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:30:06 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:30:56 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:31:00 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:31:10 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:31:11 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:31:38 2025 |
Warning (5) |
Dynamic Range Window violation |
| Wed Jul 30 07:31:49 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 30 07:31:52 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
EG
Expert
•
112.8K Messages
26 days ago
Ok so even though the signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is 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 !
0
0
EG
Expert
•
112.8K Messages
26 days ago
@Stan_3
Also, bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
0
0
XfinityRoberto
Official Employee
•
1.9K Messages
26 days ago
Hi there @Stan_3. Thank you so much for this information. I am sorry to hear that you are having intermittent connectivity. You are in the right place and we are happy to take a look at your account.
Please send us a direct chat message with your full name and complete service address to “Xfinity Support”. To do so, click on the chat icon located at the top right of this forums page.
Here's the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the "Direct Message” icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message
Let me know if you have any questions.
2