New modem (CM2000) upstream status light keeps blinking

Hello all,

Just activated Netgear CM2000 cable modem with the Xfinity app. However i notice that the upstream light is constantly blinking.

I logged in the modem to check the logs and i see upstream has this message under Upstream status:

Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete.

Prior to this i had used Netgear CM600 and did not have this issue. On the CM600 upstream light was solid.

I checked to make sure all cables are snug and i see not issue there.

Now i can use the internet, but gaming is impossible, there is so much latency, and it happens every 30 sec or so.

I restarted the modem couple of times, but no luck, upstream stays blinking.

Here is more more information from the cable modem:

Hardware Version	1.01

Cable Firmware Version	V8.01.02

Advanced Information

Frequency Start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	627000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enabled	BPI+
IP Provisioning Mode	Honor MDD	IPv6 only

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	33	627000000 Hz	3.3 dBmV	39.3 dB	52	0
2	Locked	QAM256	10	483000000 Hz	4.8 dBmV	41.1 dB	1	0
3	Locked	QAM256	11	489000000 Hz	4.4 dBmV	40.9 dB	7	0
4	Locked	QAM256	12	495000000 Hz	4.6 dBmV	40.9 dB	5	0
5	Locked	QAM256	13	507000000 Hz	4.6 dBmV	40.9 dB	1	0
6	Locked	QAM256	14	513000000 Hz	4.5 dBmV	40.7 dB	5	0
7	Locked	QAM256	15	519000000 Hz	4.6 dBmV	40.6 dB	7	0
8	Locked	QAM256	16	525000000 Hz	4.6 dBmV	39.9 dB	8	0
9	Locked	QAM256	17	531000000 Hz	4.5 dBmV	40.2 dB	7	0
10	Locked	QAM256	18	537000000 Hz	4.3 dBmV	40.0 dB	10	0
11	Locked	QAM256	19	543000000 Hz	4.2 dBmV	40.4 dB	10	0
12	Locked	QAM256	20	549000000 Hz	4.3 dBmV	40.5 dB	10	0
13	Locked	QAM256	21	555000000 Hz	4.1 dBmV	40.3 dB	15	0
14	Locked	QAM256	22	561000000 Hz	3.9 dBmV	40.1 dB	22	0
15	Locked	QAM256	23	567000000 Hz	3.9 dBmV	39.9 dB	30	0
16	Locked	QAM256	24	573000000 Hz	3.9 dBmV	39.9 dB	34	0
17	Locked	QAM256	25	579000000 Hz	4.0 dBmV	39.9 dB	24	0
18	Locked	QAM256	26	585000000 Hz	4.0 dBmV	39.8 dB	26	0
19	Locked	QAM256	27	591000000 Hz	3.7 dBmV	39.8 dB	28	0
20	Locked	QAM256	28	597000000 Hz	3.8 dBmV	39.5 dB	38	0
21	Locked	QAM256	29	603000000 Hz	3.6 dBmV	39.4 dB	39	0
22	Locked	QAM256	30	609000000 Hz	3.1 dBmV	39.5 dB	37	0
23	Locked	QAM256	31	615000000 Hz	3.2 dBmV	39.4 dB	45	0
24	Locked	QAM256	32	621000000 Hz	3.2 dBmV	39.3 dB	42	0
25	Locked	QAM256	34	633000000 Hz	3.3 dBmV	39.2 dB	42	0
26	Locked	QAM256	35	639000000 Hz	3.2 dBmV	39.0 dB	37	0
27	Locked	QAM256	36	645000000 Hz	3.4 dBmV	39.2 dB	43	0
28	Locked	QAM256	37	651000000 Hz	3.3 dBmV	39.0 dB	59	0
29	Locked	QAM256	38	657000000 Hz	3.2 dBmV	39.0 dB	49	0
30	Locked	QAM256	39	663000000 Hz	3.0 dBmV	38.9 dB	56	0
31	Locked	QAM256	40	669000000 Hz	3.1 dBmV	38.9 dB	67	0
32	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0

Upstream Bonded Channels (Partial Service)

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	1	5120 Ksym/sec	35600000 Hz	47.8 dBmV
2	Not Locked	Unknown	0	0	0	0.0 dBmV
3	Not Locked	Unknown	0	0	0	0.0 dBmV
4	Not Locked	Unknown	0	0	0	0.0 dBmV
5	Locked	ATDMA	5	2560 Ksym/sec	40400000 Hz	46.3 dBmV
6	Not Locked	Unknown	0	0	0	0.0 dBmV
7	Not Locked	Unknown	0	0	0	0.0 dBmV
8	Not Locked	Unknown	0	0	0	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	41	722000000 Hz	3.28 dBmV	38.1 dB	1108 ~ 2987	992276	980273	0
2	Not Locked	0	0	0 Hz	0 dBmV	0 dB	0 ~ 4095	0	0	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

Event Log:

Wed Apr 12 18:02:48 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:02:18 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:02:18 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:02:18 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:01:04 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:01:04 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 18:01:04 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:58:20 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:58:20 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:58:20 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:56:05 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:56:05 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:56:05 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:54:08 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:54:08 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:54:08 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:53:28 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:53:28 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:53:28 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:51:10 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:51:10 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:51:10 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:37 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:37 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:37 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:03 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:03 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:48:03 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:46:52 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:46:52 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:46:52 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:43:40 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:43:40 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:43:40 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:42:52 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:42:52 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:42:52 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:41:44 2023	(Critical (3))	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:41:44 2023	(Critical (3))	Ranging Request Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;
Wed Apr 12 17:41:44 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/aCM-QOS=1.1;CM-VER=3.1;

Responses

Accepted Solution

nermin

New Poster

•

3 Messages

2 years ago

Hello,

You can mark this issue as resolved. I had tech Come to our property. The issue was on the street pol having a bad adapter and sending no signal. They replaced that and the cable from the pol to our home and resolved the issues.

CCValerie

Official Employee

•

974 Messages

Hi there, @nermin, thank you for taking the time to reach back out and updating on our community on the resolution. I am happy to hear a technician was able to get the issue resolved for you! If you have any additional questions or need additional support please feel free to reach back out at anytime. We are available through our Xfinity Forums 24/7!

I no longer work for Comcast.

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

2 years ago

XfinityRoberto

Official Employee

•

1.7K Messages

2 years ago

Hello and welcome to Comcast. Thank you so much for reaching out to us about your new modem issues with the upstream. Now on this modem when the upstream light is blinking, it means that the cable modem is scanning for an upstream channel. I am happy to take a look at the account and see if there is anything affecting the modem.

Could you please send our team a direct message with your full name and full address? Our team can most definitely take a further look at this issue. To send a "Direct Message" ("Private") message:

Click "Sign In" if necessary
Click the "Direct Message” icon (upper right corner of this page)
Click the "New message" (pencil and paper) icon
Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
Type your message in the text area near the bottom of the window
Press Enter to send your message

EG

Expert

•

110.1K Messages

2 years ago

Now closing this marked "solved" topic.

Your Home Network

nermin

New modem (CM2000) upstream status light keeps blinking

nermin

CCValerie

XfinityRoberto

EG

New to the Community?