Meraki End-of-Life: What’s Reached Its Date, What’s Coming, and What Replaces It

If you run Cisco Meraki, three questions matter: which of your gear has already reached its dates, what is coming next, and what each piece replaces with. A large part of the lineup moves through end-of-life in 2025 through 2027, and as of now some of it is already past its End-of-Support date. This guide lays out the timeline with dates and successor paths drawn from the official Cisco Meraki notices. For the wider Cisco planning view and the replace-or-not framework, see the Cisco End-of-Support 2026 hub.

How does Meraki’s end-of-life policy work?

Cisco Meraki runs its own end-of-life policy, separate from the general Cisco lifecycle policy. EOS (End-of-Sale) and EOST (End-of-Support) are the two primary dates shown in Meraki’s consolidated EOL list; individual Cisco/Meraki product bulletins may define additional lifecycle milestones. End-of-Sale is when you can no longer buy the product. End-of-Support is the last date the product is affirmatively supported, and it is typically five years after End-of-Sale, though that is a general guideline rather than a universal rule. Meraki Go (the GX and GR lines) is one notable exception, with a shorter support window.

Because Meraki is cloud-managed, be careful about what “still works” means after End-of-Support. Continued operation, cloud connectivity, firmware and security updates, warranty, and RMA eligibility are not guaranteed after EOST and depend on the applicable product policy and terms. So the honest planning assumption is that support is no longer assured after the End-of-Support date, not that the gear runs indefinitely.

If you want the difference between end of sale, end of support, and the general Cisco milestones explained in full, the End of Sale vs End of Support guide covers it.

What Meraki gear has already passed its End-of-Support date?

As of now, several families are already past End-of-Support. If any of these are still in your network, they should be treated as unsupported and prioritized. All dates are drawn from the canonical Meraki end-of-life page.

FamilyModelsEnd-of-Support (already passed)Migration path
MR access pointsMR33, MR42, MR42E, MR45, MR52, MR53, MR53E, MR74, MR84Jul 21, 2026Cisco Wireless CW91xx (per model)
MX securityMX65-HW, MX65W-HWMay 28, 2026MX67 / MX68 (current base models)
MV camerasMV21-HW, MV71-HWJun 19, 2026MV23M / MV73M (forward path)
Meraki GoGX20-HWJun 20, 2026MX67 (forward path)

The MR group is the one to check first. On July 21, 2026 a large batch of access points reached End-of-Support together, so any MR33, MR42, MR45, MR52, MR53, MR74, or MR84 units still deployed are now past supported life.

What Meraki gear is still ahead of its date?

End-of-Support still ahead:

FamilyModelsEnd-of-SupportSuccessor
MX securityMX84-HWOct 31, 2026MX85
MX securityMX100-HWFeb 1, 2027MX95
MX securityMX64-HW, MX64W-HWJul 26, 2027MX67 / MX68 (current base models)
MR access pointsMR30H-HWJul 26, 2027CW9172H
MR access pointsMR55-HWAug 1, 2027High-density path, see Stratus recommendation below
Meraki GoGX50, GR62, GR12Apr 29, 2027Forward path into MX / MR (see below)
Virtual MXvMX100, EAB-VMX100, E3N-VMX100Dec 22, 2027vMX-M (right-size vMX-S/M/L)

Past End-of-Sale but still supported (plan ahead, no urgency):

FamilyModelsEnd-of-Sale (passed)Supported throughSuccessor
MS switchesMS210, MS225 SeriesApr 30, 2026Apr 30, 2031MS150 series
Systems ManagerCisco Meraki Systems ManagerJun 3, 2026Jun 3, 2029Ivanti Neurons for MDM (via SolutionsPlus)

End-of-Sale still ahead in 2026 (buy-by dates, supported for years after):

FamilyModelsEnd-of-SaleSupported throughSuccessor
MS switchesMS450-12-HWOct 29, 2026Oct 31, 2031C9500-32QC
MT sensorsMT10-HW through MT40-HWNov 10, 2026Nov 30, 2031No designated replacement yet (see note)
MX security (cellular)MX67C, MX68CWNov 27, 2026Nov 30, 2031C8111-C-G2-MX / C8121-CW-G2-MX
MR access pointsMR36, MR36H, MR44, MR46, MR46EDec 31, 2026Dec 31, 2031Cisco Wireless CW9172 / CW9174 / CW9176

Note on the MX branch models: it is the cellular MX67C and MX68CW variants that are reaching end-of-sale. The base non-cellular MX67, MX67W, MX68, and MX68W remain in the current Meraki portfolio with no end-of-sale announcement, which is why they are the migration target for the older MX64 and MX65.

What replaces each retiring product?

Successors fall into three categories, and it is worth being clear which is which.

