AC1750 (C6300) suddenly dropping wifi connection on ALL devices

[kiwineedshelp]

Bought this dual model/router in early 2020. It's been working fine ever since. Last weekend, we installed a new Nest camera and ever since then (coincidence?) the wifi signal has been dropping on ALL devices (4 Nest devices, 2 phones, 1 computer).

Modem/router shows all green. Ethernet connection is perfectly fine. Did a reboot then a reset to factory. Changed channels.

Changed the SSID from standard "Netgearxx" to something (example) "XYZ", keeping "XYZ-2G" and "XYZ-5G" parallel names as recommended by Netgear. That seemed to fix the problem for a couple days.

Now everything is dropping again. Changed SSID again and then none of the devices could find the new SSID. Did a factory reset and it's working again so far.

Help! Do I need to upgrade my Internet service? Or what's happening? I don't see any problem on the routerlogin site. Everything is green. Going a little nuts here and about to start a wfh job.

Possibly not helpful, but event log since factory reset (now working) is below. Sorry I don't have one from when it was dropping connection.

[FURRYe38]

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?

as a power off for 1 minute then back ON with the ISP modem been performed?

[kiwineedshelp]

Thanks for your reply. I have powercycled the modem a couple times before and it did not help previously.

Last time, I took the channels off auto and I selected 9 for the 2.4G (because 1, 6, and 11 were heavily used) and 149 for the 5G. I've attached the images below. I live in a townhome so there are a number of competing neighbors, at least 11 - 18.

Currently, it seems the latest fix is holding without any disconnections -- which was yesterday I reset to factory and kept the default network names ("Netgearxx") as well as found a less congested channel.

[kiwineedshelp]

Images seem to not be loading. I've attached a link to the photos here to the wireless channels: https://imgur.com/a/Tw35rpz

Forgot to mention that I tried to run the latency test for Puma 6 jitters while plugged in by ethernet (if I am saying that correctly) and I can't get the graphic to show up. It only shows that there are something like 89 errors. It doesn't show green or red.

[FURRYe38]

I recommend you change to channel 11 since theres only 1 and 48 or 161 since nobody is using that channel. I guess you can use channel 9 however it's not recommended has its not a primary channel. See how it works for you though. 

[kiwineedshelp]

Thank you for the advice. It has now started disconnecting intermittently at the rate of every couple minutes. Here is the event log. I don't know what to make of it. Please advise!

Sep 16 2021 14:47:35	Notice (6)	TLV-11 - unrecognized OID
Sep 16 2021 14:47:34	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 16 2021 14:44:30	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:44:29	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:44:10	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:44:09	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:43:50	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:43:49	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:43:30	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:43:29	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:43:10	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:43:10	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:42:50	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:42:50	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:42:10	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:42:10	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:41:50	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:41:50	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:40:43	Notice (6)	TLV-11 - unrecognized OID
Sep 16 2021 14:40:42	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 16 2021 14:40:03	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:40:03	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:39:43	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:39:43	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:39:23	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:39:23	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:39:03	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:39:03	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 14:37:43	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 14:37:43	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 13:49:40	Notice (6)	TLV-11 - unrecognized OID
Sep 16 2021 13:49:40	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 16 2021 13:49:04	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 13:49:04	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 13:48:44	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 13:48:44	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 13:48:24	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 13:48:24	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Sep 16 2021 13:48:04	Critical (3)	No Ranging Response received - T3 time-out
Sep 16 2021 13:48:04	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC

[FURRYe38]

Ya those are critcical errors that the ISP needs to resolve.

Please post a copy and paste of the modems connection status page.
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. 
Be sure to power OFF the modem for 1 minute them back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Mod...