Skip to main content
user_p6a178's profile
user_p6a178
1st Reply
1st Topic

New Poster

 • 

5 Messages

10/07/2026 10:00 AM

Started Unicast Maintenance Ranging - No Response received - T3 time-out (like so many others)

This problem seems to be more common than we know! This problem started a couple of months ago. I am kind of nerdy and check my Netgear CAX80 logs EVERYDAY! Like I said, this started a couple of months ago, but something else started a couple of months ago as well. Channel 194 is now Channel 0 and is unlocked... When channel 194, or 193 for that matter switches its ID to channel 0 and shows an unlocked status, it means your cable modem has completely lost its connection to the ultra-high-speed DOCSIS 3.1 signal from your Internet Service Provider (ISP). I had Xfinity come out. They changed the drop from the telephone pole and changed the wall connectors at my three cable outlets. They removed a VERY expensive swivel cable that connected the wall outlet to my router and put in their standard cable. Fact is, he never even asked to do it. I just saw my swivel cable sitting there rolled up and their typical cable installed. At the time I thought, well maybe it could drop signal... No, the problem still persists! I already cleared my logs for the day, but I'll be back tomorrow to share my event log and cable info log...

Question

 • 

Updated 

42 minutes ago

21

2

0

Oldest First
Selected Oldest First
XfinityJustinM

Official Employee

 • 

1.1K Messages

1 day ago

Hi @user_p6a178, 

Thanks for visiting our community forums support page again. I dig your "about me" section, by the way! Have those T3 timeouts, persisted? We'd be more than happy to take a closer look. I'd suggest sending over those logs you mentioned. 

4

0

user_p6a178

New Poster

 • 

5 Messages

@XfinityJustinM​ ok, let's see how we do this...

Cable Info Log:

Cable Diagnostic

Status: Good

Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.

Internet Access: Good

Downstream Status: Good

    Downstream Power Level: Good

    Downstream SNR: Good

Upstream Status:  Good

    Upstream Power Level: Good


Current time: Sat Oct 10 09:04:38 2026

Startup Procedure
Acquire Downstream Channel: 819 MHz   Locked
Connectivity State:          OK       Operational
Boot State:                  OK       Operational
Security:                   Enabled   BPI+


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID  Frequency        Power       SNR   Correctables Uncorrectables     
      1     Locked     256 QAM     28     819000000 Hz     -1.1 dBmV     44 dB     0     0
      2     Locked     256 QAM      1     387000000 Hz     -1.1 dBmV     45.5 dB     0     0
      3     Locked     256 QAM      2     393000000 Hz     -1.5 dBmV     45.3 dB     0     0
      4     Locked     256 QAM      3     399000000 Hz     -1.5 dBmV     45.3 dB     0     0
      5     Locked     256 QAM      4     405000000 Hz     -1.4 dBmV     45.3 dB     0     0
      6     Locked     256 QAM      5     411000000 Hz     -1.5 dBmV     45.2 dB     0     0
      7     Locked     256 QAM      6     417000000 Hz     -1.6 dBmV     45.4 dB     11     0
      8     Locked     256 QAM      7     423000000 Hz     -1.4 dBmV     45.4 dB     16     0
      9     Locked     256 QAM      8     429000000 Hz     -1.4 dBmV     45.4 dB     12     0
     10     Locked     256 QAM      9     435000000 Hz     -1.5 dBmV     45.3 dB     0     0
     11     Locked     256 QAM     10     441000000 Hz     -1.7 dBmV     45.2 dB     0     0
     12     Locked     256 QAM     11     447000000 Hz     -1.7 dBmV     45.2 dB     0     0
     13     Locked     256 QAM     12     453000000 Hz     -1.7 dBmV     45.2 dB     0     0
     14     Locked     256 QAM     13     459000000 Hz     -1.9 dBmV     45.1 dB     19     0
     15     Locked     256 QAM     14     465000000 Hz     -1.8 dBmV     45.2 dB     30     0
     16     Locked     256 QAM     15     471000000 Hz     -1.8 dBmV     45.2 dB     22     0
     17     Locked     256 QAM     16     477000000 Hz     -1.8 dBmV     45.2 dB     0     0
     18     Locked     256 QAM     17     483000000 Hz     -2.1 dBmV     45.1 dB     0     0
     19     Locked     256 QAM     18     489000000 Hz     -2 dBmV     45 dB     0     0
     20     Locked     256 QAM     19     495000000 Hz     -1.6 dBmV     45.3 dB     0     0
     21     Locked     256 QAM     20     765000000 Hz     -2.3 dBmV     44.3 dB     32     0
     22     Locked     256 QAM     21     771000000 Hz     -2.8 dBmV     43.8 dB     21     0
     23     Locked     256 QAM     22     777000000 Hz     -2.7 dBmV     43.7 dB     0     0
     24     Locked     256 QAM     23     783000000 Hz     -2.6 dBmV     43.8 dB     0     0
     25     Locked     256 QAM     24     789000000 Hz     -2.5 dBmV     43.8 dB     0     0
     26     Locked     256 QAM     25     801000000 Hz     -2 dBmV     44.1 dB     16     0
     27     Locked     256 QAM     26     807000000 Hz     -1.9 dBmV     44.2 dB     11     0
     28     Locked     256 QAM     27     813000000 Hz     -1.6 dBmV     44.3 dB     0     0
     29     Not Locked     Unknown      0     0 Hz     0.0     0.0     0     0
     30     Not Locked     Unknown      0     0 Hz     0.0     0.0     0     0
     31     Not Locked     Unknown      0     0 Hz     0.0     0.0     0     0
     32     Not Locked     Unknown      0     0 Hz     0.0     0.0     0     0


