Im having issues with rebooting as well

Ok.

So current UPtime no debug page and show stats same or showing different values? 

You lost me.....what is the question?

Rebooted again...this time its shows all rebooted 12 hours 52 min ago.  9am pst.  so why?  I did get a message from Sepctrum that they would be dong some work in my area about that time.  THey said I could see 15 minutes downtime.  So maybe that what happened this time.  But even if Spectrum went down, you would think that only the WAN would show 12 hours and everything else would be higher right?

Ok I think this maybe an ISP thing or the RBR maybe reacting to something happening on the WAN port. 
I just put a CM3000 series cable modem online today. I did not reboot the RBR I have connected to it. 
I noticed that after the system was fully up and running and ready, I checked the Show stats button the the RBR850 I have connected to the modem and saw the UpTime on the WAN port of 22 minutes:

However looking at the RBRs debug page, the system uptime there hows 3 plus days of up time. Hasn't changed here.

So I don't think the WAN port uptime is not tied to the debug page uptime. The WAN port uptime is actual connection up time between the RBR and ISP modem or ONT. So if the WAN port is changing up time randomly and the debug page isn't, I guess the WAN port is seeing problem coming from the ISP modem/ONT here. Debug page is reporting full system up time which hasn't changed on yours. 

If the ISP is letting you know there doing things, you'll need to keep track on this and keep monitoring the WAN port up time along with debug just to be sure. I guess these will be different values for you. Hoping that the ISP will be correcting what ever is happening on there side and the RBRs WAN port will stop loosing connection with the ISP services. 

Jesse:

I have had issues with Spectrum and their nodes, which has been problematic in my area that would cause disconnection issues.   Have you tried escalating the issue with the provider and seeing if they can determine if there is an issue with the node in the area.   I recently had to call them 3 times in less than a week before my network issues were resolved as a lot of times their techs that send out for service really don't know much about fixing the issues. 

4 reboots since last update.  Here is the latest which just happened.

Please post a screen capture of the RBRs debug page please. 

me: 03/19/2024, 05:53:44 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:02:49
Time: 03/19/2024, 05:58:42 CPU %: 8.93% Memory Usage: 1121 MB/1743 MB Uptime: 3 days 08:07:47
Time: 03/19/2024, 06:03:40 CPU %: 8.93% Memory Usage: 1123 MB/1743 MB Uptime: 3 days 08:12:46
Time: 03/19/2024, 06:08:39 CPU %: 8.93% Memory Usage: 1121 MB/1743 MB Uptime: 3 days 08:17:44
Time: 03/19/2024, 06:13:37 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:22:42
Time: 03/19/2024, 06:18:35 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:27:40
Time: 03/19/2024, 06:23:33 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:32:39
Time: 03/19/2024, 06:28:32 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:37:37
Time: 03/19/2024, 06:33:30 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:42:35
Time: 03/19/2024, 06:38:28 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:47:33
[31760:33092:0319/064257.120:ERROR:device_event_log_impl.cc(236)] [06:42:57.109] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064257.121:ERROR:device_event_log_impl.cc(236)] [06:42:57.110] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064258.585:ERROR:device_event_log_impl.cc(236)] [06:42:58.223] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064258.585:ERROR:device_event_log_impl.cc(236)] [06:42:58.227] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064258.872:ERROR:device_event_log_impl.cc(236)] [06:42:58.577] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064258.879:ERROR:device_event_log_impl.cc(236)] [06:42:58.581] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064326.066:ERROR:device_event_log_impl.cc(236)] [06:43:26.065] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064326.066:ERROR:device_event_log_impl.cc(236)] [06:43:26.065] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
Time: 03/19/2024, 06:43:26 CPU %: 49.40% Memory Usage: 1182 MB/1743 MB Uptime: 0 days 00:01:02
Time: 03/19/2024, 06:48:25 CPU %: 21.93% Memory Usage: 1148 MB/1743 MB Uptime: 0 days 00:06:01
Time: 03/19/2024, 06:53:23 CPU %: 15.25% Memory Usage: 1149 MB/1743 MB Uptime: 0 days 00:10:59
Time: 03/19/2024, 06:58:21 CPU %: 12.65% Memory Usage: 1140 MB/1743 MB Uptime: 0 days 00:15:57
Time: 03/19/2024, 07:03:20 CPU %: 11.60% Memory Usage: 1138 MB/1743 MB Uptime: 0 days 00:20:56
Time: 03/19/2024, 07:08:18 CPU %: 10.86% Memory Usage: 1138 MB/1743 MB Uptime: 0 days 00:25:54
Time: 03/19/2024, 07:13:16 CPU %: 10.25% Memory Usage: 1136 MB/1743 MB Uptime: 0 days 00:30:52
Time: 03/19/2024, 07:18:15 CPU %: 9.81% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:35:50
Time: 03/19/2024, 07:23:13 CPU %: 9.83% Memory Usage: 1136 MB/1743 MB Uptime: 0 days 00:40:49
Time: 03/19/2024, 07:28:11 CPU %: 9.49% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:45:47
Time: 03/19/2024, 07:33:09 CPU %: 9.25% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:50:45
Time: 03/19/2024, 07:38:08 CPU %: 9.22% Memory Usage: 1135 MB/1743 MB Uptime: 0 days 00:55:43
Time: 03/19/2024, 07:43:06 CPU %: 9.03% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 01:00:42
Time: 03/19/2024, 07:48:04 CPU %: 8.89% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 01:05:40

