How long does Cisco Meraki support hardware?

Meraki announces End-of-Sale typically about six months before the last order date, and the End-of-Support (EOST) date is typically five years after the End-of-Sale date. After EOST the device is no longer affirmatively supported.

What is the difference between Meraki EOS and EOST?

EOS (End-of-Sale) is the last date you can order the product. EOST (End-of-Support) is the last date Meraki will support it, typically five years after EOS. Since August 2024, Meraki's EOL policy also covers firmware lifecycle explicitly.

Why does Meraki end-of-life matter more than usual?

Meraki hardware is cloud-managed and licence-dependent. When a device reaches End-of-Support it stops receiving updates, and because functionality is tied to the Meraki dashboard and active licensing, an unsupported device becomes both a security risk and an operational dead end. You can't run it disconnected the way you might a legacy switch.

Vendor EOL guides · Cisco Meraki

Cisco Meraki end-of-life: EOS, EOST, and the licence catch

By Nico De Muynck · Updated July 19, 2026

Quick answer

Meraki has a clean, published lifecycle: End-of-Sale (EOS) is announced ~6 months ahead of the last order date, and End-of-Support (EOST) lands typically five years after EOS. The twist: because Meraki is cloud-managed and licence-dependent, an out-of-support device isn't just unpatched, it's an operational dead end you can't run offline.

The two dates that matter

End-of-Sale (EOS): the last date to order the product through Meraki. Announced typically about six months before, on Meraki's EOL page.
End-of-Support (EOST): the last date Meraki affirmatively supports the product, typically five years after EOS. This is the date to plan your refresh around.

Since August 2024, Meraki's EOL policy also explicitly covers firmware lifecycle, so you get clearer signals about when a device's software stops advancing, not just when hardware support ends.

Why Meraki EOL bites harder than most

A legacy unmanaged switch that goes EOL still forwards packets in a closet for years. Meraki is different: every device depends on the Meraki cloud dashboard and an active licence. When a model hits End-of-Support, it stops getting the updates that keep it compatible and secure, and because you can't manage it outside the dashboard, there's no “just run it a bit longer, disconnected” escape hatch. EOST for Meraki is closer to a hard stop than a soft one, which makes tracking the date early non-negotiable. (The stakes, in full: the five EOL risks.)

Don't forget the licence clock

Meraki has two clocks running: the hardware EOST date and your licence renewal date. A device can be perfectly supported but go dark simply because its licence lapsed, and a device approaching EOST isn't worth a fresh multi-year licence. Track both together so you don't renew a licence on hardware you're about to retire, or let a licence lapse on hardware you're keeping.

How to find your dates

1. The Meraki EOL list. Cisco Meraki maintains an official End-of-Life products and dates page with EOS and EOST dates per model.

2. The dashboard. Your Meraki dashboard shows the models you actually run and their licence status, cross-reference against the EOL list.

3. Record EOST + licence renewal per device and watch both, so a refresh is planned well before either clock runs out.

Track EOST and licence dates in one place.

Record your Meraki End-of-Support and renewal dates in EOL Tracking and get warned months before either runs out.

Start free, up to 5 assets

No credit card · CSV import for whole fleets