RBR850 Frequent Disconnects Starting March 9th AM EST

I have been having the same issues with quick signal dropout as well with the RBR850. I noticed I was having audio streaming drop outs with Sonos (ethernet to BOOST to speakers via mesh network), Elder Scrolls Online (PC via ethernet), vairious online games (PS4 via ethernet) and YouTube/Netflix restarts and drop outs (Roku and Android devices via ethernet and also wifi). 

System is Netgear Orbi RBK852 (RBR850/RBS850) and a Netgear CM1200 Modem (my own) with Spectrum ISP.

Steps I took to no avail:

- Rebooted Modem & Orbis (of course)

- Checked stats on modem and Orbi and could not find anything that stood out

- Checked Modem direct and the PC direct worked perfectly with no drop outs

- Checked CTS and RTS values and those were set to 2347 for both as suggested

- Checked Modem in case it was a low signal that for some reason worked direct but didn't work with a router, no issues stood out

- Tried rolling back drivers to 3.9.2 and there was no change in the issue

- Used my protection plan to get a new Orbi System...same issue right out of the box without upgrading firmware. It was 3.9.2 out of the box originally. This means anyone picking up a new Orbi AX6000 will have issues most likely.

- Tried running a ping in CMD (pinged Google for a couple nights in a row) and would get a few drop outs (~10) but less then what I was actually experiencing which was around 4 or 5 an hour
- Tried about a dozen other fixes I have research with none of them working

- Found my old router, connected it up and had no issues

The only thing that has worked so far is the fix I found on here where you roll back the firmware to 3.1.5.23 on the Satellite, then the Router, then factory reset both (I did Satellite first then the Router). Then blocked the update site (remember to click always and then aply) and so far it has stuck and has worked. I honestly think someone at Netgear was quitting made this code to spite the company, because when a system right out of the box has issues with your firmware retroactively, it had to be on purpose. Thanks Netgear, probably not recommending this to anyone now. Also a huge thanks to the individual who figured out this fix!