Ok so both WAN and Debug pages were reset. 

Please continue to monitor and observe the CPU Usage and see if you notice any creeping for this value in a upwards direction or if it seems to crest at a certain value. 

New beta firmware installed on RBR and 2 RBS.  Monitoring tools executed for RBR and both RBS. Its been up for 17 hours since I installed the new beta firmware

👍

Reboot about 7:14 pm (pst ).  But weird....the log doesnt show anything about that time.....but only the WAN and LAN went down

Time: 03/21/2024, 06:50:21 CPU %: 17.36% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 00:32:09
Time: 03/21/2024, 06:55:20 CPU %: 16.48% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:37:08
Time: 03/21/2024, 07:00:19 CPU %: 15.80% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 00:42:07
Time: 03/21/2024, 07:05:18 CPU %: 15.19% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:47:05
Time: 03/21/2024, 07:10:17 CPU %: 14.61% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:52:04
Time: 03/21/2024, 07:15:15 CPU %: 14.13% Memory Usage: 1127 MB/1743 MB Uptime: 0 days 00:57:03
Time: 03/21/2024, 07:20:14 CPU %: 13.68% Memory Usage: 1121 MB/1743 MB Uptime: 0 days 01:02:01
Time: 03/21/2024, 07:25:12 CPU %: 13.28% Memory Usage: 1120 MB/1743 MB Uptime: 0 days 01:06:59
Time: 03/21/2024, 07:30:10 CPU %: 12.97% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:11:58
Time: 03/21/2024, 07:35:09 CPU %: 12.66% Memory Usage: 1122 MB/1743 MB Uptime: 0 days 01:16:56
Time: 03/21/2024, 07:40:07 CPU %: 12.38% Memory Usage: 1124 MB/1743 MB Uptime: 0 days 01:21:54
Time: 03/21/2024, 07:45:05 CPU %: 12.11% Memory Usage: 1118 MB/1743 MB Uptime: 0 days 01:26:52
Time: 03/21/2024, 07:50:03 CPU %: 11.95% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:31:51
Time: 03/21/2024, 07:55:02 CPU %: 11.79% Memory Usage: 1119 MB/1743 MB Uptime: 0 days 01:36:49
Time: 03/21/2024, 08:00:00 CPU %: 11.65% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:41:47
Time: 03/21/2024, 08:04:58 CPU %: 11.55% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:46:46
Time: 03/21/2024, 08:09:57 CPU %: 11.39% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:51:44
Time: 03/21/2024, 08:14:55 CPU %: 11.28% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:56:42
Time: 03/21/2024, 08:19:53 CPU %: 11.18% Memory Usage: 1124 MB/1743 MB Uptime: 0 days 02:01:40
Time: 03/21/2024, 08:24:52 CPU %: 11.08% Memory Usage: 1123 MB/1743 MB Uptime: 0 days 02:06:39
Time: 03/21/2024, 08:29:50 CPU %: 10.98% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 02:11:37
Time: 03/21/2024, 08:34:48 CPU %: 10.88% Memory Usage: 1119 MB/1743 MB Uptime: 0 days 02:16:35
Time: 03/21/2024, 08:39:47 CPU %: 10.82% Memory Usage: 1122 MB/1743 MB Uptime: 0 days 02:21:34
Time: 03/21/2024, 08:44:45 CPU %: 10.74% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 02:26:32
Time: 03/21/2024, 08:49:43 CPU %: 10.68% Memory Usage: 1123 MB/1743 MB Uptime: 0 days 02:31:30
Time: 03/21/2024, 08:54:42 CPU %: 10.62% Memory Usage: 1121 MB/1743 MB Uptime: 0 days 02:36:29

