Juniper MX and M Series (hardware) End of Life (EOL) Dates & Support Timeline

Juniper MX and M Series (hardware) lifecycle status — the real story

Juniper MX and M Series is the hardware under Junos OS on the routing side: the MX5, MX10, MX40, MX80, MX104, MX150 and MX204 fixed and small modular routers, the MX240, MX480 and MX960 chassis, the MX2008, MX2010 and MX2020 and the MX10003 and MX10016 universal chassis, plus the retired M5, M10, M7i, M10i, M20, M40, M40e, M120, M160 and M320 routers. Cycles on this page are router models, so it is the hardware companion to the Junos OS software page; the exploited Junos CVEs in CISA's KEV catalog are tracked there. Every date comes from Juniper's own M (M, MX) Series Hardware Dates and Milestones page (public, no login, static table; vendor stamp Last updated 16 Sept 2026), re-checked at every build. Juniper publishes the MX dates on the M Series page; the /mx_series/ address returns an error page. The page is SKU-level; each vendor row is mapped to the model it describes and the SKUs are listed in the release column. Line-card (MPC, MIC, DPC, FPC, PIC), routing-engine, optic, cable, power, licence, vMX/vBNG and customer-specific bundle rows are deliberately not modelled.

Field mapping, identical to the Juniper SRX page: support is Juniper's Last Order date; eol is Juniper's End of Support (the last date to receive maintenance support, excluding engineering support). The announcement date and the End of Engineering date (newer rows) or the Same Day Support Discontinued date (older rows) are carried as supportMilestone, with the Technical Support Bulletin number where printed.

The dates that matter now. Juniper announced the MX2010 and MX2020 end of life on August 15, 2026 (base and premium systems last order the same day, End of Engineering January 30, 2032, Junos 27.4 last, End of Support January 30, 2033) and the MX204 hardware on June 15, 2026 (last order June 15, 2027, End of Engineering June 15, 2030, End of Support June 30, 2032; the original MX204 SKUs print June 15, 2032). The MX2008 ends on September 15, 2031 (Junos 23.4 last); the MX10003 and MX10016 on April 3, 2029; the MX150 on June 30, 2028; the MX104 on March 15, 2028. Already past support: MX5, MX10, MX40 and MX80 on June 30, 2026 (the same vendor row retires the first-generation MPC1E to MPC4E line cards, RE-S-1800X4 and SCBE); M7i, M10i, M120 and M320 on December 31, 2022; M40e on January 31, 2016; M20 on December 31, 2012; M160 on July 31, 2011; M5 and M10 on January 31, 2010; M40 on September 30, 2008.

The MX240, MX480 and MX960 chassis are named on the page only through selected bundles (End of Support June 30, 2026) and SKU renamings, with no chassis end-of-life row, so they are listed without dates, which the EOS Edge Device feed reports as no date announced. The MX10008 row lists only fans, switch fabric and power supplies and no base system, so no MX10008 cycle is served; current models absent from the EOL page (MX304, MX10004, MX10008 base) are not listed.

Juniper MX and M Series (hardware) release and support pattern

Of the 25 release lines tracked, 14 are past end of life and 11 are still within support. The next scheduled end of life is MX104 on March 15, 2028 — 520 days from this build. The longest-supported line currently published is MX2020, to January 30, 2033.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Juniper MX and M Series (hardware) end of life mean for your organization?

When a version of Juniper MX and M Series (hardware) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Juniper MX and M Series (hardware) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Juniper MX and M Series (hardware) reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Juniper MX and M Series (hardware) versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products