Skip to main content
user_aq0p1q
1st Topic
1st Reply

Visitor

 • 

2 Messages

Monday, August 3rd, 2026 11:12 PM

Three weeks of intermittent drops, multiple times per day/week, lasting 2 minutes to 2 hours

Not a WiFi issues, router logs WAN loss, cable modem in bridge mode behind a UDR7.

Please pull the flap history and signal levels of the modem over the last 30 days

Modem Logs:

Sat Aug 01 16:05:47 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 06:29:27 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 06:59:37 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 11:28:07 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 17:17:23 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 18:10:41 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Sun Aug 02 20:33:03 2026   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; 
Sun Aug 02 20:41:12 2026   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; 
Mon Aug 03 06:32:48 2026   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; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Warning (5)  B-INIT-RNG Failure - Retries exceeded;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Notice (6)  Honoring MDD; IP provisioning mode = IPv6 
Mon Aug 03 10:30:40 2026   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; 
Mon Aug 03 10:34:21 2026   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; 
Mon Aug 03 11:05:03 2026   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; 
Mon Aug 03 11:08:01 2026   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; 
Mon Aug 03 11:16:21 2026   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; 
Mon Aug 03 11:21:22 2026   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; 
Mon Aug 03 14:55:17 2026   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; 

Question

 • 

Updated 

4 hours ago

 • Edited

21

3

0

Oldest First
Selected Oldest First
user_aq0p1q

Visitor

 • 

2 Messages

22 hours ago

 Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 20 5120 35.6 54.0
2 Locked ATDMA 17 5120 16.4 45.7
3 Locked ATDMA 18 5120 22.8 45.7
4 Locked ATDMA 19 5120 29.2 45.7

0

0

XfinityCliff

Official Employee

 • 

481 Messages

22 hours ago

Hello @user_aq0p1q, and thanks for reaching out on our Xfinity Community forums with your concerns regarding your internet connection.

I can see why this would be frustrating. Intermittent connectivity issues that have been occurring for weeks, especially when your router logs show WAN loss events and the modem is generating repeated T3 timeout errors, can make it difficult to maintain a reliable connection.

We'd like to take a closer look at the modem's history and the health of the connection. Please send us a Direct Message* with your full name and complete service address, and we'll review the account, and check the modem's signal levels and circuit logs.

How to Send Us a Direct Message*:
(*Note: Never send a direct message to us unless requested by us.)

  1. Click "Sign In" if necessary.
  2. Click the "Direct Messaging" icon or visit Xfinity Direct Messaging.
  3. Click the "New message" (pencil and paper) icon.
  4. In the "To:" line, type "Xfinity Support".
  5. As you type, a drop-down list will appear. Select "Xfinity Support" from that list.
  6. An "Xfinity Support" graphic will replace the "To:" line.
  7. Type your message in the text area near the bottom of the window.
  8. Press Enter to send it.

Click Here For an example of how to send us a Direct Message.

0

0

EG

Expert

 • 

119.8K Messages

4 hours ago

@user_aq0p1q 

The upstream power is too high / out of spec on channel #1. Please also post the *Downstream Power Levels*and the *SNR'* (Signal to Noise Ratio) values here.

0

0

forum icon

New to the Community?

Start Here