Contributor
•
85 Messages
T3 timeouts are back with erratic internet streaming and stability issues over weeks or months
I started a new job where we do a lot of video meetings (like over Zoom and Meet and Slack etc), and we've all become annoyed at me every few minutes in random (but increasingly frequent) meetings having to ask someone to repeat themselves or say that I can't read the text in the screenshare because it gets blurry... this is becoming insanely frustrating. Everyone else is saying they're not experiencing these issues.
Troubleshooting my modem/router/devices the way I know and Xfinity recommends as well, nothing is fixing the issue. I've been at my place just over a year and things are fine most months, but then the T3 tornadoes start striking during seemingly random periods.
I'll paste my modem logs below but never once have any issues like these happening during periods of T3 timeouts in the modem logs turned out to be a problem with any of my equipment... each time it wouldn't just go away, a senior-level tech ultimately had to investigate Comcast's lines in the walls or outside or in their boxes and then found a problem there, oftentimes multiple problems, oftentimes over weeks-long periods... so frustrating. This is even after going through multiple modem/router swaps and many many many times going through Comcast's instructions and phone support usually through multiple support/"tech" reps including over several "tech levels".
Event Log (sorry that I don't know how to censor the MACs while pasting to a pretty-looking table):
Log
Time Priority Description
Fri Jul 05 09:46:55 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Jul 05 18:37:33 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Jul 12 16:21:03 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Sun Jul 14 17:39:36 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Wed Jul 31 14:22:03 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Aug 02 18:37:27 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Thu Aug 08 00:16:20 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Thu Aug 08 22:12:09 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Aug 09 08:40:21 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sat Aug 10 13:41:15 2024 Warning (5) MDD message timeout;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Sat Aug 10 13:45:48 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Aug 16 22:15:02 2024 Warning (5) MDD message timeout;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Fri Aug 16 22:47:15 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Mon Aug 19 09:59:39 2024 Warning (5) MDD message timeout;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Mon Aug 19 09:59:59 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Mon Aug 19 14:17:55 2024 Warning (5) MDD message timeout;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Mon Aug 19 15:37:13 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 15:03:59 2024 Warning (5) MDD message timeout;CM-MAC=[confidential_1];CMTS-MAC=[confidential_2];CM-QOS=1.1;CM-VER=3.0;
I don't lease the modem, I've had it over 5 years and it's great besides needing an occasional reboot (yes that's when I/we traced it to that, which has been less often than the senior-tech-confirmed T3 Comcast problems). Every time the senior tech found the problem based on me being persistent with Comcast on the T3 timeouts, they fixed the problem, and it was gone for months with great consistent internet, even over a year a few times. Why Comcast can't make this years or decades without the problem, I don't know.
Anyway, now what? I'm so tired right now from everything that my eyes are blurry. Can you escalate this to a senior-level tech so they can inspect the lines again? Or do I need to run through the gauntlet of low-level support reps hanging up on me 1/3rd of the time while going through steps?
Also a junction (?) box outside has no cover and has been exposed to birds making nests in it and rainstorms and snow etc for over a year now. I was told by a tech that I need to report it to the regional office or something... and couldn't tell me how. I have no idea what to do about it. I'd bet it's the problem though. There's no reason for that to be exposed. Comcast should have fixed that before I got here. It honestly looks like a fire hazard. Maybe I should ask the fire department about it? I've got photographs of it going back months. I'm in a condo complex
codelirious
Contributor
•
85 Messages
3 months ago
Oop, I forgot I should post the d/u stream signal stuff...
0
0
XfinityRay
Official Employee
•
2.2K Messages
3 months ago
Thank you for the modem signal levels and other helpful information, codelirious. Since there are concerns with the outside box as well, let's take this into a direct message. We will further troubleshoot the service. We will need a visit for the box to be repaired which may also be the root cause of the timeouts.
Please send us a direct message with your full name and complete service address to “Xfinity Support”. To do so, click on the direct messaging 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
0
0
user_5f6ksr
1 Message
2 months ago
I have had these same issues for four years, on and off. I have paid over $350 in service calls with no resolution. Did you find resolution?
3
0