I'm not too familiar with how routers work and what not. Is this issue on my end or the ISP? How would you fix this issue? Frequency start ValueThis 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 ProcedureProcedureStatusCommentAcquire Downstream Channel693000000 HzLockedConnectivity StateIn progressUpstream Parameters AcquiredBoot StateIn progressUnknownSecurityFailedBPI+IP Provisioning ModeHonor MDDIPv4 only Downstream Bonded ChannelsChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectabables1Locked256 QAM24693000000 Hz8.6 dBmV40.2 dB36290436822Locked256 QAM1555000000 Hz10.2 dBmV40.9 dB003Locked256 QAM2561000000 Hz10.1 dBmV40.6 dB004Locked256 QAM3567000000 Hz10.3 dBmV41.1 dB005Locked256 QAM4573000000 Hz10.3 dBmV41.2 dB006Locked256 QAM5579000000 Hz10.2 dBmV41.1 dB007Locked256 QAM6585000000 Hz10.2 dBmV41.0 dB008Locked256 QAM7591000000 Hz10.3 dBmV41.1 dB009Locked256 QAM8597000000 Hz10.4 dBmV41.1 dB0010Locked256 QAM9603000000 Hz10.4 dBmV40.9 dB0011Locked256 QAM10609000000 Hz10.3 dBmV40.9 dB0012Locked256 QAM11615000000 Hz10.3 dBmV40.8 dB0013Locked256 QAM12621000000 Hz10.3 dBmV40.8 dB0014Locked256 QAM13627000000 Hz10.2 dBmV40.8 dB0015Locked256 QAM14633000000 Hz10.2 dBmV40.8 dB0016Locked256 QAM15639000000 Hz10.2 dBmV40.9 dB0017Locked256 QAM16645000000 Hz10.0 dBmV40.7 dB0018Locked256 QAM17651000000 Hz10.1 dBmV40.6 dB28319Locked256 QAM18657000000 Hz10.1 dBmV40.6 dB0020Locked256 QAM19663000000 Hz10.0 dBmV40.5 dB0021Locked256 QAM20669000000 Hz9.8 dBmV40.5 dB2871122Locked256 QAM21675000000 Hz9.8 dBmV40.2 dB40023Locked256 QAM22681000000 Hz9.5 dBmV40.6 dB14024Locked256 QAM23687000000 Hz9.3 dBmV40.5 dB127591656825Locked256 QAM25699000000 Hz7.9 dBmV40.0 dB114112088826Locked256 QAM26705000000 Hz6.8 dBmV39.6 dB5501410249727Locked256 QAM27711000000 Hz5.4 dBmV39.1 dB504569365728Locked256 QAM28717000000 Hz5.5 dBmV39.2 dB4505015150929Locked256 QAM29723000000 Hz6.7 dBmV39.5 dB5485518769730Locked256 QAM30729000000 Hz7.9 dBmV39.8 dB139294154631Locked256 QAM31735000000 Hz8.6 dBmV39.9 dB731148132Not LockedUnknown00 Hz0.0 dBmV0.0 dB00 Upstream Bonded ChannelsChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower1LockedATDMA15120 Ksym/sec36000000 Hz42.8 dBmV2LockedATDMA25120 Ksym/sec29600000 Hz42.8 dBmV3LockedATDMA35120 Ksym/sec23200000 Hz42.8 dBmV4LockedATDMA45120 Ksym/sec18400000 Hz42.3 dBmV5Not LockedUnknown00 Ksym/sec0 Hz0 dBmV6Not LockedUnknown00 Ksym/sec0 Hz0 dBmV7Not LockedUnknown00 Ksym/sec0 Hz0 dBmV8Not LockedUnknown00 Ksym/sec0 Hz0 dBmV Downstream OFDM ChannelsChannelChannel IDFrequencyPowerSNR/MERActive Subcarrier Number RangeTotal CodewordsUncorrectable Codewords133865000000 Hz11.3 dBmV39.6 dB1108 ~ 298762056738810200 Hz0 dBmV0 dB0 ~ 000 Upstream OFDMA ChannelsChannelUpstreamIsMutedRanging StatusSubcarrier Zero FrequencyActive Subcarrier Number RangeSymbols Per FrameTx Power1 Other0 MHz0 ~ 000 dBmV2 Other0 MHz0 ~ 000 dBmV

What Firmware version is currently loaded? Please post a copy and paste of the modems event log page. 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. Power levels are too hight and all over the place: https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router Correctables and un-correctables should be zeros like the other channels. 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://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/

Forum Discussion

destrosed

Aspirant

Nov 13, 2025

Solved

CAX30 cable connection status: poor

