Contributor
•
13 Messages
Intermittent Connectivity with T3, T4 Timeouts and no block sync conditions
My current router is a TP-Link AX3000 (first using when problems started. Previous was a TP-Link AC1750 but I have swapped both for testing purposes) and my current modem is a Arris Surfboard SB6183 (previous is a Surfboard SB8200, and is the modem I was first using when the issues started. I have swapped both for testing purposes.)
I have been having intermittent connectivity for more than 4 months now in the form of intermittent dropouts. I have tested with using only a modem and a modem and router combination and the issues persist.
I've had 2 techs come out. First one said that there was noise on the line, did a splice and said everything looked good. I do not have a wall outlet; the coax cable runs through the floorboard of my computer room, through my crawlspace and then outside to my cable box. It is the original coax cable from the initial setup of my cable in 2018.
Last tech that came out said everything is green and could not find a single issue. In my modem's event log (below) the number of T3, T4 timeouts and no block syncs in a span of nearly 8am to noon in one day says otherwise.
This log is from using a modem only connected to my PC.
Time | Priority | Description |
Sun Apr 09 07:46:54 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 07:46:54 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 07:46:54 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 07:51:30 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 07:55:50 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 07:57:49 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:02:09 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:03:20 2023 | Critical (3) | TFTP failed - Request sent - No Response;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:03:20 2023 | Critical (3) | TFTP Request Retries exceeded, CM unable to register |
Sun Apr 09 08:03:28 2023 | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 08:04:11 2023 | Critical (3) | TFTP failed - Request sent - No Response;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:04:11 2023 | Critical (3) | TFTP Request Retries exceeded, CM unable to register |
Sun Apr 09 08:04:14 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:04:30 2023 | Critical (3) | No UCDs Received - Timeout;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:04:47 2023 | Critical (3) | No UCDs Received - Timeout;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:04:54 2023 | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 08:05:40 2023 | Critical (3) | TFTP Failed - OUT OF ORDER packets;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:05:40 2023 | Critical (3) | TFTP Request Retries exceeded, CM unable to register |
Sun Apr 09 08:05:59 2023 | Critical (3) | No UCDs Received - Timeout;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:06:00 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:06:17 2023 | Critical (3) | No UCDs Received - Timeout;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 08:06:24 2023 | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 08:55:04 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:55:04 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:55:04 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:55:21 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:55:21 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:55:21 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 08:58:05 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 09:02:25 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 09:18:36 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 09:18:36 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 09:18:36 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 09:19:20 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 09:23:40 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:10:42 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:10:42 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:10:42 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:11:12 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:11:12 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:11:12 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:15:31 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Sun Apr 09 10:35:34 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:35:34 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:35:34 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:36:15 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:36:15 2023 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:36:15 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:36:15 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 10:40:35 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Time Not Established | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.0;CM-VER=3.0; |
Sun Apr 09 11:23:21 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Sun Apr 09 11:27:41 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Warning (5) | ToD request sent - No Response received;CM-QOS=1.0;CM-VER=3.0; |
As for my channels, I currently have more uncorrectables than corrected. The numbers were way worse when I was using a router after the 1st tech visit, with the number of uncorrectables reaching the hundreds in a single day.
This picture is from April 5th.

