I spoke with my ISP and they have scheduled a tech to test the line as they are seeing low frequency on the line. Paying for 1 gig, used to get anywhere from 400-700 Mbps down depending on time of day, now I am getting 4-16 Mbps down. Any assistance in isolating the cause would be appreciated. I have a feeling it's the line but want to verify it's not my device before the tech arrives next week. Event log is below. Time Priority Description 2024-1-6, 18:54:44Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE2024-1-6, 18:41:04Warning (5)MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:39:35Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE2024-1-6, 18:23:50Warning (5)MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:23:13Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:09:38Warning (5)MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:09:25Notice (6)TLV-11 - unrecognized OID;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:09:24Error (4)Primary address failed, secondary active;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:09:24Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:01:06Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:47Notice (6)Honoring MDD; IP provisioning mode = APM1970-1-1, 00:00:44Critical (3)No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:41Notice (6)WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT1970-1-1, 00:00:41Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT1970-1-1, 00:00:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-6, 18:07:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-6, 18:02:08Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;2024-1-6, 18:01:40Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:01:08Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:45Critical (3)No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:38Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:01:04Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:42Critical (3)No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-6, 17:45:22Critical (3)Resetting the cable modem due to docsDevResetNow2024-1-6, 17:08:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:01:05Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:43Critical (3)No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-2, 19:07:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-2, 17:51:28Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-2, 14:20:24Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2024-1-1, 19:43:30Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2023-12-27, 18:31:57Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2023-12-25, 17:57:45Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;2023-12-24, 23:54:36Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:01:06Critical (3)DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:44Critical (3)No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-12-23, 04:34:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;

Ok, So power levels are too low and all over the place. Power needs to come up and be with in 3db of each channel. https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-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. You have a ton of correctables and uncorrectables that should be zero. 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-Modems/m-p/1530376#M12853https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.htmlhttps://highspeed.tips/docsis-events/ Get a on site ISP tech out to review all this and get it working better.

DabbinBallZ

Aspirant

Jan 07, 2024

Solved

Slow speed on my Nighthawk C7000v2

I spoke with my ISP and they have scheduled a tech to test the line as they are seeing low frequency on the line. Paying for 1 gig, used to get anywhere from 400-700 Mbps down depending on time of day, now I am getting 4-16 Mbps down. Any assistance in isolating the cause would be appreciated. I have a feeling it's the line but want to verify it's not my device before the tech arrives next week. Event log is below.

Time	Priority	Description
2024-1-6, 18:54:44	Notice (6)	WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2024-1-6, 18:41:04	Warning (5)	MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:39:35	Notice (6)	WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2024-1-6, 18:23:50	Warning (5)	MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:23:13	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:09:38	Warning (5)	MDD message timeout;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:09:25	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:09:24	Error (4)	Primary address failed, secondary active;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:09:24	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:01:06	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:47	Notice (6)	Honoring MDD; IP provisioning mode = APM
1970-1-1, 00:00:44	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41	Notice (6)	WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41	Notice (6)	WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:39	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-6, 18:07:03	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-6, 18:02:08	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
2024-1-6, 18:01:40	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:01:08	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:45	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:38	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:04	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-6, 17:45:22	Critical (3)	Resetting the cable modem due to docsDevResetNow
2024-1-6, 17:08:18	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:01:05	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:43	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-2, 19:07:32	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-2, 17:51:28	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-2, 14:20:24	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2024-1-1, 19:43:30	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2023-12-27, 18:31:57	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2023-12-25, 17:57:45	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
2023-12-24, 23:54:36	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:01:06	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:44	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-12-23, 04:34:49	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:ff:f8:10;CMTS-MAC=00:01:5c:70:64:5f;CM-QOS=1.1;CM-VER=3.0;

FURRYe38
Jan 07, 2024
Ok,

So power levels are too low and all over the place. Power needs to come up and be with in 3db of each channel.

https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-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.

