// LIFECYCLE · CHECKED 27 JULY 2026
Your access points are old. Does it actually matter?
End-of-support dates for RUCKUS and Cisco business access points, taken from the vendors' own published notices — and the part nobody selling hardware tells you: when ageing access points are fine, and what to check before you spend anything.
- ● Vendor sources linked
- ● Dates checked 27 July 2026
- ● Independent — we sell no vendor’s kit
Independent, and dated. 365 Techies is an independent IT firm. We are not an authorised partner, reseller or agent of RUCKUS Networks, Belden, CommScope, Cisco or Cisco Meraki, and we have no access to their support entitlements on your behalf. Every date on this page comes from the vendor’s own published notices, linked in the source column, and was checked on 27 July 2026. Where we could not verify something from a vendor source we say “check with vendor” rather than guess.
/01 — THE SHORT ANSWER
Most access points are retired for the wrong reason
Access points almost never wear out. They are retired because the world around them moves — the phones get newer, the security bar rises, the controller stops being supported — and somewhere along the way someone decides the hardware is “old” and quotes for eighteen new ones.
Sometimes that is right. Often it is not. The tables below are here so you can tell which, using the vendor’s own published dates rather than anyone’s sales pitch — ours included.
The single most useful thing on this page: a RUCKUS R510, a 2016 access point that plenty of people will tell you is obsolete, is supported by the vendor until 31 December 2028. If someone has told you your R510s are out of support today, they are wrong against RUCKUS’s own table.
Dates checked: 27 July 2026. Vendors move these. If you are making a decision on a date below, open the vendor link in the source column and check it yourself — then tell us if it has moved and we will correct this page.
/02 — THE DATES
Every model we could verify
Sorted as the vendors publish them. Note the ordering: some newer models lose support sooner than older ones — the RUCKUS R730 (Wi-Fi 6) ends support before the R510 (Wi-Fi 5) does. Age is not the same as remaining life.
| Model | Generation | End of sale | End of support | Status today | Last supported software | Vendor’s replacement |
|---|---|---|---|---|---|---|
| RUCKUS R310 | 802.11ac Wave 1 (Wi-Fi 5) | 31/03/2021 | 31/03/2026 | Support ended | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R320 |
| RUCKUS R500 | 802.11ac Wave 1 (Wi-Fi 5) | 31/10/2018 | 30/04/2024 | Support ended | SmartZone 5.2.x (AP zone) / ZoneDirector 10.4.x | R510 |
| RUCKUS R600 | Check with vendor | 30/04/2019 | 30/04/2024 | Support ended | SmartZone 5.2.x (AP zone) / ZoneDirector 10.5.x | R610 |
| RUCKUS R510 | 802.11ac Wave 2 (Wi-Fi 5) | 31/01/2022 | 31/12/2028 | Supported | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R550 |
| RUCKUS R610 | 802.11ac Wave 2 (Wi-Fi 5) | 31/01/2022 | 31/12/2027 | Ends in about 17 months | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R650 |
| RUCKUS R710 | 802.11ac Wave 2 (Wi-Fi 5) | 31/01/2022 | 31/12/2028 | Supported | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R750 |
| RUCKUS R720 | 802.11ac Wave 2 (Wi-Fi 5) | 31/01/2022 | 31/12/2027 | Ends in about 17 months | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R750 |
| RUCKUS R320 | 802.11ac Wave 2 (Wi-Fi 5) | 31/01/2022 | 31/12/2028 | Supported | SmartZone 6.1.x (AP zone) / ZoneDirector 10.5.x | R350 |
| RUCKUS R730 | Wi-Fi 6 (802.11ax) | 28/02/2022 | 28/02/2027 | Ends in about 7 months | SmartZone 6.1.0 (AP zone) / ZoneDirector 10.5.x | R850 |
| RUCKUS R550 | Wi-Fi 6 (802.11ax) | — | Not announced | Current product — no end-of-life announced | — | — |
| RUCKUS R650 | Wi-Fi 6 (802.11ax) | — | Not announced | Current product — no end-of-life announced | — | — |
| RUCKUS R750 | Wi-Fi 6 (802.11ax) | — | Not announced | Current product — no end-of-life announced | — | — |
| RUCKUS R850 | Wi-Fi 6 (802.11ax) | — | Not announced | Current product — no end-of-life announced | — | — |
| RUCKUS R670 | Wi-Fi 7 (802.11be), tri-band | — | Not announced | Current product — no end-of-life announced | — | — |
| RUCKUS R770 | Wi-Fi 7 (802.11be), tri-band | — | Not announced | Current product — no end-of-life announced | — | — |
| Cisco Aironet 1700 (AIR-AP1702I) | 802.11ac Wave 1 (Wi-Fi 5) | 30/04/2019 | 30/04/2024 | Support ended | — | — |
| Cisco Aironet 2700 (AIR-AP2702I/E) | 802.11ac Wave 1 (Wi-Fi 5) | 30/04/2019 | 30/04/2024 | Support ended | — | — |
| Cisco Aironet 3700 (AIR-AP3702) | 802.11ac Wave 1 (Wi-Fi 5) | 30/04/2019 | 30/04/2024 | Support ended | — | — |
| Cisco Aironet 1830 (AIR-AP1832I) | 802.11ac Wave 2 (Wi-Fi 5) | Check with vendor | 30/04/2027 | Ends in about 9 months | — | — |
| Cisco Aironet 1850 (AIR-AP1852I/E) | 802.11ac Wave 2 (Wi-Fi 5) | Check with vendor | Check with vendor | Check with vendor | — | — |
Sources: RUCKUS Hardware AP end-of-life table · Cisco end-of-sale and end-of-life bulletins. We link the vendor, never a reseller or an end-of-life aggregator.
Not listed? We only publish what we could verify from a vendor source. This cluster covers RUCKUS and Cisco Aironet, plus Meraki licensing and the Meraki Wi-Fi 5 access points. If you run Aruba, Ubiquiti, TP-Link Omada, Zyxel or EnGenius, we have not yet verified those dates and will not guess at them — ring us and we will look them up with you.
/03 — WHAT THE WORDS MEAN
“End of life” is four different things
This is where most expensive misunderstandings begin. RUCKUS publishes three milestones for access points; Cisco publishes seven. They do not line up, and the one everybody quotes — end of sale — is the one that matters least.
| Vendor | Milestone | What it actually means |
|---|---|---|
| RUCKUS | End of Sale | The last day you can buy it new from the vendor. Says nothing about support. |
| RUCKUS | End of Support | The last day the vendor will help you or issue fixes. This is the date that matters. |
| RUCKUS | Last supported software release | Not a date — a version number. The newest firmware your model will ever run. Once your controller moves past it, that model stops being manageable. |
| Cisco | End of Sale | The last day to order it. |
| Cisco | End of Software Maintenance | No more bug fixes. Security fixes may continue — see the next milestone. |
| Cisco | End of Vulnerability/Security Support | No more security patches. A working access point past this date is a risk decision, not a fault. |
| Cisco | Last Date of Support | The end. No support of any kind, at any price. |
/04 — THE SPECS, AND THE POE COLUMN
What each model does — and what it quietly stops doing
The right-hand columns are the ones worth your time. An access point running on less power than it wants does not fail, complain or show a warning. It reports as perfectly healthy while running with fewer aerials, a dead second network port and, on some models, no USB and no IoT radio. It is the most commonly missed fault in business Wi-Fi, and it costs nothing to check.
| Model | Streams | Headline rate (theoretical) | Ports | PoE for full function | What you lose on 802.3af | WPA3 |
|---|---|---|---|---|---|---|
| RUCKUS R310 | 2x2:2 SU-MIMO (no MU-MIMO listed) | 300 / 867 Mbps | 1 x 1GbE | 802.3af (11W max) | af is its normal mode | No |
| RUCKUS R500 | 2x2:2 SU-MIMO | 300 / 867 Mbps | 2 x 1GbE | 802.3af (10.5W max) | af is its normal mode | No |
| RUCKUS R600 | Check with vendor | Check with vendor | Check with vendor | Check with vendor | Check with vendor | Check with vendor |
| RUCKUS R510 | 2x2:2, SU-MIMO and MU-MIMO | 300 / 867 Mbps | 2 x 1GbE, 1 x USB 2.0 | 802.3af (12.6W max) — no separate 802.3at mode listed | af is its normal mode — this is why R510 estates sit on af-only switches | Yes Listed on the current datasheet; needs later firmware and a controller version that exposes it. |
| RUCKUS R610 | 3x3:3, SU-MIMO and MU-MIMO | 450 / 1300 Mbps | 2 x 1GbE with LACP, 1 x USB | 802.3at (21.87W) | 2.4GHz limited to 2x3 (2-chain TX at 21dBm aggregate); USB port off; one Ethernet port off | Yes Firmware and controller dependent. |
| RUCKUS R710 | 4x4:4 SU-MIMO; 3 streams for MU-MIMO | 600 / 1733 Mbps | 2 x 1GbE with LACP, 1 x USB | 802.3at (peak 25W) | 2.4GHz drops to 2x4 at 19dBm/chain; 2nd Ethernet disabled; USB disabled | Yes On the current (2020) datasheet. The 2019 revision listed no WPA3 - it arrived by firmware. |
| RUCKUS R720 | 4x4:4, SU-MIMO and MU-MIMO | 600 / 1733 Mbps | 1 x 2.5GbE, 1 x 1GbE, 1 x USB | PoH / UPoE (up to 33.5W) for all features | af (12.95W): both radios collapse to 1x4. at (25.5W): full 4x4 but the 2nd Ethernet port and USB are still disabled | Yes On the current (2020) datasheet. The 2019 revision listed no WPA3 - it arrived by firmware. |
| RUCKUS R320 | 2x2:2, SU-MIMO and MU-MIMO | 300 / 867 Mbps | 1 x 1GbE | 802.3af (12.18W max) | af is its normal mode - nothing is disabled | Yes On the current datasheet only. The 2019 revision listed no WPA3, so it arrived by firmware - old firmware will not have it. |
| RUCKUS R730 | 8x8:8 (5GHz) + 4x4:4 (2.4GHz) - 12 streams | 1148 Mbps / 4.8 Gbps | 1 x 1/2.5/5GbE, 1 x 1GbE | PoH / UPoE / DC (31.0W max) | RUCKUS marks 802.3af not recommended. On 802.3at (23.8W) the 5GHz radio runs 4x4 instead of 8x8 and the Zigbee/BLE radio is disabled - so an R730 on an ordinary PoE+ switch silently runs at half its 5GHz streams | Yes Datasheet states WPA3 and Wi-Fi Enhanced Open. |
| RUCKUS R550 | 2x2:2 both bands, SU-MIMO and MU-MIMO | 574 / 1200 Mbps | 2 x 1GbE, 1 x USB | 802.3at (18.71W) | 12.71W limited mode: 2.4GHz 2x2 at 19dBm/chain; 2nd Ethernet, onboard IoT radio and USB all disabled | Yes WPA3-Personal and WPA3-Enterprise both listed on the datasheet. |
| RUCKUS R650 | 4x4:4 (5GHz) + 2x2:2 (2.4GHz) | 574 / 2400 Mbps (2974 combined) | 1 x 2.5GbE, 1 x 1GbE, USB, BLE + Zigbee | 802.3at (21.59W) | 12.25W: 5GHz drops 4x4 to 2x4; 2nd Ethernet, IoT radio and USB disabled | Yes |
| RUCKUS R750 | 4x4:4 both bands | 1148 / 2400 Mbps | 1 x 2.5GbE, 1 x 1GbE, USB, BLE + Zigbee | 802.3at (22.34W) | 12.54W: both radios 2x4; 2nd Ethernet, IoT radio and USB disabled | Yes |
| RUCKUS R850 | 8x8:8 (5GHz) + 4x4:4 (2.4GHz) - 12 streams | 1148 Mbps / 4.8 Gbps | 1 x 1/2.5/5GbE, 1 x 1GbE | 802.3bt-class supply (PoH / UPoE / DC) | On 802.3at the 5GHz radio runs 4x4 instead of 8x8 | Yes |
| RUCKUS R670 | 2x2:2 / 2x2:2 / 2x2:2 tri-band (6 streams), or 2x2:2 + 4x4:4 dual-band | 689 / 5765 / 5765 Mbps (9.34 Gbps combined) | 1 x 1/2.5/5GbE, 1 x 1GbE | Check with vendor | Check with vendor | Check with vendor |
| RUCKUS R770 | 2x2:2 (2.4GHz) / 4x4:4 (5GHz) / 2x2:2 (6GHz) | 689 / 5765 / 5765 Mbps (12.22 Gbps combined) | 1 x 1/2.5/5/10GbE, 1 x 1GbE | Check with vendor | Check with vendor | Check with vendor |
| Cisco Aironet 1700 (AIR-AP1702I) | 3x3:2 | 867 Mbps (80MHz) / 300 Mbps (40MHz) | 2 x 1GbE + console | 802.3af / 802.3at / Cisco Enhanced PoE; 15W draw | — | No |
| Cisco Aironet 2700 (AIR-AP2702I/E) | 3x4:3 | 1.3 Gbps | 2 x 1GbE + console (plus AUX for a downstream device) | 802.3at; 15W draw | Cisco's wording: the access point will dynamically shift from 3x4 to 3x3 | No |
| Cisco Aironet 3700 (AIR-AP3702) | 4x4:3 | 1.3 Gbps | Check with vendor | 802.3at, Enhanced PoE or PWRINJ4 (16.1W for 4x4:3) | Degrades to 3x3:3 | No Inferred from sibling Wave 1 datasheets — the 3700 datasheet has been withdrawn from Cisco's site. |
| Cisco Aironet 1830 (AIR-AP1832I) | 3x3:2, SU-MIMO and MU-MIMO | 867 / 300 Mbps (vendor aggregate: up to 1 Gbps dual-radio) | 1 x 1GbE only, plus console and USB | 802.3af / 802.3at; 15.4W draw | Cisco's wording: if 802.3af PoE is the source of power, the USB port is disabled | Yes Delivered by the controller (AireOS 8.10.x or Catalyst 9800), not by the AP. |
| Cisco Aironet 1850 (AIR-AP1852I/E) | 4x4 MIMO, 4 streams (SU-MIMO); 3 streams (MU-MIMO) | 216.7 Mbps / 1.73 Gbps | 2 x 1GbE (no multi-gig) | 802.3at or Cisco Enhanced PoE (20.9W draw) | 802.3af cannot supply its 20.9W draw | Check with vendor |
Vendor headline figures are theoretical PHY rates. Real throughput per client, on a shared access point, is a fraction of them — Cisco’s own datasheets use the word “theoretical”.
The full PoE trap, explained — including why “just swap the access points” usually understates the job by a switch.
/05 — WHEN NOT TO REPLACE
The advice nobody selling hardware will give you
If your estate is patched, powered properly, and managed by a controller that is itself still supported, and your complaint is one dead spot in one room — replacement is not your answer. A channel plan, a power fix or moving one access point probably is.
An ageing estate that misbehaves in 2026 is usually a capability and lifecycle conversation, not an out-of-support emergency. Those are different problems with very different price tags, and it is worth knowing which one you have before anyone quotes.
It works and it's patched
Then you have a capability question, not a fault. Ask what you actually need that it cannot do — and if the answer is nothing, do nothing.
It works but can't be patched
That is a risk decision somebody in the business has to take knowingly. Here is how to weigh it. The same decision arrives when a firewall licence expires.
The controller is out of support
This is usually the real deadline, and it is not the access points. Why the controller decides.
It's fine at 9am and awful at 2pm
That is capacity, not age. A 2x2 access point rated ‘up to 100 clients’ and thirty modern devices is an airtime problem, not a broken one.
/06 — BEFORE YOU RING ANYONE
Eight checks you can run yourself
Ordered cheapest and most diagnostic first. Write the answers down — whoever ends up doing the work, this list will save you money.
| Software | Fixed build | Notes |
|---|---|---|
| RUCKUS Unleashed | 200.15.6.212.27 | Wi-Fi 5 branch — fixes CVE-2025-46120 |
| RUCKUS Unleashed | 200.18.7.1.323 | Current branch — fixes CVE-2025-46120 |
| RUCKUS ZoneDirector | 10.5.1.0.282 | Fixes CVE-2025-46120 |
// BEFORE YOU RING ANYONE
Walk the site and write down what people actually get
Our free Wi-Fi signal test runs in a browser, needs no sign-up, and scores every room. Ten minutes with it turns “the Wi-Fi is rubbish upstairs” into numbers — which is the difference between a guess and a diagnosis, whoever ends up doing the work. See also our room-by-room method.
The rest of this guide
Ten deeper pages, each answering one question properly. Start with whichever describes your situation.
RUCKUS end-of-life dates
R310 to R770, checked against the vendor’s own table.
Is my RUCKUS R510 too old?
The honest answer, and it is probably not the one you were told.
Cisco Aironet end-of-life
What “last date of support” actually costs you.
AP won’t join the controller
Check the certificate date before you do anything else.
The PoE trap
Why replacing access points is never just access points.
APs dropping off the controller
A diagnostic order of play, cheapest check first.
Your controller is the real deadline
Not the access points. This is the one most people miss.
When a Meraki licence expires
What actually happens — and what doesn’t.
Working but unpatched
A different problem from broken, and a different decision.
R510 field playbook
Diagnose it properly, and the 802.3af trap that sends an R550 upgrade backwards.
Not sure what you're looking at?
Send us a photo of the label on one access point and the make of your controller. We'll tell you what you've got, what its dates are, and whether it's actually your problem — no charge for the answer.
01202 775566 · help@365techies.co.uk · MON–FRI 9AM–5PM