RBE971 V12.1.11.15: Intel AX211 client severe latency on main 5 GHz SSID, fine on IoT SSID

If it helps krwagnermitc​ FURRYe38​ I have an AX210 in a Dell laptop. I was having trouble with WiFi, I found there was an updated driver -it's pretty new, version 24.70.0.3 - driver date 7/29/2026. I installed that and it's been humming on 6 GHz ever since. Here's the link to it on the Intel web page if you don't have it - note it specifically says it installs 24.70.0.3 even though the driver file is 24.70.0

https://www.intel.com/content/www/us/en/download/19351/intel-wireless-wi-fi-drivers-for-windows-10-and-windows-11.html 

Thanks. Before the specific answers, one point on the interference theory generally: this system has been in this exact spot, on these channels, with these two satellites, for about 20 months without a problem. Nothing was added, moved, or changed in the room where the router is, or anywhere else in my house, for that matter. Interference doesn't appear overnight on its own, and if it had, it would affect the Linksys I placed in the same spot just as much. What happened overnight on Sept 22–23 was a firmware update, and since then it has steadily worsened on channels 36/40. A radio that worked for 20 months and then degraded over a week, in the same environment, on the same channels the satellites and a different router still use fine, is a radio with a fault.

To your questions:

Linksys test result: different, not the same. That's the key finding. Linksys Wi-Fi 6E router in the exact spot where the RBR sits, RBR and both RBS powered off, same laptop, channel 36: ping avg 5 ms, max 104 ms, 0% loss. The RBR in that spot on channel 36/40: avg 150–1117 ms, up to 16% loss. The location and the channel are fine for a different radio; only the RBR's 5 GHz radio has the problem.

RBR off / RBS off: The Linksys test above was with the whole Orbi system off. I've also tested the reverse: RBR on, both RBS unplugged (backhaul radios idle), channel 36: avg 174 ms, max 920 ms, 4 of 60 lost. Still bad, so it isn't the RBR interfering with itself via the backhaul, and it isn't the satellites.

6 GHz on the AX211: This laptop has never associated on 6 GHz to this system. The 6 GHz BSSIDs show as colocated APs in netsh, and setting the Intel driver's Preferred Band to 6 GHz didn't get it to move; it stays on 5 GHz. My iPhone (5+6 GHz MLO) and Mac (6 GHz) use the RBR's 6 GHz radio at 1,100+ Mbps with no trouble, so that radio is fine. I haven't pursued 6 GHz for the laptop further because it wouldn't change the diagnosis: the 5 GHz radio is the one that's faulty, and a Qualcomm Wi-Fi 5 laptop and a Sony TV, neither of which has 6 GHz, are affected the same way.

Two satellites: Understood on the guidance, and I can revisit that separately. But the fault is present with both satellites unplugged, so the satellite count isn't a factor here.

Everything else is unchanged: factory reset and rollback to 12.1.10.12 didn't help, channel 44 works, channels 36/40 are getting worse, and the satellites' 5 GHz radios are fine on those same channels. If there's a specific test that would help NETGEAR distinguish a calibration or hardware fault in the RBR from anything else, I'm glad to run it. Otherwise I'm hoping the case can get an engineering look rather than the "it works on 44" answer.

Thanks for the reply, and for the testing you're doing with the various adapters.

To your questions:

• Intel driver: 24.70.0.3, dated 7/29/2026, so we're on the same current release. It hasn't changed since before the problem started.
• Factory reset: Yes, full reset on Sept 29. I tested on the default configuration (default SSID, nothing restored) before touching anything: laptop beside the router on the router's 5 GHz radio, channel 40 (Auto's choice), ping avg 329 ms, max 1537 ms, 1 loss out of 60. Same laptop through a satellite in the same session: avg 6 ms. Then I restored the backup; no difference either way.
• Satellites: Two RBS (RBE970), both on other floors and on the opposite side of the house from the router, well over 30 ft away. Both show "Good" backhaul on 5 GHz + 6 GHz. Home is roughly 3,500 sq ft over three levels. The router is on the lowest level, and each satellite is on a separate level.

On the adapter question: I agree the AX2xx cards can be finicky, and that was my first theory too, but the results say it isn't the client here. A second laptop with a Qualcomm QCA61x4A (Wi-Fi 5) gets the same erratic latency on the router's 5 GHz radio (avg 301 ms, max 2140 ms, at 100% signal), and a Sony TV on the router's 5 GHz started buffering the same week. Meanwhile, every one of those clients, including the AX211, is clean through either satellite on the same SSID and channel (avg 5–6 ms, 990 Mbps). The AX211 also runs clean on a Linksys Wi-Fi 6E router placed in the Orbi's exact spot, on channel 36. So, a USB adapter would just be a fourth client showing the same thing; I'm happy to run it if you think it adds something, but three different radios from three vendors already agree.

The pattern is one radio, in one unit, on specific channels: the RBE971's 5 GHz client radio is bad on 36 and 40 and fine on 44, while the satellites' 5 GHz radios are fine on all of them. Manual channel 44 is my workaround right now, and it works well (1,084 Mbps, 3 ms pings). But channel 40 got measurably worse between Sept 23 and Sept 29 (from ~150–430 ms to avg 1117 ms with 16% loss), and it survived both the factory reset and a rollback to 12.1.10.12, so I'm treating 44 as a stopgap rather than a fix.

