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

Forum Discussion

Alpha1991's avatar
Alpha1991
Aspirant
Jun 14, 2023

CM1000v2 modem with slow speeds of 480mbps

I have been using my CM1000v2 Modem for the past six months. My plan with xfinity is 1200 Mbps. I recently gotten in contact with them and they send an electrician over. They fixed an issued on the ou...
Alpha1991's avatar
Alpha1991
Aspirant
Jun 15, 2023
What is the brand name and model number of the router you have connected downstream of your CM1000v2?

I am a bit confused by this, what do you mean? I thought that was private information. Sorry! New to all of this. I will send out what router log said.
Kitsap's avatar
Kitsap
Master
Jun 15, 2023
Alpha1991 wrote:
What is the brand name and model number of the router you have connected downstream of your CM1000v2?

I am a bit confused by this, what do you mean? I thought that was private information. Sorry! New to all of this. I will send out what router log said.

Just exactly what it says.  You are complaining about the throughput performance of a cable modem, CM1000v2.

 

Downstream of that modem you should have a router of some unknown brand name and unknown model number that you connect to some unknown device where you are testing performance.  Difficult to provide assistance without knowing what hardware is connected in the data stream path.

 

When you say send out what router log said, nothing is found.  Where did you send it?

  • Alpha1991's avatar
    Alpha1991
    Aspirant
    Jun 15, 2023
    2023-06-15, 13:15:55Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 13:13:47Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 04:06:01Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 04:03:59Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 04:01:26Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 04:01:25Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:30:44Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:28:36Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:10:03Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:08:01Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:05:58Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 03:05:47Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 01:37:38Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-15, 01:37:32Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
    Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 17:49:06Critical (3)Resetting the cable modem due to docsDevResetNow
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 17:19:42Critical (3)Resetting the cable modem due to docsDevResetNow
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 16:03:29Critical (3)Resetting the cable modem due to docsDevResetNow
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 15:50:46Critical (3)Resetting the cable modem due to docsDevResetNow
    2023-06-14, 14:06:27Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:06:22Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:03:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:03:43Critical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:03:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:03:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:02:01Critical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:01:57Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:01:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:01:55Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:01:55Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    2023-06-14, 14:01:55Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
    • FURRYe38's avatar
      FURRYe38
      Guru - Experienced User
      Jun 18, 2023

      Any Criticals, Errors or Warnings seen in the Event logs needs to be reviewed and resolved by the ISP.

       

      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.

      Alpha1991 wrote:
      2023-06-15, 13:15:55 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 13:13:47 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 04:06:01 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 04:03:59 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 04:01:26 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 04:01:25 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:30:44 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:28:36 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:10:03 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:08:01 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:05:58 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 03:05:47 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 01:37:38 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-15, 01:37:32 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;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=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;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=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 17:49:06 Critical (3) Resetting the cable modem due to docsDevResetNow
      Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;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=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 17:19:42 Critical (3) Resetting the cable modem due to docsDevResetNow
      Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;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=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 16:03:29 Critical (3) Resetting the cable modem due to docsDevResetNow
      Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;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=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 15:50:46 Critical (3) Resetting the cable modem due to docsDevResetNow
      2023-06-14, 14:06:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:06:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:03:45 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:03:43 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:03:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:03:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:02:01 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:01:57 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:01:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:01:55 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:01:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
      2023-06-14, 14:01:55 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;

       

       

  • Alpha1991's avatar
    Alpha1991
    Aspirant
    Jun 15, 2023

    Sorry, I read that wrong, my router is the "nighthawk pro gaming WIFI6 Gaming Router XR1000"

    • Kitsap's avatar
      Kitsap
      Master
      Jun 15, 2023

      Repeat question:  Do you have a PC that you can directly connect to the CM1000v2 with an Ethernet cable and test your throughput?

       

      How is your unknown test device connected to your XR1000?  Via Wi-Fi or via Ethernet cable.

       

      How are you testing your throughput on your unknown test device?  Are you using an application?  A web browser and some testing address?

       

       

      • Alpha1991's avatar
        Alpha1991
        Aspirant
        Jun 15, 2023
        Repeat question:  Do you have a PC that you can directly connect to the CM1000v2 with an Ethernet cable and test your throughput?
         
        I do!



        How is your unknown test device connected to your XR1000?  Via Wi-Fi or via Ethernet cable.
         
        Usually I do test with the Nighthawk app.
        3 weeks ago, I noticed the difference in speed because I play intense games. So my latency was high 100 when I usually get 10-14 ping. So this happen out of nowhere.

        The last log on the app was at 890 Mbps Upload was 42 MBPS and ping was 13 June 2,2023

        Now is at 574.50 Mbps Upload 41.93 Mbps Ping
        52.0. Let me remind that I have 1.2 gbps for internet.


        How are you testing your throughput on your unknown test device?  Are you using an application?  A web browser and some testing address?

        Nighthawk app hasn’t failed me with testing speed. This is the first time I have troubles with my speed since I usually have been running at 800 and had no issues for the past 7 months.