9 products reach end of support in 2032
27 part numbers across 5 vendors lose manufacturer support during 2032. Every date below is the vendor's own, linked to the bulletin it was read from. The biggest sets: Juniper with 2, Arista with 2, Cisco Meraki with 2.
The largest retirements of 2032
Ranked by tracked part numbers reaching their last date of support this year.
Arista · Data center switch · support ends Feb 2032 · 3 part numbers
details →Cisco Meraki · Access switch · support ends Mar 2032 · 1 part number
details →Everything reaching end of support in 2032, by quarter
Grouped the way budgets are built. A product appears at its earliest 2032 milestone; families where different part numbers carry different dates show every 2032 month.
Q1 · January to March
| Product | Vendor | Category | Support ends | Parts | Vendor-named replacement |
|---|---|---|---|---|---|
| Juniper QFX Series QFX5110 | Juniper | Switch | Jan + Jul 2032 | 13 | none published |
| Arista DCS-7060CX5-56D8 | Arista | Data center switch | Feb 2032 | 3 | none published |
| Arista DCS-7060DX5-32 | Arista | Data center switch | Feb 2032 | 3 | none published |
| Dell Azure Local | Dell | Converged infrastructure | Feb 2032 | 1 | none published |
| Cisco Meraki MS390 Series | Cisco Meraki | Access switch | Mar 2032 | 1 | none published |
Q2 · April to June
| Product | Vendor | Category | Support ends | Parts | Vendor-named replacement |
|---|---|---|---|---|---|
| Cisco Meraki MS390-48UX2-HW | Cisco Meraki | Access switch | Apr 2032 | 1 | none published |
| Juniper M/MX Series MX204 | Juniper | Router | Jun 2032 | 3 | none published |
Q4 · October to December
| Product | Vendor | Category | Support ends | Parts | Vendor-named replacement |
|---|---|---|---|---|---|
| Zyxel MES3500-24S | Zyxel | Service provider access equipment | Dec 2032 | 1 | MGS3520-28 |
| Zyxel MGS3700-12C | Zyxel | Service provider access equipment | Dec 2032 | 1 | MGS3530-16F |
If your hardware is on this list
An end-of-service-life date is a planning fact, not an outage. The equipment keeps working past the date; what stops is vendor support: security patches, software maintenance, replacement hardware and TAC. The realistic paths, in the order most teams weigh them:
Replace on your schedule
Budget the refresh into the right quarter above. Where the vendor has named a successor it is listed in the table and linked, with its own lifecycle page, from each product page.
Third-party maintenance
Independent providers keep hardware running past the vendor date with break/fix, spare parts and on-site SLAs, usually below the last OEM renewal quote. It does not restore firmware or security patches; only the manufacturer ships those. What TPM covers, and what it does not.
Pre-stock spares
Buy spares while units still circulate and self-maintain. Pairs well with TPM for gear where a same-day part matters more than a contract.
Run to failure, documented
A deliberate choice for non-critical, easily replaced, well-segmented gear: record the risk, harden monitoring and backups, retire on your terms.
For internet-facing or compliance-scoped equipment, weigh the unpatched-vulnerability exposure first; after the date, new CVEs in the platform stay unpatched.
Work this list against your own inventory
Paste part numbers or drop a CSV into the bulk checker; it runs in your browser and returns each part's dates and source. Subscribe to the EOSL calendars to get these dates as events, or follow the change ledger for new announcements the week they appear.
2032 end-of-life questions
What hardware goes end of life in 2032?
EOSL.ai tracks 9 product families with 27 part numbers reaching their manufacturer's last date of support in 2032, across 5 vendors. The largest sets are Juniper (2 products), Arista (2 products), Cisco Meraki (2 products). Every date on this page links to the vendor's own end-of-life bulletin.
Does hardware stop working at end of service life?
No. The equipment keeps running. What ends is manufacturer support: security patches, software maintenance, hardware replacement and TAC cases. The risk grows over time rather than arriving on the date, which is why the realistic responses are planning moves rather than emergencies.
What are the options when hardware reaches EOSL?
Replace it on your schedule, keep it running under third-party maintenance (hardware support only; security patches still end), pre-stock spares and self-maintain, or run non-critical gear to failure with the risk documented. The support options guide covers each path and how to choose per box.
Where do these 2032 dates come from?
Every date is read from the manufacturer's own published end-of-life bulletin, and each product row links to that bulletin so you can verify it at the source. Records show when they were last re-checked.