I'm not too familiar with how routers work and what not. Is this issue on my end or the ISP? How would you fix this issue?

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	693000000 Hz	Locked
Connectivity State	In progress	Upstream Parameters Acquired
Boot State	In progress	Unknown
Security	Failed	BPI+
IP Provisioning Mode	Honor MDD	IPv4 only

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectabables
1	Locked	256 QAM	24	693000000 Hz	8.6 dBmV	40.2 dB	36290	43682
2	Locked	256 QAM	1	555000000 Hz	10.2 dBmV	40.9 dB	0	0
3	Locked	256 QAM	2	561000000 Hz	10.1 dBmV	40.6 dB	0	0
4	Locked	256 QAM	3	567000000 Hz	10.3 dBmV	41.1 dB	0	0
5	Locked	256 QAM	4	573000000 Hz	10.3 dBmV	41.2 dB	0	0
6	Locked	256 QAM	5	579000000 Hz	10.2 dBmV	41.1 dB	0	0
7	Locked	256 QAM	6	585000000 Hz	10.2 dBmV	41.0 dB	0	0
8	Locked	256 QAM	7	591000000 Hz	10.3 dBmV	41.1 dB	0	0
9	Locked	256 QAM	8	597000000 Hz	10.4 dBmV	41.1 dB	0	0
10	Locked	256 QAM	9	603000000 Hz	10.4 dBmV	40.9 dB	0	0
11	Locked	256 QAM	10	609000000 Hz	10.3 dBmV	40.9 dB	0	0
12	Locked	256 QAM	11	615000000 Hz	10.3 dBmV	40.8 dB	0	0
13	Locked	256 QAM	12	621000000 Hz	10.3 dBmV	40.8 dB	0	0
14	Locked	256 QAM	13	627000000 Hz	10.2 dBmV	40.8 dB	0	0
15	Locked	256 QAM	14	633000000 Hz	10.2 dBmV	40.8 dB	0	0
16	Locked	256 QAM	15	639000000 Hz	10.2 dBmV	40.9 dB	0	0
17	Locked	256 QAM	16	645000000 Hz	10.0 dBmV	40.7 dB	0	0
18	Locked	256 QAM	17	651000000 Hz	10.1 dBmV	40.6 dB	28	3
19	Locked	256 QAM	18	657000000 Hz	10.1 dBmV	40.6 dB	0	0
20	Locked	256 QAM	19	663000000 Hz	10.0 dBmV	40.5 dB	0	0
21	Locked	256 QAM	20	669000000 Hz	9.8 dBmV	40.5 dB	287	11
22	Locked	256 QAM	21	675000000 Hz	9.8 dBmV	40.2 dB	40	0
23	Locked	256 QAM	22	681000000 Hz	9.5 dBmV	40.6 dB	14	0
24	Locked	256 QAM	23	687000000 Hz	9.3 dBmV	40.5 dB	12759	16568
25	Locked	256 QAM	25	699000000 Hz	7.9 dBmV	40.0 dB	11411	20888
26	Locked	256 QAM	26	705000000 Hz	6.8 dBmV	39.6 dB	55014	102497
27	Locked	256 QAM	27	711000000 Hz	5.4 dBmV	39.1 dB	50456	93657
28	Locked	256 QAM	28	717000000 Hz	5.5 dBmV	39.2 dB	45050	151509
29	Locked	256 QAM	29	723000000 Hz	6.7 dBmV	39.5 dB	54855	187697
30	Locked	256 QAM	30	729000000 Hz	7.9 dBmV	39.8 dB	13929	41546
31	Locked	256 QAM	31	735000000 Hz	8.6 dBmV	39.9 dB	731	1481
32	Not Locked	Unknown	0	0 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	1	5120 Ksym/sec	36000000 Hz	42.8 dBmV
2	Locked	ATDMA	2	5120 Ksym/sec	29600000 Hz	42.8 dBmV
3	Locked	ATDMA	3	5120 Ksym/sec	23200000 Hz	42.8 dBmV
4	Locked	ATDMA	4	5120 Ksym/sec	18400000 Hz	42.3 dBmV
5	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV
6	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV
7	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV
8	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV

Downstream OFDM Channels

Channel	Channel ID	Frequency	Power	SNR/MER	Active Subcarrier Number Range	Total Codewords	Uncorrectable Codewords
1	33	865000000 Hz	11.3 dBmV	39.6 dB	1108 ~ 2987	6205673881	0
2	0	0 Hz	0 dBmV	0 dB	0 ~ 0	0	0

Upstream OFDMA Channels

Channel	UpstreamIsMuted	Ranging Status	Subcarrier Zero Frequency	Active Subcarrier Number Range	Symbols Per Frame	Tx Power
1		Other	0 MHz	0 ~ 0	0	0 dBmV
2		Other	0 MHz	0 ~ 0	0	0 dBmV

not listed

FURRYe38
Nov 13, 2025
What Firmware version is currently loaded?

Please post a copy and paste of the modems event log page.

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.

Power levels are too hight and all over the place:

https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router

Correctables and un-correctables should be zeros like the other channels.

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://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/

3 Replies

destrosed

Aspirant

Nov 13, 2025

Thank you for the response. I'm currently looking at my line and where they went into my house they spliced a RG6 coax cable to another cable and hung it above a rafter in t he basement then pullled it through to reach the upstairs. Not sure if that's anything to do with it but thank you so I do have a place to start.

My Router: CAX30

Firmware Version V2.2.4.2

Event Log

Clear Log Refresh

Time	Priority	Description
2025-11-13 07:47:50	Error (4)	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:52	Warning (5)	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:47	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Error (4)	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:34	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
1970-01-01 00:00:31	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 18:18:41	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:28	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:23	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2025-10-22 19:33:06	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-22 13:20:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-20 12:55:10	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-05 07:54:00	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-04 16:31:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-03 12:53:34	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-03 00:43:33	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-02 15:32:16	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-30 10:55:59	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-23 15:09:44	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-21 20:15:37	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-18 14:20:04	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-17 17:33:34	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-17 12:43:32	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-16 16:47:24	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-15 14:36:31	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;

FURRYe38
Guru - Experienced User
Nov 13, 2025
Ya you got lots of criticals and errors that the ISP needs to look at.

FURRYe38
Guru - Experienced User
Nov 13, 2025
What Firmware version is currently loaded?

Please post a copy and paste of the modems event log page.

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.

Power levels are too hight and all over the place:

https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router

Correctables and un-correctables should be zeros like the other channels.

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://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/