1. Cisco-designated direct replacements (named in the official notices): MX84 to MX85, MX100 to MX95, MR36/44/46 to the Cisco Wireless CW9172/CW9174/CW9176 line, MS210/MS225 to the MS150 series, MS450-12-HW to the C9500-32QC, the cellular MX67C to C8111-C-G2-MX and MX68CW to C8121-CW-G2-MX, and Systems Manager to Ivanti Neurons for MDM via SolutionsPlus. The older MX64 and MX65 move to the current base MX67 and MX68 models.

2. Forward migration paths, where the originally-designated successor is itself aging. MV21 and MV71 were originally designated to MV22 and MV72, but those Gen2 cameras are now themselves end-of-sale and map forward to MV23M and MV73M, so the current path is MV23M/MV73M. Meraki Go is the other case: the intermediate Go successors are end-of-life, so the current forward path is into the standard MX and MR lines (for example GX50 to MX67, GR62 to MR78, GR12 to MR28).

3. Stratus engineering recommendations. For high-density wireless (the MR53 and MR55 class), our engineering recommendation is the CW9178I, but this is our design guidance, not a Cisco-designated one-for-one swap, and it requires RF, PoE, uplink, and 6 GHz design validation. Treat it as a path to validate, not a drop-in.

On the MT sensor line: there is no designated replacement announced yet. Important context: MT remains supported through its published lifecycle (End-of-Support Nov 30, 2031), so this is a longer-horizon planning note, not an immediate unsupported-state decision. You have runway; you just do not yet have a named successor.

Should you replace, extend, or accept the risk?

Not every unit needs replacing on Meraki’s schedule. Replace when the gear is in your core, carries security or compliance sensitive traffic, or is already past End-of-Support. Extend when a successor is planned but not yet due, which for Meraki mostly means a spares strategy, since support is not assured past EOST. Accept the risk when the gear is isolated, non-critical, or scheduled for decommission. The full framework and how to sequence the spend is on the hub.

A worked example

A retailer with a dozen sites still runs MR52 access points, a pair of MX84 appliances at the core, and a few Meraki Go units at a temporary site. The MR52s are already past End-of-Support as of July 2026, so they are the first priority, migrated onto the CW91xx line with an RF design check for the higher-density stores. The MX84s reach End-of-Support at the end of October 2026, so the MX85 swap is scheduled right behind the access points. The Go units are isolated and the site closes next year, so they confirm the isolation, document it, and accept the risk. Same estate, three different answers, sequenced across budget cycles.

What to do

  1. Inventory your Meraki estate and note each model’s End-of-Support date. That is the date that matters.
  2. Flag anything already past its date first (the July 2026 MR group, MX65, MV21/71, GX20).
  3. Match each retiring model to its successor, and check whether that successor is itself aging.
  4. Add design time for any high-density wireless.
  5. Back-plan the replacements onto your budget cycle.

Not sure which of your Cisco or Meraki gear is reaching its date? Send us your Bill of Materials and request a free quote. Our ex-Cisco team will map your estate against the current dates and lay out the options per platform.

Frequently asked questions

What Meraki products are reaching end of life in 2026? As of now, a batch of older MR access points (MR33, MR42, MR45, MR52, MR53, MR74, MR84) has already reached End-of-Support (July 21, 2026), along with MX65 and MV21/MV71. Still ahead in 2026 are MX84 (End-of-Support Oct 31) and several End-of-Sale dates, including the MS450-12 aggregation switch, the MT sensor line, the cellular MX67C and MX68CW, and the current MR36/44/46 access points. The full list with successor paths is above.

When does Meraki end of support actually happen? End-of-Support (EOST) is the last date a product is affirmatively supported, typically about five years after its End-of-Sale date, with Meraki Go as a shorter-window exception. After the End-of-Support date, continued operation, cloud connectivity, updates, warranty, and RMA are not guaranteed and depend on the applicable policy and terms.

What replaces the Meraki MR access points that are going end of life? The current MR36/44/46 access points have a Cisco-designated path to the Cisco Wireless CW9172/CW9174/CW9176 line. For older high-density models, Stratus’s engineering recommendation is the CW9178I, which needs RF and design validation rather than a straight swap.

Sources

Do you like this article?

Share with friend!

Last Articles:
Most Popular Posts:

Read also

Stratus Information Systems - Cisco Meraki Channel Partner
Request a Free Quote
Whether you are considering moving to a cloud-hosted solution for the first time or just refreshing old gear, Stratus has the knowledge and expertise to set your organization up for a flawless network deployment.
Enter your requirements or upload your Bill of Materials (BoM) below
Thank you!
We are working on your request and we will contact you as soon as possible. Have a nice day!