NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 performance degradation after 2.5.0.38 firmware update
Hi everyone, Updating my Orbi RBR50 router and RBS50 satellites to the latest firmware release package (2.5.0.38) seems to have resulted in a significant deterioration of my network's performance...
So... after reverting my RBR50 and RBS50s to firmware 2.3.5.30, which Netgear considers the last stable release, the network slowdown that came out of nowhere is gone. However, this doesn't cure the random spikes in latency that were driving me absolutely spare. After receiving no meaningful assistance from Netgear's dev team, I've opted to just broom my Orbi setup and replaced it with a more reliable mesh system from another manufacturer. Specifically, the Asus ROG Rapture GT-AX11000 WiFi 6 triple-band system. It's proving to be much more stable than the Orbi was and thus far has offered slightly better performance, though it's about 1 1/2 times the size and looks like a futuristic take on Stonehenge.
Your best bet is to revert your firmware to an earlier version. If you do a search you'll fine that 2.5.0.38 has been beat to death with folks posting the same issue as you.
Anothe tip: STOP performing manual firmware updates.
Retired_Member wrote:Your best bet is to revert your firmware to an earlier version. If you do a search you'll fine that 2.5.0.38 has been beat to death with folks posting the same issue as you.
I did actually read a number of threads on the subject, though I didn't find any where the poster delved into the actual symptoms in much greater detail than "my network's slow now" so I couldn't be sure it was exactly the same issue. (Do the support people actually read the support community at all, or is this just a venue for commisserating over the apparent incompetence of Netgear's dev team?)
WRT reverting, is it actually possible to revert firmware and have it stay reverted now?
Last time Netgear released a firmware build this disgracefully broken, the only way to stop the Orbi from automatically reinstalling the bad firmware after a reversion was to telnet into the system configuration using ExtraPuTTY and manually turn off the update bit to protect the system from the update for a day or so at most. That was just more stress than it was worth.
For now, I've worked around the problem by shifting speed-sensitive tasks to a node upstream of the Orbi.