NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1000 is it the Modem or provider
I have been having a problem for the last week or so that it loses internet connection even though all the modem lights show everything is good. It happens every 2-3 hours and if I power cycle the modem it works again for another 2-3 hours.
When it loses internet I can unplug the ethernet cable going to my router and plug it into my PC directly but it still does not have internet until I power cycle it again.
These are the current readings.
Does this seem like it is the cable provider issue(signal quality or other) or a failing modem?
Thanks
10 Replies
Only seeing 1-16 channels being used.
Which ISP are you with?
What speed plan UP and Down are you paying for?Not seeing any majors in the Event logs sans one Warning.
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.
All channels 1-16 are a bit on the low side. With in specs mostly though power could come up some:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
Be sure your WifI router isn't a problem. Does the wifi router see this issue at the modem? Any LED indications?
Contact the ISP when you see this issue to see if they notice anything on there side.
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
MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:55 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:48 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:48 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:48 Warning (5) MDD message timeout;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:46 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:46 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:38 Warning (5) MDD message timeout;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:37 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:29 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:28 Warning (5) MDD message timeout;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:24 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:24 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:10 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
Time Priority Description
2026-05-30, 19:09:22 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:09:22 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:46 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:46 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:32 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:32 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:11 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:11 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:08:06 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:56 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:56 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:26 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:26 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:09 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:07:06 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:36 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:35 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:33 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:33 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:23 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:23 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:18 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:18 Warning (5) MDD message timeout;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:13 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:03 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:06:03 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-MAC=00:eb:d5:21:e8:78;CM-QOS=1.1;CM-VER=3.1;
2026-05-30, 19:05:56 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 161; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:2c:38;CMTS-
Im still try to paste in the event log with no luck. I will keep trying
Firmware v1.01.03
Ubiquiti UDMPRO
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
317000000
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 165000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv4 only
Downstream Bonded Channels (Partial Service)
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 1 165000000 Hz -6.5 dBmV 40.7 dB 394974424 0 0
2 Locked QAM256 2 171000000 Hz -6.8 dBmV 40.2 dB 394977135 0 0
3 Locked QAM256 3 177000000 Hz -6.3 dBmV 41.0 dB 394980878 0 0
4 Locked QAM256 4 183000000 Hz -6.2 dBmV 40.8 dB 394986655 0 0
5 Locked QAM256 5 189000000 Hz -7.0 dBmV 40.4 dB 394989980 0 0
6 Locked QAM256 6 195000000 Hz -6.2 dBmV 40.9 dB 394992714 0 0
7 Locked QAM256 7 201000000 Hz -6.1 dBmV 40.8 dB 394996503 0 0
8 Locked QAM256 8 207000000 Hz -6.6 dBmV 40.6 dB 395001018 0 0
9 Locked QAM256 9 213000000 Hz -6.0 dBmV 40.8 dB 395004562 0 0
10 Locked QAM256 10 219000000 Hz -6.8 dBmV 40.5 dB 395008052 0 0
11 Locked QAM256 11 225000000 Hz -6.3 dBmV 40.4 dB 395011938 0 0
12 Locked QAM256 12 231000000 Hz -6.4 dBmV 40.5 dB 395015156 0 0
13 Locked QAM256 13 237000000 Hz -6.8 dBmV 40.2 dB 395019199 0 0
14 Locked QAM256 14 243000000 Hz -6.7 dBmV 40.2 dB 395023496 0 0
15 Locked QAM256 15 249000000 Hz -6.9 dBmV 40.5 dB 395023157 0 0
16 Locked QAM256 16 255000000 Hz -7.0 dBmV 40.0 dB 395024402 0 0
17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
Upstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 1 35800000 Hz 53.5 dBmV
2 Not Locked Unknown 0 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV
Downstream OFDM Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0, 3, 5, 6 159 317000000 Hz -8.2 dBmV 37.5 dB 898 ~ 3197 327626907 77824 0
2 Locked 0, 1, 2, 3 161 409000000 Hz -10.3 dBmV 0.0 dB 828 ~ 3267 1340273 19 1340410
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Locked 3, 4, 9, 10, 11, 12, 13 7 6050000 Hz 49.8 dBmV
2 Not Locked 3, 4, 9, 10, 11, 12, 13 0 0 Hz 0.0 dBmV
Current System Time: Sat May 30 19:08:50 2026
System Up Time: 2:25:36
What Firmware version is currently loaded?
Please post a copy and paste of the modems connection status and event log page. Text from the web page is only needed.
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. CAT6 is recommended.
What is the brand and model of the host wifi router connected to the modem?
Yes, the Community Forum has been unable to upload images since the first week of January. If you can copy the information as text, it can be pasted as a "Code Sample".
[url=https://postimg.cc/dLx0ZcSL][img]https://i.postimg.cc/dLx0ZcSL/1.png[/img][/url]
[url=https://postimg.cc/nCPL9fwX][img]https://i.postimg.cc/nCPL9fwX/2.png[/img][/url]
[url=https://postimg.cc/2VK5LNX3][img]https://i.postimg.cc/2VK5LNX3/3.png[/img][/url]
[url=https://postimg.cc/crbJtG5K][img]https://i.postimg.cc/crbJtG5K/4.png[/img][/url]
[url=https://postimg.cc/rKPpR2Yw][img]https://i.postimg.cc/rKPpR2Yw/5.png[/img][/url]
Trying to do as an attachment
Sorry, its not letting me upload the images.
It says uploading images please try again in a few moments