Downstream Bonded Channels | ||||||||
---|---|---|---|---|---|---|---|---|
Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Corrected | Uncorrectables |
1 | Locked | QAM256 | 29 | 567000000 Hz | 5.1 dBmV | 38.1 dB | 16 | 17 |
2 | Locked | QAM256 | 30 | 573000000 Hz | 5.2 dBmV | 38.1 dB | 7 | 26 |
3 | Locked | QAM256 | 31 | 579000000 Hz | 5.2 dBmV | 38.2 dB | 20 | 89 |
4 | Locked | QAM256 | 32 | 585000000 Hz | 4.8 dBmV | 38.0 dB | 4 | 30 |
5 | Locked | QAM256 | 34 | 591000000 Hz | 4.8 dBmV | 38.0 dB | 12 | 22 |
6 | Locked | QAM256 | 35 | 597000000 Hz | 5.1 dBmV | 38.0 dB | 12 | 21 |
7 | Locked | QAM256 | 36 | 603000000 Hz | 4.8 dBmV | 38.0 dB | 10 | 68 |
8 | Locked | QAM256 | 37 | 609000000 Hz | 4.8 dBmV | 37.9 dB | 8 | 27 |
9 | Locked | QAM256 | 38 | 615000000 Hz | 4.8 dBmV | 37.9 dB | 11 | 38 |
10 | Locked | QAM256 | 39 | 621000000 Hz | 4.9 dBmV | 37.8 dB | 4 | 37 |
11 | Locked | QAM256 | 40 | 627000000 Hz | 4.9 dBmV | 37.8 dB | 11 | 43 |
12 | Locked | QAM256 | 41 | 633000000 Hz | 5.1 dBmV | 37.9 dB | 9 | 39 |
13 | Locked | QAM256 | 42 | 639000000 Hz | 4.9 dBmV | 37.7 dB | 19 | 93 |
14 | Locked | QAM256 | 43 | 645000000 Hz | 4.9 dBmV | 37.7 dB | 16 | 65 |
15 | Locked | QAM256 | 44 | 651000000 Hz | 4.9 dBmV | 37.7 dB | 21 | 81 |
16 | Locked | QAM256 | 45 | 657000000 Hz | 5.1 dBmV | 37.7 dB | 15 | 43 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
1 | Locked | ATDMA | 32 | 5120 Ksym/sec | 35600000 Hz | 42.5 dBmV |
2 | Locked | ATDMA | 29 | 5120 Ksym/sec | 16300000 Hz | 42.8 dBmV |
3 | Locked | ATDMA | 30 | 5120 Ksym/sec | 22800000 Hz | 42.5 dBmV |
4 | Locked | ATDMA | 31 | 5120 Ksym/sec | 29200000 Hz | 42.5 dBmV |
Current thoughts are that maybe my coaxial cable needs replaced, the cable in my cable box needing replaced, the cable leading from the box to the utility pole needs looked at or the CMTS in my area needs looked at.
Any help is greatly appreciated. I have the option to have an Xfinity representative send out a special request for a local team to come out and find issues but I would like any second opinions or observations before I green light it as I would like to try and keep things simple and low cost.
EDIT*
LITERALLY after posting this 10 minutes ago, a T3 timeout happened and my current uncorrectables shot up into the hundreds.
EG
Expert
•
110K Messages
2 years ago
Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
2
EG
Expert
•
110K Messages
2 years 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 poll the CMTS for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
@EG Thank you very much!
Just for good measure, here is the most recent status on my channels and event log:
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Ok, I have a technician coming this Thursday. Xfinity Support sent a configuration signal to my modem and found packet loss and areas of signal that are null when they should be polling.
0
0
EG
Expert
•
110K Messages
2 years ago
Please post back here about how things turn out after the tech visit.
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Current channel status for today. A single T3 timeout is only listed in the event log right now (I power cycled the modem yesterday) but the number of uncorrectables is more than corrected so the issue remains despite the robot phone call I got from Comcast today saying that my issue is fixed and that I probably don't need a tech to come out which is the opposite of what I want.
(edited)
1
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
I've also discovered that, according to an FAQ about signal levels for my modem on Arris' website, the acceptable upstream power levels when using ATDMA and a symbol rate of 5120 Ksym/sec are 45 dBmV to 51 dBmV. I've never seen my power levels be 45 or more but the closest I've seen it be is 44.8, which was 8 days ago. Right now, everything is sitting at 43. I don't know if this a great cause for concern but the FAQ does suggest that I have my provider adjust the signal level to the acceptable range.
The link for the FAQ site for my modem is this.
*EDIT
According to new information I found, I should disregard what Arris says as the equipment Comcast uses makes sure my power is at optimal levels.
(edited)
0
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
@EG Two techs came out today, one who was a supervisor who left me their card. They replaced the coaxial cable running from the modem to the box and said that the cable running to the pole is good. They found that the upstream power coming from my modem was 3 dB more than what was being read with the meter or at the box, I don't remember exactly, but they made it so the upstream power coming out matched my modem's. They were not exactly sure if it was really my modem causing this power issue. They also replaced the coaxial cable running from my modem to the box so no more additional splices on my line.
They also said that there was a team at the CMTS doing some testing and they would test the node in my area for any issues.
So far, everything has been fine.
1
0
EG
Expert
•
110K Messages
2 years ago
@user_7c0e97
Here's how to send them a DM......;
To send a direct message (private message);
Click "Sign In" if necessary.
Click the "Direct Message" icon in the upper right corner or https://forums.xfinity.com/direct-messaging
Click the "New message" (pencil and paper) icon.
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there.
As you are typing a drop-down list appears. Select "Xfinity Support" from that list.
An "Xfinity Support" graphic replaces the "To:" line.
Type your message in the text area near the bottom of the window.
Press Enter to send it.
[Permission from and credit given to BruceW].
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Around 7:20pm yesterday, talking to XfinityEthan about the promotional offer for my plan, my internet went off and my modem reset. If this was due to maintenance work at the CMTS or the node in my area or the same issue that has been plaguing me, I don't know.
Here is my current channels status and event log:
(edited)
0
0
user_934a37
Visitor
•
1 Message
2 years ago
Hello,
I too have been dealing with numerous T3 timeouts/intermittent connectivity issues here in the Indianapolis area for the past several months. I've reached out to Xfinity countless times, and have yet to receive a resolution. I was told my hardware was to blame, even though the issue started with my Netgear Nighthawk AC1900, but continued when I upgraded to a combination of the Arris Surfboard SB8200 and TP-Link Deco AX3000, and then continued further when I replaced my modem with the Arris Surfboard S33 at the recommendation of Xfinity (as I later upgraded to the 1Gbps download plan).
A technician has come out twice and has confirmed everything looks good in my home, as well as outside of my home, regarding coax.
The last visit the technician told me monitoring would be set up to check the node near my home. I never heard back about this.
I am reaching out to Xfinity via this forum in hopes of finally getting a resolution. I have been customer for roughly 6 years and will be switching to T-Mobile if this is not resolved when the tech visits for the 3rd time tomorrow.
1
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
@XfinityEthan is there an update on the node issue?
So far I'm still getting uncorrectables and T3 Timeouts but thankfully the issue seems to be nowhere near how it was before. As for the uncorrectables and T3s, I do not know if this is normal for almost 2 days of uptime for my modem (I power cycled it on the 13th) @EG .
My channels and event log for today:
(edited)
0
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Well what timing, my internet just went off at 3:02pm and is still off. I'm on my phone.
(edited)
0
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Seems I spoke too soon. Just had a T4 timeout and the modem reset. I see I also had a T2 timeout.
(edited)
2
0
user_7c0e97
Contributor
•
13 Messages
2 years ago
Dang, it just went off again.
0
0