NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cru26
Jan 17, 2024Aspirant
RAX35v2 - Firmware v1.0.16.132 - Internet Download/Upload Speed by Device stats not refreshing
Since the upgrade to the latest firmware, I'm observing that I'm having issues with the data in the Attached Devices view refreshing properly. It appears to be retaining the max values for Internet D...
Cru26
Jul 31, 2025Aspirant
In this screen cap, the client highlighted in red was downloading a file at over 2 Mbps, however it's not showing that it's downloading anything at all in the router. This used to show me real-time when a device on the network was downloading something large.
FURRYe38
Jul 31, 2025Guru - Experienced User
What is the brand and model# of the ISP modem that the RAX is connected too?
There is newer FW available:
Something to try.
A factory reset may still be needed...
- Cru26Jul 31, 2025Aspirant
Already have that version of firmware running. Why would the ISP modem matter? It's off the WAN interface on my router- I'm looking for download utilization for internal devices.
The factory reset didn't work back when you recommended it the first time in 2024. I was hoping by now they would have fixed this **bleep** with a firmware update or something.
- FURRYe38Jul 31, 2025Guru - Experienced User
ISP Modem could play a part in some of this. Why we ask. Hard to troubleshoot more with out it.
Do you see same speed results with a eithernet connected PC behind the router? Using Ooklas installable speed test app?
Other than this speed UI issue, does the Router work?
That was 2024, maybe need a FR since you updated to check this.
- Cru26Jul 31, 2025Aspirant
I have a wireless ISP, so my WAN interface is connected to directly to their radio- no router. I see similar speed test results no matter what I use. The device that I shared in the screen capture was connected via ethernet.
Router works fine other than this specific UI issue. I tried the FR after you suggested it- it didn't fix the issue then, so why would it fix it now after multiple firmware updates?