user_m145's profile

Frequent Visitor

 • 

15 Messages

Sunday, October 27th, 2024 10:41 AM

Upstream issues and modem errors.

I'm on the "superfast" plan which is 800mbps down and 20mbps up. Recently though I've been having issues with my upstream, and have barely been able to get 10mbps upload (even at non peak hours) with downstream being unaffected. I've already ran through all the usual trouble shooting steps, like power cycling and direct connecting the modem to a pc bypassing any and all network equipment to no avail. Something strange I noticed when checking my modems event log was a large amount of errors. The modem is a Netgear Nighthawk CM2050V, it was purchased just a few months ago and has been working without issue until recently. Below I'll include both the event log errors and my status page.

Time Priority Description
Sun Oct 27 05:18:12 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:18:03 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:59 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:58 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:58 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:57 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:53 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:52 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:17:47 2024 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Time Not Established (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:09:19 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:51 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:38 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:38 2024 (Critical (3)) UCD invalid or channel unusable;[Edited: "Personal Information"];CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:34 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:34 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:32 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:32 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:27 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:25 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 27 05:08:20 2024 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Time Not Established (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:40:24 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:36:08 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:33:49 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:33:25 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:33:18 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:13:18 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 09:12:49 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:52:42 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:52:35 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:52:33 2024 (Warning (5)) Dynamic Range Window violation
Sat Oct 26 08:52:33 2024 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:32:28 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:32:20 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 26 08:32:12 2024 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Procedure Status Comment
Acquire Downstream Channel 489000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 489000000 Hz -2.3 dBmV 44.4 dB 0 0
2 Locked QAM256 13 447000000 Hz -1.9 dBmV 44.7 dB 0 0
3 Locked QAM256 14 453000000 Hz -2.4 dBmV 44.5 dB 0 0
4 Locked QAM256 15 459000000 Hz -2.2 dBmV 44.5 dB 0 0
5 Locked QAM256 16 465000000 Hz -2.2 dBmV 44.5 dB 0 0
6 Locked QAM256 17 471000000 Hz -2.6 dBmV 44.3 dB 0 0
7 Locked QAM256 18 477000000 Hz -2.1 dBmV 44.5 dB 0 0
8 Locked QAM256 19 483000000 Hz -1.8 dBmV 44.7 dB 0 0
9 Locked QAM256 21 495000000 Hz -2.0 dBmV 44.6 dB 0 0
10 Locked QAM256 22 501000000 Hz -2.0 dBmV 44.6 dB 0 0
11 Locked QAM256 23 507000000 Hz -2.1 dBmV 44.6 dB 0 0
12 Locked QAM256 24 513000000 Hz -2.0 dBmV 44.7 dB 0 0
13 Locked QAM256 25 519000000 Hz -2.0 dBmV 44.6 dB 0 0
14 Locked QAM256 26 525000000 Hz -2.4 dBmV 44.3 dB 0 0
15 Locked QAM256 27 531000000 Hz -2.6 dBmV 44.3 dB 0 0
16 Locked QAM256 28 537000000 Hz -2.5 dBmV 44.3 dB 0 0
17 Locked QAM256 29 543000000 Hz -2.4 dBmV 44.3 dB 0 0
18 Locked QAM256 30 549000000 Hz -2.7 dBmV 44.2 dB 0 0
19 Locked QAM256 31 555000000 Hz -2.7 dBmV 44.2 dB 0 0
20 Locked QAM256 32 561000000 Hz -2.5 dBmV 44.2 dB 0 0
21 Locked QAM256 33 567000000 Hz -3.0 dBmV 43.8 dB 0 0
22 Locked QAM256 34 573000000 Hz -2.3 dBmV 44.3 dB 0 0
23 Locked QAM256 35 579000000 Hz -1.9 dBmV 44.4 dB 0 0
24 Locked QAM256 36 585000000 Hz -2.3 dBmV 44.3 dB 0 0
25 Locked QAM256 37 591000000 Hz -2.3 dBmV 44.1 dB 0 0
26 Locked QAM256 38 597000000 Hz -1.9 dBmV 44.2 dB 0 0
27 Locked QAM256 39 603000000 Hz -2.6 dBmV 43.9 dB 0 0
28 Locked QAM256 40 609000000 Hz -2.5 dBmV 43.9 dB 0 0
29 Locked QAM256 41 615000000 Hz -2.0 dBmV 44.1 dB 0 0
30 Locked QAM256 42 621000000 Hz -3.0 dBmV 43.6 dB 0 0
31 Locked QAM256 43 627000000 Hz -3.0 dBmV 43.6 dB 0 0
32 Locked QAM256 44 633000000 Hz -2.7 dBmV 43.4 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 16400000 Hz 59.0 dBmV
2 Locked ATDMA 18 5120 22800000 Hz 57.8 dBmV
3 Locked ATDMA 19 5120 29200000 Hz 56.0 dBmV
4 Locked ATDMA 20 5120 35600000 Hz 55.8 dBmV
5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1 Locked 0 ,1 ,2 ,3 193 690000000 Hz -2.4 dBmV 43.2 dB 328 ~ 3767 5537105 3904754 0
2 Locked 0 ,1 ,2 ,3 194 957000000 Hz -8.5 dBmV 40.4 dB 148 ~ 3947 5578227 5335037 0
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

Expert

 • 

107.1K Messages

27 days ago

The upstream power is way too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

Frequent Visitor

 • 

15 Messages

@EG​ Thank you for the reply. I was able to speak with an agent over chat and they said there was some kind of outage (their words not mine) in my area specifically related to upstream. Unfortunately they weren't very specific about what the problem was or when it might be resolved. Could something like that be causing this, and would it still be worth having a tech come out?

Expert

 • 

107.1K Messages

27 days ago

Quite welcome ! It could be local to you or farther up the line somewhere. If the upstream power is still that high then that needs to be addressed. Have you tried any of those tips ?

Frequent Visitor

 • 

15 Messages

@EG​ I took a quick look at the cables but didn't notice any external damage, we haven't made any changes or moved them at all. It's definitely possible that one of them has been damaged internally from age but I wouldn't have any way of knowing without replacing them. We do also have a splitter, but again I saw no damage and wouldn't know if it was without replacing it. I assume at this point its best if I just schedule a tech to come out and check things over.

Expert

 • 

107.1K Messages

27 days ago

Yes. If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated. 


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 ! Please post back here with how things turn out.

Frequent Visitor

 • 

15 Messages

26 days ago

Just as a quick update to this, I work nights and all my testing and troubleshooting has been done during the night and early morning. Something I realized was that during the day (around 11am) the upstream is completely fine. Is there a representative from xfinity that can confirm whether this some kind of work or maintenance going on during the night that would cause this? I'm still scheduling a tech visit to check all the lines, but clearly something is happening at night that is causing upstream issues that isn't happening during the day time.

Official Employee

 • 

2.8K Messages

@user_m145 Thank you for taking the time to reach out to us here on our Xfinity Forums. I agree with @EG, we may need to consider getting a technician back out. I definitely want to take a look at the signals on our end, as well if there has been any maintenance happening in the evening. Please send us a DM to Xfinity Support with your full name and address to get started. 

 

To send a direct message:
Click "Sign In" if necessary
Click the "Direct Message" icon or  https://forums.xfinity.com/direct-messaging
Click the "New message" (pen 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.
A "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

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 a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here