I recommend opening up a support ticket with NG support and lets start giving them more information and ask about RMA options. Only thing I can think of is that this RBR maybe faulty and no mater FW version, needs to be replaced. 

Agreed.  Now what would be the best way to do this as I know Fernando, one of the engineers at Netgear, is watchng this thread and is that has been helping me during this time including giving me all the beta firmwares.

FYI RBR just rebooted again

RBR Log

Time: 03/22/2024, 06:17:28 CPU %: 8.57% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:02:20
Time: 03/22/2024, 06:22:26 CPU %: 8.50% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:07:18
Time: 03/22/2024, 06:27:25 CPU %: 8.52% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:12:17
Time: 03/22/2024, 06:32:23 CPU %: 8.45% Memory Usage: 1133 MB/1743 MB Uptime: 0 days 01:17:15
Time: 03/22/2024, 06:37:21 CPU %: 8.40% Memory Usage: 1132 MB/1743 MB Uptime: 0 days 01:22:13
Time: 03/22/2024, 06:42:19 CPU %: 8.39% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 01:27:12
Time: 03/22/2024, 06:47:18 CPU %: 8.37% Memory Usage: 1129 MB/1743 MB Uptime: 0 days 01:32:10
Time: 03/22/2024, 06:52:16 CPU %: 8.31% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:37:08
Time: 03/22/2024, 06:57:14 CPU %: 8.29% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:42:06
Time: 03/22/2024, 07:02:13 CPU %: 8.33% Memory Usage: 1128 MB/1743 MB Uptime: 0 days 01:47:05
Time: 03/22/2024, 07:07:11 CPU %: 8.28% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:52:03
Time: 03/22/2024, 07:12:09 CPU %: 8.26% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 01:57:01
Time: 03/22/2024, 07:17:08 CPU %: 8.25% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 02:02:00
Time: 03/22/2024, 07:22:06 CPU %: 8.27% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 02:06:58
Time: 03/22/2024, 07:27:04 CPU %: 8.26% Memory Usage: 1128 MB/1743 MB Uptime: 0 days 02:11:56
Time: 03/22/2024, 07:32:02 0 0 0 Call to debug page timed out/did not fully populate

Ya I sent him this as well. 

Just to confirm you had done a full on factory reset and setup from scratch with the beta FW? 

I'd at least get a ticket open and get something started. I just had someone PM me from Feb and said was having bad issues with there 970 series, got an RMA and they are good now. So I'm wondering if yours maybe faulty out of the box like there's was. I told the user to ask about a cross shipping RMA where NG could send you a RMA unit while you hold on to the original unit, gives you some time to test out the new RMA unit. If all is good and the RMA works, then you have to send the original unit back to NG. 

I think this would be worth getting that started while you and Straq continue on this original unit. 

Ive done a reset a few times....but not with this most recent beta firmware

That would be one last try I guess. Full on FR. If it still continues to reboot, let NG and Straq know. 

I will attempt to do this before I leave out of town.  Ill be away for about 2 week.

👍

Any progress on this? 

---

JesseDiaz wrote:

I will attempt to do this before I leave out of town.  Ill be away for about 2 week.

---

They sent me a new router....but still old issues.  Its still rebooting.....at least based on the logs.  Stability is a little worse too.  Running the newrouterstat and newsatstats debug tools again

Have you been updating the support ticket on this? 

What FW version is on the newer RBR? 

I have...every move.  I have the latest 9.11.1.1. or something like that.  They wanted be on non-beta firmware

Ok, only other idea would be to put a Fan under or on top of the RBR. I see that a couple of other users posted about seeing connection issues at the RBR and after putting a fan on top, seemed to have stopped that. Have sent this to NG as well.