You have a ton of correctables and uncorrectables that should be zero.

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-Modems/m-p/1530376#M12853
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/

Get a on site ISP tech out to review all this and get it working better.

3 Replies

FURRYe38

Guru - Experienced User

Jan 07, 2024

Who is the ISP?

What Firmware version is currently loaded?
Please post a copy and paste of the modems connection status page data.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router

DabbinBallZ

Aspirant

Jan 07, 2024

V1.03.01

ISP is Optimum

ownstream Bonded Channels (Partial Service)

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	17	657000000 Hz	-7.3 dBmV	34 dB	0	0
2	Locked	QAM256	1	561000000 Hz	-7.8 dBmV	33.7 dB	0	0
3	Locked	QAM256	2	567000000 Hz	-6.3 dBmV	35.2 dB	0	0
4	Locked	QAM256	3	573000000 Hz	-5.6 dBmV	35.6 dB	0	0
5	Locked	QAM256	12	627000000 Hz	-2.8 dBmV	37.3 dB	0	0
6	Locked	QAM256	13	633000000 Hz	-3.3 dBmV	37.2 dB	0	0
7	Locked	QAM256	14	639000000 Hz	-4.7 dBmV	35.8 dB	0	0
8	Locked	QAM256	15	645000000 Hz	-6.2 dBmV	35.2 dB	0	0
9	Locked	QAM256	16	651000000 Hz	-7.4 dBmV	34.1 dB	0	0
10	Locked	QAM256	18	663000000 Hz	-6 dBmV	35 dB	0	0
11	Locked	QAM256	19	669000000 Hz	-5.4 dBmV	35 dB	0	0
12	Locked	QAM256	20	675000000 Hz	-9.1 dBmV	31.6 dB	403	0
13	Locked	QAM256	21	681000000 Hz	-13.7 dBmV	27.6 dB	75659269	3221598
14	Not Locked	Unknown	22	687000000 Hz	0.0 dBmV	0.0 dB	0	0
15	Not Locked	Unknown	23	693000000 Hz	0.0 dBmV	0.0 dB	0	0
16	Locked	QAM256	24	699000000 Hz	-13.6 dBmV	27.9 dB	14030911	5437
17	Locked	QAM256	25	705000000 Hz	-11.1 dBmV	30.3 dB	13	0
18	Locked	QAM256	26	711000000 Hz	-11.8 dBmV	29.8 dB	140	0
19	Locked	QAM256	27	717000000 Hz	-12.7 dBmV	29.1 dB	816	0
20	Locked	QAM256	28	723000000 Hz	-11.6 dBmV	30.3 dB	10	0
21	Locked	QAM256	29	729000000 Hz	-12.3 dBmV	29.3 dB	458	0
22	Locked	QAM256	30	735000000 Hz	-14.8 dBmV	27.1 dB	287803	1407
23	Locked	QAM256	31	741000000 Hz	-15.8 dBmV	26.1 dB	50223	189548
24	Not Locked	Unknown	32	747000000 Hz	0.0 dBmV	0.0 dB	0	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	5	5120 Ksym/sec	38000000 Hz	37.8 dBmV
2	Locked	ATDMA	6	5120 Ksym/sec	31600000 Hz	36.8 dBmV
3	Locked	ATDMA	7	5120 Ksym/sec	25000000 Hz	36.3 dBmV
4	Locked	ATDMA	8	2560 Ksym/sec	20200000 Hz	35.5 dBmV
5	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV

FURRYe38
Guru - Experienced User
Jan 07, 2024
Ok,

So power levels are too low and all over the place. Power needs to come up and be with in 3db of each channel.

https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-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.

You have a ton of correctables and uncorrectables that should be zero.

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-Modems/m-p/1530376#M12853
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/

Get a on site ISP tech out to review all this and get it working better.

Forum Discussion

Slow speed on my Nighthawk C7000v2