Upstream Bonded Channels
Channel   LockedStatus  ChannelType ChannelID   SymbolRate        Frequency       Power     
      1       Locked       ATDMA     19       5120 Ksym/sec       29200000 Hz       41.3 dBmV
      2       Locked       ATDMA     18       5120 Ksym/sec       22800000 Hz       41.0 dBmV
      3       Locked       ATDMA     17       5120 Ksym/sec       16400000 Hz       41.0 dBmV
      4       Locked       ATDMA     20       5120 Ksym/sec       35600000 Hz       41.3 dBmV
      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


Downstream OFDM Channels
Channel   LockedStatus  ProfileID  ChannelID    Frequency       Power       SNR/MER    ActiveSubcarrier    Unerror    Correctable   Uncorrectable
      1     Locked     0 ,1 ,2 ,3     193     900000000 Hz     -0.62 dBmV     44.1 dB     268 ~ 3827     18991039160     1951177227     0
      2     Not Locked     0      0     0 Hz     0 dBmV     0 dB     0 ~ 4095     0     0     0


Upstream OFDMA Channels
Channel   LockedStatus    ProfileID    ChannelID    Frequency       Power
      1     Not Locked     0      0     0 Hz     0 dBmV
      2     Not Locked     0      0     0 Hz     0 dBmV

_____________________________________________________________________________________________________________________


Event Log:

Sat Oct 10 06:40:02 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 04:26:44 2026 Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 02:31:50 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 02:29:07 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 01:31:45 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 01:26:52 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 00:41:06 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 00:40:10 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Oct 10 00:39:40 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 23:33:54 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 23:31:32 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 21:55:59 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 21:49:50 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 20:56:04 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 20:54:18 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 20:31:13 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 20:28:07 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 20:07:39 2026 Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 11:49:13 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 11:42:59 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 11:24:55 2026 Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 04:41:02 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 04:37:22 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 01:08:41 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Fri Oct 9 01:03:17 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 23:49:44 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 23:47:40 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 20:47:34 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 20:40:41 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 20:24:37 2026 Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 20:17:08 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 20:14:37 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 19:51:54 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 19:46:29 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 19:23:39 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 19:17:56 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 18:26:23 2026 Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 18:16:05 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Thu Oct 8 18:12:53 2026 Notice (6)  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;

 

(edited)

Like

Reply

5 hours ago

0

XfinityJustinM

Official Employee

 • 

1.1K Messages

Thanks for shooting that over, @user_p6a178. Now a few T3 timeouts as you may already know shouldn't raise too many alarm bells. How has your experience been alongside those timeouts? 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

4 hours ago

0

user_p6a178

New Poster

 • 

5 Messages

It started at the same time OFDM Downstream channel 194 went from locked to Channel 0 unlocked... I am only getting 100 to 400 mbps when I was getting 900 to 1,100 mbps before. I pay for a 1 gig service!

Like

Reply

1 hour ago

0

XfinityJustinM

Official Employee

 • 

1.1K Messages

Alright, that's a side of things I can attack from. I want to review some of your configuration on my end, @user_p6a178. To get started can you please send our team a direct message with your full name and service address.

How to Send Us a Direct Message:

1.  Click "Sign In" if necessary.

2.  Click the "Direct Messaging" icon.

3.  Click the "Start new conversation" (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.  A "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.
 

How to: Direct messaging within the forum | Xfinity Community Forum

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

52 minutes ago

0

EG

Expert

 • 

122K Messages

42 minutes ago

@user_p6a178 @XfinityJustinM 

Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

0

0

forum icon

New to the Community?

Start Here