Skip to main content

    Support

    Offers

U
user_uwixj4
1st Topic
1st Reply
Conversation Starter

11 Messages

Tuesday, July 8th, 2025 4:07 PM

Frequent outages that last 1 to 5 minutes

I had a similar problem last year. Cable changed form pole to modem. I haven't made any changes since then so there are no unnecessary splitters, etc.

I made an appointment for a tech to come and they are scheduled for this Friday morning. Posting here just to make sure keeping the appointment is a good idea.

Last years thread with all the details:

https://forums.xfinity.com/conversations/your-home-network/internet-keeps-going-out-modem-reboot-resolves/66a918451466ce252a85da03

Logs from today:

Thu Jul 03 16:19:52 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu Jul 03 16:20:05 2025    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40...................................:00;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:20:14 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40.........................................:00;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:20:35 2025    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:.........................................::00;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:20:58 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:21:11 2025    Notice (6)   Received REG-RSP while in REG-HOLD1 state;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:25:59 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:26:05 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu Jul 03 16:27:05 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40.............................:;CMTS-MAC=00:90:.......................:-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:28:10 2025    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40.......................;CMTS-MAC=00:90:..................................-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:28:28 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40.......................;CMTS-MAC=00:90:.............;CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:28:47 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu Jul 03 16:29:23 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90:...............;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:29:30 2025    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:................;CMTS-MAC=00:90.......................;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 16:29:43 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:3.....................;CMTS-MAC=00:90...................CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:29:59 2025    Notice (6)   Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:40...................;CMTS-MAC=00:90:...................CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:30:00 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40..................;CMTS-MAC=00:90................CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:30:05 2025    Notice (6)   Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:40:3..................;CMTS-MAC=00:90:................;CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:32:03 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:3..................;CMTS-MAC=00:9........................;CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 16:32:07 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu Jul 03 17:13:33 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:................;CMTS-MAC=00:9......................;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 17:14:38 2025    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40.............;CMTS-MAC=00:90:f.................;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 03 17:15:01 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:.................;CMTS-MAC=00:90....................CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 17:15:23 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................CM-QOS=1.0;CM-VER=3.0; 
 Thu Jul 03 17:15:26 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Tue Jul 08 08:08:41 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90.......................-QOS=1.1;CM-VER=3.0; 
 Tue Jul 08 08:08:41 2025    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 08 08:08:45 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:65:a0:82;CMTS-MAC=00:90.......................;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 08 08:09:51 2025    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:.......................;CMTS-MAC=00:.......................-QOS=1.1;CM-VER=3.0; 
 Tue Jul 08 08:10:13 2025    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:.......................-MAC=00:90:f.......................;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 08 08:10:39 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 08 08:10:42 2025    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Tue Jul 08 10:35:24 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40..........;CMTS-MAC=00:90:...................;CM-QOS=1.1;CM-VER=3.0; 

Connection



   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 411000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  



   Connection Status    
   System Up Time 41 days 01h:17m:09s  
  
   Network Access Allowed  
  



   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 4 411.0 0.5 43.0 5966 5084
2 Locked QAM256 1 393.0 0.2 43.2 6477 4261
3 Locked QAM256 2 399.0 0.3 43.2 5942 4718
4 Locked QAM256 3 405.0 0.4 43.2 6233 4189
5 Locked QAM256 5 417.0 0.5 43.3 5778 4052
6 Locked QAM256 6 423.0 0.7 43.4 5615 4116
7 Locked QAM256 7 429.0 0.8 43.4 5663 4056
8 Locked QAM256 8 435.0 0.9 43.5 5493 4133
9 Locked QAM256 9 441.0 1.0 43.4 5444 3397
10 Locked QAM256 10 447.0 1.0 43.4 5183 4280
11 Locked QAM256 11 453.0 1.1 43.5 5116 4025
12 Locked QAM256 12 459.0 1.2 43.5 4827 3830
13 Locked QAM256 13 465.0 1.2 43.5 4710 3488
14 Locked QAM256 14 471.0 1.3 43.1 4938 3421
15 Locked QAM256 15 477.0 1.3 43.4 4702 3821
16 Locked QAM256 16 483.0 1.3 43.3 4491 3459
17 Locked QAM256 17 489.0 1.4 45.7 4607 5985
18 Locked QAM256 18 495.0 1.5 45.6 4417 5873
19 Locked QAM256 19 501.0 1.4 45.8 4525 5786
20 Locked QAM256 20 507.0 1.4 45.8 4500 5682
21 Locked QAM256 21 513.0 1.3 45.6 4234 5677
22 Locked QAM256 22 519.0 1.3 45.7 4166 5334
23 Locked QAM256 23 525.0 1.3 45.6 4301 5240
24 Locked QAM256 24 531.0 1.2 45.6 4116 5275
Total             121444 109182



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 1 5120 16.4 50.3
2 Locked ATDMA 2 5120 22.8 51.0
3 Locked ATDMA 3 5120 29.2 50.9
4 Locked ATDMA 4 5120 35.6 52.4
5 Not Locked Unknown 0 0 0 0.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0

Question

 • 

Updated 

6 hours ago

 • Edited

8

1

0

EG

Expert

 • 

111.5K Messages

6 hours ago

The upstream power is still too high as it was last year. This needs to be addressed !

If there is nothing more that you can do to improve the connection quality, then you'll need to get the techs involved again until it gets fixed properly. 

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.


Good luck !

0

0

forum icon

New to the Community?

Start Here