NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Jimkowal's avatar
Jimkowal
Initiate
Jan 07, 2024

My download speeds are half what they were 6 months ago

I got the same email from Comcast.  My download speeds are half what they were 6 months ago (just checked and got 471 Mbs). I also experience periodic loss of connection. 

 

My firmware is V2.01.03

 

Is Netgear really working on this?  

4 Replies


  • Jimkowal wrote:

    I got the same email from Comcast.  My download speeds are half what they were 6 months ago (just checked and got 471 Mbs). I also experience periodic loss of connection. 

     

    My firmware is V2.01.03

     

    Is Netgear really working on this?  


    I am also running a CM2050V with firmware V2.01.03.  Download averaging 1150-1170 Mbps to my router, as shown with the Netgear mobile application.

     

    Stability is not the greatest.  I blame that on the Comcast upgrade work that is going on in my area.

     

    I am not with Netgear.  Several weeks ago it was reported from a couple of sources that Netgear has action to update the firmware.  No recent status updates.

     

     

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    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-modem-modem-router
    https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
    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.
    Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended. 
    What is the brand and model of the host wifi router connected to the modem?


    Jimkowal wrote:

    I got the same email from Comcast.  My download speeds are half what they were 6 months ago (just checked and got 471 Mbs). I also experience periodic loss of connection. 

     

    My firmware is V2.01.03

     

    Is Netgear really working on this?  


     

    • Jimkowal's avatar
      Jimkowal
      Initiate

      My router is a Netgear AC1750 model R6700v2

      This is from the modem:

      Modem Status
      Hardware Version1.01
      Cable Firmware VersionV2.01.03
      Cable Modem Serial Number6921267xxxxxx
      CM CertificateInstalled
      CM MAC08:36:c9:b4:1d:40
       
      Event Log
       
      TimePriorityDescription
      Wed Jan 17 04:38:01 2024(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jan 17 01:24:29 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jan 17 01:20:13 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jan 17 00:06:12 2024(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 40 42 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jan 17 00:06:06 2024(Warning (5))MDD message timeout;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:53:23 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:52:52 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:34:53 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:31:07 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:17:27 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 19:10:53 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:58:21 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:53:33 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:48:17 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:41:24 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:17:52 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:15:01 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:08:16 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:07:08 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:06:21 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 18:02:12 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:45:01 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:38:38 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:37:56 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:30:51 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:30:06 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:28:53 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:28:47 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:27:29 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:26:50 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 17:24:28 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:40:53 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:39:40 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:17:24 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:16:00 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:13:34 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:07:41 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 15:01:44 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 13:43:41 2024(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.;CM-MAC=08:36:c9:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;
      Tue Jan 16 13:40:29 2024(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:b4:1c:30;CMTS-MAC=00:90:f0:21:02:00;CM-QOS=1.1;CM-VER=3.1;