NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
NetGear WAX620 devices gets removed from Insight cloud frequently
Every other day, the Insight app pings me with: "The following device has been deleted from your network by (Me/Username)" . I am the sole administrator with access to the account, and I can confirm I am not orchestrating these deletions; I have every intention of keeping my job rather than speeding up my own professional demise. When this occurs, the access points drop from Insight-managed mode into standalone local mode (the power LED switches from blue to green). This is not isolated to a single unit—all 18 of our WAX620 APs experience this simultaneously. Had it been simple brownout or power loss, it should've said "Device Disconnected" but instead, it gets removed entirely from cloud which shouldn't happen automatically. Some Details: Power: All APs are powered via Rack PoE switch connected to a high-capacity inverter backup system, ruling out brownouts or power interruptions. There is also no power issues as all devices work normally on a good day Firmware: All units are updated to the latest firmware (v12.8.0.7). Networking: The issue persists regardless of whether DHCP or static IP addresses are assigned. Is this a known configuration issue, a bug within the Netgear Cloud backend, or something else entirely? Has anyone encountered a similar problem?AX600 missing Port Forwarding setting
I have an AX600 in router mode that has been running for multiple years with the same configuration and I had a port forward rule configured that was working on the initial setup. I am trying to edit the Port Forward rule but I am not seeing the setting/option anywhere in the management portal. I see everything that I normally see but am missing any Security and Firewall settings. What am I missing?WAX210 Firmware 1.1.0.34 Bug – SSID Password Complexity Incorrectly Enforced
Hi everyone — I’m seeing what looks like a firmware regression on the WAX210 after updating to v1.1.0.34, and I want to report it in case others are affected. After updating, the AP now refuses to save any configuration changes (even unrelated ones like just renaming the Access Point). The UI throws this error: SSID1: SSID passphrase length must be between 8 and 63 characters, and contain at least one uppercase letter, one lowercase letter, one number, and one special symbol. This happens even when the SSID password is not edited at all. The AP loads the existing (valid) WPA2/WPA3 passphrase and flags it as invalid due to a complexity requirement that didn’t exist before. This appears to be the AP Login Password complexity policy being mistakenly applied to SSID passphrases, which contradicts the official manual. SSID passwords for WPA2/WPA3 should only require 8–63 characters. Reproduction Steps Update WAX210 to firmware 1.1.0.34 Log into the web interface Make any change (example: AP Name only) Click Apply The SSID password complexity error appears, even though SSID settings were untouched Impact. The AP cannot accept any configuration changes unless the SSID password is replaced with a much more complex passphrase. This forces a complete re-key of all connected devices. Expected Behavior Per the WAX210 User Manual, SSID passphrases should be valid with: 8 to 63 characters No requirements for uppercase/lowercase/digits/symbols Those rules worked correctly in previous firmware versions. Current Workaround Rolling back to firmware 1.1.0.25 or 1.1.0.20 fully resolves the issue. Request Can Netgear please confirm whether this is a regression in 1.1.0.34 and escalate to the firmware engineering team? This issue effectively prevents configuration of the device. I can provide: Screenshots of the error dialog A configuration backup A short video showing the issue Exact hardware revision and serial if needed Thanks in advance.We have several WAX610Y that were added to device groups
We have several WAX610Y that were added to device groups. Everything runs right now on the new insight platform. Some of them were added and other failed and we had to re-add them manually on the insight using the serial number and MAC Address. Since then, we have several devices that constantly loose access to the insight (cloud). We have checked about DHCP exhaustion but did not find any issue on that side. Any thoughts on that issue ?Disable Auto Firmware Update - SXR50/SXS50
I have the SXR50 and 3 SXS50 satellites. The recent firmware update (V4.3.2.200) totally dorked up the routers. I would experience disconnects to wireless and hardwired devices were not picking up IPs correctly. I reverted back to the previous firmware version (V4.3.2.100) and all issues were resolved. However, the option to disable Auto Update for the firmware is greyed out. Any idea why this would be and how to allow me to disable it so I do not run in to this again?SXR30
Hello, Use a Orbi SXR30 with 4 satellites for my home network. Previous to recent Insight update (4.3.4.300) phone app listed all connected devices and allowed blocking access through the app. Now when clicking "connected devices" the app shows "no connected clients available". On the "about" tab of the app, it shows 38 connected clients. Thanks for any assistanceWAX610 cannot be added to Insight - ownership release required
Hello, I have a NETGEAR WAX610 that I cannot add to Insight. Error message: "This device was previously added to a different account." I have already factory reset the device multiple times. Serial number: 6KE10C280023E I understand this device was previously used at another location and I do not have access to the original account. Could you please assist with ownership release so I can use the device with Insight? Thank you.WAX210 iPhone WPA3 Incorrect Password isBSSIDDenylisted 1
Hi I've been using a WAX210 as my home access point for a few months and every few days my iPhone is banned from the network. It won't auto-connect and if I manually connect it fails with "Incorrect password" I enabled iOS Wi-Fi diagnostics and it shows the BSSID has been banned for connections, with isBSSIDDenylisted 1. WAX210 running latest Firmware V1.1.0.34 released 25th July 2025 iPhone 16 Pro running latest iOS 26.3.1 5Ghz network WPA3 password I have also submitted feedback to apple as FB22209711 in case it is their bug. I believe it's either a bug in the WAX210 that is getting it banned by the iPhone or the iPhone's banning logic is too restrictive. Relevant log lines below: 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Network 'agate', isFilteringAJCandidates 0, isSSIDTemporarilyDenylisted 0, isBSSIDDenylisted 1, isTDDenylisted 0 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Not considering problematic Network agate isSSIDTemporarilyDenylisted 0 isBSSIDDenylisted 1 isFilteringAJCandidates 0 isTDDenylisted 0