Nighthawk CM2050V Comcast Firmware Killed Speed

[db3058]

I understand Comcast has just updated the firmware in these routers from V2.01.03 to V9.01.01.  My download speed went from 934 to 225.  Comcast tech came out yesterday and cleared some signal loss but it did nothing to increase the speed back to what it was.  I'm paying for 800.  

Is anyone else having this issue?  Is Comcast killing these routers?

[db3058 · Accepted solution]

I contacted a supervisor who actually responded he could see the modem was not properly provisioned, he opened another ticket and one of their best techs came out.  I think they fixed it from inside but he was excellent.  Problem solved after a month and about 15 tickets opened.   Thanks for the encouragement 

[FURRYe38]

Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Has a power off for 1 minute then back ON with the ISP modem and router been performed since last update?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.

Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended. 
What is the brand and model of the host wifi router connected to the modem?

CM series modems are not routers. Just only modems.

[db3058]

Time	Priority	Description
Tue Sep 26 05:38:37 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 05:33:20 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:28:32 2023	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:28:24 2023	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:28:23 2023	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:28:14 2023	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Tue Sep 26 00:28:06 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:56 2023	(Warning (5))	ToD request sent - No Response received;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:55 2023	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:54 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:54 2023	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:53 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:06 2023	(Warning (5))	MDD message timeout;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:06 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:00 2023	(Warning (5))	MDD message timeout;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 26 00:24:00 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 23:31:45 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 23:26:06 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 23:19:33 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 22:36:04 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 22:27:00 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 20:50:10 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 15:26:40 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 15:19:33 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 14:40:36 2023	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 14:40:30 2023	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:51:38 2023	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:12:40 2023	(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.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:05:08 2023	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:05:02 2023	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:01:14 2023	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:01:13 2023	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 13:01:05 2023	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Mon Sep 25 13:00:58 2023	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 12:58:41 2023	(Warning (5))	ToD request sent - No Response received;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 25 12:58:39 2023	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1;

[Kitsap]

---

@db3058 wrote:

I understand Comcast has just updated the firmware in these routers from V2.01.03 to V9.01.01.  My download speed went from 934 to 225.  Comcast tech came out yesterday and cleared some signal loss but it did nothing to increase the speed back to what it was.  I'm paying for 800.  

Is anyone else having this issue?  Is Comcast killing these routers?

---

The firmware on my CM2050V was updated several days ago.  No degradation in throughput capacity.  No indication elsewhere on the web that the firmware update is killing the modems.

Recommend you use the Ookla stand alone application for testing throughput.  It is available from the play store.  What device are you using to test throughput and how is it connected to the internet?  Maybe via Wi-Fi?

If you are on Windows, check to see if your Network Profile has changed from Private to Public.  If yes, change it back to Private.

Check the router that sets between your modem and whatever device you are using to test throughput.

[FURRYe38]

Please post the cable connections status data page as well.

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

[db3058]

I am measuring the speed on the back of the modem with my laptop.

[Kitsap]

---

@db3058 wrote:

I am measuring the speed on the back of the modem with my laptop.

---

With what application?  Did you check your Network Profile?  Is it Public or Private?

[FURRYe38]

Please post a copy and paste of the modems connection status page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...

[db3058]

https://speedtest.xfinity.com/

[db3058]

Cable Connection

Cancel Apply

Cable Diagnostic Status:   Good Action:   Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help. If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info. CM Status:  Downstream Status:  Upstream Status:  Refresh Save Cable Diagnostic Info 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 573000000 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 28 573000000 Hz -4.1 dBmV 40.5 dB 0 0 2 Locked QAM256 1 405000000 Hz 2.9 dBmV 43.7 dB 0 0 3 Locked QAM256 2 411000000 Hz 2.8 dBmV 43.3 dB 0 0 4 Locked QAM256 3 417000000 Hz 3.0 dBmV 43.7 dB 0 0 5 Locked QAM256 4 423000000 Hz 2.8 dBmV 43.7 dB 0 0 6 Locked QAM256 5 429000000 Hz 2.9 dBmV 43.7 dB 0 0 7 Locked QAM256 6 435000000 Hz 2.9 dBmV 43.8 dB 0 0 8 Locked QAM256 7 441000000 Hz 2.6 dBmV 43.6 dB 0 0 9 Locked QAM256 8 447000000 Hz 2.8 dBmV 43.7 dB 0 0 10 Locked QAM256 9 453000000 Hz 2.6 dBmV 43.7 dB 0 0 11 Locked QAM256 10 459000000 Hz 2.3 dBmV 43.6 dB 0 0 12 Locked QAM256 11 465000000 Hz 2.3 dBmV 43.5 dB 0 0 13 Locked QAM256 12 471000000 Hz 2.0 dBmV 43.4 dB 0 0 14 Locked QAM256 13 477000000 Hz 1.7 dBmV 43.3 dB 0 0 15 Locked QAM256 14 483000000 Hz 1.6 dBmV 43.3 dB 0 0 16 Locked QAM256 15 489000000 Hz 1.5 dBmV 43.2 dB 0 0 17 Locked QAM256 16 495000000 Hz 1.4 dBmV 43.1 dB 0 0 18 Locked QAM256 17 507000000 Hz 1.0 dBmV 43.2 dB 0 0 19 Locked QAM256 18 513000000 Hz 0.6 dBmV 43.1 dB 0 0 20 Locked QAM256 19 519000000 Hz 0.4 dBmV 43.0 dB 0 0 21 Locked QAM256 20 525000000 Hz -0.1 dBmV 42.9 dB 0 0 22 Locked QAM256 21 531000000 Hz -0.6 dBmV 42.6 dB 0 0 23 Locked QAM256 22 537000000 Hz -1.1 dBmV 42.4 dB 0 0 24 Locked QAM256 23 543000000 Hz -1.9 dBmV 41.9 dB 0 0 25 Locked QAM256 24 549000000 Hz -2.3 dBmV 41.7 dB 0 0 26 Locked QAM256 25 555000000 Hz -2.6 dBmV 41.5 dB 0 0 27 Locked QAM256 26 561000000 Hz -3.5 dBmV 40.9 dB 0 0 28 Locked QAM256 27 567000000 Hz -3.6 dBmV 40.8 dB 0 0 29 Locked QAM256 29 579000000 Hz -4.7 dBmV 40.2 dB 0 0 30 Locked QAM256 30 585000000 Hz -4.8 dBmV 40.0 dB 0 0 31 Locked QAM256 31 591000000 Hz -5.1 dBmV 39.7 dB 0 0 32 Locked QAM256 32 597000000 Hz -5.5 dBmV 39.4 dB 0 0   Upstream Bonded Channels   Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 40.3 dBmV 2 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 39.3 dBmV 3 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 38.8 dBmV 4 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 41.0 dBmV 5 Locked ATDMA 21 2560 Ksym/sec 40400000 Hz 40.0 dBmV 6 Locked ATDMA 22 2560 Ksym/sec 10400000 Hz 38.3 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 193 688000000 Hz -7.02 dBmV 34.7 dB 1108 ~ 2987 45058777 43893332 864171 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   Current System Time:Mon Sep 25 14:35:40 2023   System Up Time:01:31:18

Help CenterShow/Hide Help Center

[db3058]

I misspoke...I know

[db3058]

Not changed...private

[FURRYe38]

Power levels are with in spec however power levels across all channels is all over the place. All channels should be with in 3db on each channel. ISP needs to get the channel power with in spec of each other.

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
Be sure your using good quality RG6 coax cable up to the modem. 
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Mod...
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/

[Kitsap]

---

@db3058 wrote:

https://speedtest.xfinity.com/

---

That is a web address that uses a web browser in the data path.

Search for Ookla in the play store.  It is a stand alone installable application that does not use a web browser for the testing.

[db3058]

I opened up a ticket with Comcast cable maintenance, as the issue is escalated.  At this point I've changed everything except the modem.  I could always install my 9 yr old Arris modem...it was clocking over 400 and that would tell me a lot but it's a serious hassle installing any new modem because there are very few people at Comcast who can do anything correctly.  I took many calls and many hours to get this modem installed.  Most of them are complete idiots and bs you with no regard for your time and energy.  If I wasn't retired I would need someone else unemployed to install anything.  It's the plant or the modem...can't be anything else.

[FURRYe38]

Could try one of the ISP modems to see what it does as a temp test. 
But the logs and data show, there is something on the ISP side that needs reviewed. Have the ISP tech look at the info I posted about. 

[Kitsap]

---

@db3058 wrote:

I opened up a ticket with Comcast cable maintenance, as the issue is escalated.  At this point I've changed everything except the modem.  I could always install my 9 yr old Arris modem...it was clocking over 400 and that would tell me a lot but it's a serious hassle installing any new modem because there are very few people at Comcast who can do anything correctly.  I took many calls and many hours to get this modem installed.  Most of them are complete idiots and bs you with no regard for your time and energy.  If I wasn't retired I would need someone else unemployed to install anything.  It's the plant or the modem...can't be anything else.

---

@db3058 

Any updated status on this issue ??

[db3058]

Comcast will not come out until the 11th of October!!!...will update after that.

[Kitsap]

---

@db3058 wrote:

Comcast will not come out until the 11th of October!!!...will update after that.

---

OK  Thank you.

[db3058]

So as I know regardless of diagnostics hardware fails and did in this case.

Comcast came out today and measured the input speed to the back of the modem to 1500mhz.  From the back of the RJ45 on the modem I'm getting 300....200 to my laptop hardwired I was getting 934 a month ago.   It worked for 2 months.

I will post whether or not support who I have an open ticket with under the 3 month hardware warranty replaces my modem. 

[FURRYe38]

This ISP has been working with something call mid-split. Might ask them about this. IF it was working at one point then not, ISP has done something.

[db3058]

The tech who came out here knew his s**t....he was awesome.  The bottom line is I'm getting 1500 mhz into the modem and 200 out.  It's a piece of junk.  I worked outside plant with ATT for 7 years and 30 years as a PBX tech with thousands of circuits. I'm a commercial electrician as well.  I know many times regardless of diagnostics, stuff needs to be replaced.

[Kitsap]

---

@db3058 wrote:

The tech who came out here knew his s**t....he was awesome.  The bottom line is I'm getting 1500 mhz into the modem and 200 out.  It's a piece of junk.  I worked outside plant with ATT for 7 years and 30 years as a PBX tech with thousands of circuits. I'm a commercial electrician as well.  I know many times regardless of diagnostics, stuff needs to be replaced.

---

Hardware fails.  It is a fact of life.  It is also a fact of life firmware updates have errors.  It would not hurt to request Comcast to push the firmware update to your modem again.

[db3058]

Do you work for Netgear?...your responses do not make sense.  There are thousands upon thousands of reviews on the net indicating the modem is junk...I'm the fool who had hope.  I'm the fool who spent 325 bucks on a piece of junk.  I'm pissed. It's despicable that Netgear puts out this garbage with so many negative reviews and people having similar experiences as me...they should be sued. I'll never buy another Netgear product. What I'll get Comcast to do is install their own modem since most of what is out there is crap now.  Then they can replace their own junk when it goes out.  I installed 2 Arris T25's before this and they were both garbage....first one never came up and the second caused constant static on the telephony lines.  I give up and I'm not someone who does. 

[Kitsap]

---

@db3058 wrote:

Do you work for Netgear?...your responses do not make sense.  There are thousands upon thousands of reviews on the net indicating the modem is junk...I'm the fool who had hope.  What I'll get Comcast to do is install their own modem since most of what is out there is crap now.  Then they can replace their own junk when it goes out.  I installed 2 Arris T25's before this and they were both garbage....first one never came up and the second caused constant static on the telephony lines.  I give up and I'm not someone who does. 

---

If you are talking to me, no, I do not work for Netgear.  I am a retired electrical engineer who worked for 45+ years in the communications business.  Mostly machine controls.  I came to this community some years ago and asked for help.  It was willingly provided and resolved the issue I was working on.  I pay the community back when I can.

The sooner you start having Comcast charge your credit card for a gateway lease, the better you will feel.

My CM2050V has been in service since September 2021 and has not missed a beat.  The first firmware update was a few weeks ago as Comcast is working on their infrastructure for the mid-split configuration update.