Support's position so far (case 49892824) is that since 44 works, the radio is fine and it's "channel conditions." The Linksys-in-the-same-spot test is what I'd point to on that; conditions don't discriminate by brand. If you can flag the case for a second look, I'd appreciate it. I'll keep the thread updated with whatever comes back.

What Intel driver version are you using? I'm using current lastest version from them, v.70 something. 

Might try a external USB adapter and check 5Ghz to conpare. 

Has a full on factory reset and setup from scratch been performed? 

How many RBS are deployed? 

What is the size of your home? Sq Ft?

What is the distance between the router 📡 and satellite(s)🛰️? 30 feet or more is recommended in between RBR 📡 and RBS 🛰️ to begin with depending upon building materials when wired or wirelessly connected.

I don't have a AX211, however do have a AX210 and have been testing that adapter on a few different Orbi BE systems. Currently testing a 770v1 series. 

Last testing on the 970 series was fairly good. 

Manual channels 1 and 40 here. 

No IoT network enabled.

Saw some ms in teens area here and there however not frequeny and not high pings seen or timeouts. Timeouts are a big concern for wifi devices connected behind the RBS. 

Also testing while connected at the RBS to help check for latency stability with RBS wireless connected. 

However, I have only been testing 6Ghz as testing the top tier frequency support that someone else had posted and had asked about. 

Testing other adapters as well i.e. Intel BE200 and NG A9000. 

Between all adapters i've been testing, AX210 seems to be most problematic with Orbi systems that I've noticed. Intel BE200 in MLO and A9000 at 6Ghz only has been most stable. 

Keep in contact thru the case #

UPDATE (Sept 30): Not a client issue. The RBE971's 5 GHz radio fails on channels 36/40 for every client; satellites and a different router in the same spot are fine. NETGEAR has declined an RMA.

A lot of testing since the original post. The short version: my original theory (WiFi 7 / mixed-security interop with the Intel AX211) was wrong. It turned out the "good" IoT-SSID result in my first post was actually through a satellite, not the router. Once I controlled for which Orbi unit the laptop was connected to, everything lined up differently.

What I found

• Every 5 GHz client on the RBE971 router on channel 36 or 40 is bad: ping to 192.168.1.1 avg 150–430 ms, spikes to 1.7–3.7 s, occasional loss, throughput 5–40 Mbps. This includes my Intel WiFi 6E laptop, a second laptop with a Qualcomm WiFi 5 adapter (avg 301 ms, max 2140 ms, 100% signal), and a Sony TV (buffering that never happened before).
• The same clients on the same SSID through either RBE970 satellite, same channel: avg 5–6 ms, max 14 ms, 0% loss, 990 Mbps.
• The router's 2.4 GHz radio (avg 28 ms) and 6 GHz radio (iPhone/Mac 1,100+ Mbps) are fine. Wired to the router: 1–4 ms.
• SSID and security don't matter: the IoT SSID (WPA2-only) through the router is just as bad.
• Client settings don't matter: 20 MHz width, 802.11ac mode, power saving off, disconnecting the MLO iPhone and Watch, all no change.
• Factory reset of the router; tested on defaults before restoring anything: avg 329 ms, 1 lost. No change.
• Rollback to V12.1.10.12: avg 232–426 ms, max 3.7 s. No change. The router's transmit rate to the client had dropped to 52 Mbps while the client's was 490. Back on 12.1.11.15 now.
• Changing the 5 GHz channel to 44 (suggested by Netgear phone support) immediately returned it to normal. Avg 3–4 ms, max 12 ms, 1,084 Mbps down. Auto picks 40, so Auto reproduces the fault.
• Back to channel 40 with a nearby printer and Arlo base station unplugged: avg 1117 ms, max 3777 ms, 16% loss, worse than the previous week. Back to 44: avg 3 ms.
• Control test: a Linksys WiFi 6E router placed in the RBE971's exact location, Orbi powered off, same laptop on channel 36: avg 5 ms, 0% loss. A scan from that spot shows no other 5 GHz networks on 36–48.

So: one radio in one unit has lost the ability to operate on the lower 5 GHz channels; it survived a factory reset and a firmware rollback; it's getting worse; and identical radios in the satellites, plus a different brand's radio in the same location, are fine on those channels. Channel 44 works today.

NETGEAR's response

Support's position (case 49892824) is that because the router performs normally on channel 44, the radio is "functioning"; the problem is "channel conditions" or "environmental factors that may not always be visible during standard WiFi scans." I should set the 5 GHz channel to Auto. I replied that the Linksys control test rules out the environment, the satellites rule out the channels, and Auto selects 40, the failing channel. Waiting on escalation.

Questions for the community

1. Has anyone seen an RBE971 (or other Orbi) develop a channel-specific 5 GHz fault like this? A corrupted calibration table or internal self-interference from the backhaul/6 GHz radios seem like plausible mechanisms; I'd be interested to know whether either has come up before.
2. Any advice on getting a hardware case escalated past the "it works on another channel, so it's fine" script? The hardware warranty has ~145 days left.

Happy to share the full logs (ping outputs, netsh interface dumps, WLAN report) if useful.