Look up End-of-Sale, Last Date of Support, days remaining, and recommended upgrade path for Cisco UC products — CUCM, Unity Connection, UCCX, Expressway, and IOS-XE. Dates refreshed weekly from Cisco's official notice listings.
Cisco publishes EoS/EoL notices per product family, with dates buried in tables that move when new versions ship. This tracker pulls the current notice listings for CUCM, Unity Connection, UCCX, Expressway, and IOS-XE, normalizes them, and presents the three numbers you actually need: EoS date, LDoS date, and days remaining. Each answer links back to the Cisco source page, so you can verify before forwarding to your CIO or TAC engineer. The underlying JSON is refreshed every Monday; if a source page goes > 90 days without a refresh, the tool flags the staleness. If a version isn't listed, the common cause is that Cisco hasn't published an EoL notice for it yet — those records show as "Supported, no EoS announced" rather than returning an error.
Pick a product and version, click Look up.
Last date Cisco sells the version new. After EoS you can still run the version but can't buy new licenses for it.
Last date Cisco TAC supports it and CVE patches ship. This is the date that matters for risk, compliance, and audits.
Plan an upgrade 6–12 months before LDoS so the final cut happens on a calm week, not a panicked one.
Cisco EoL dates move. Not in the sense that a published LDoS changes — once announced, Cisco doesn't pull it back — but in the sense that you're tracking a moving set of notices across five or more product families, each with its own URL, each with its own column ordering, and each with its own rhythm of announcements. A hospital IT director who built a CUCM refresh plan in 2023 using the dates they knew is now wrong about Unity Connection (which moved), Expressway (which added a 10th version), and IOS-XE (which deprecated an entire branch). The dates they built the plan on are still correct; the set of things they needed to plan for has grown.
The most frequent mistake is treating EoS as the urgent date. It isn't. EoS means no new licenses, which only matters if you're growing the footprint. LDoS is the compliance and security date — once passed, TAC closes any ticket you open, and CVEs stop being patched. HITRUST, SOC 2, and PCI all flag environments past LDoS on Cisco components as a finding, and depending on the assessor, either a deficiency or a material weakness. If your last audit cycle didn't catch a post-LDoS CUCM or Unity, your next one probably will.
The second mistake is assuming Cisco's date is the planning date. It isn't. If LDoS is 12 months out, your plan-the-upgrade date is 18 months out, because a CUCM upgrade from 11.5 to 15 is a 2-3 month effort even in a clean environment — endpoint firmware, licensing migration, SCCP → SIP conversion, and a test cycle. Rushing the final cut against an LDoS deadline is how you end up with a dropped-call incident on a Monday morning.
The third mistake is treating product families as equivalent. CUCM LDoS in 2026 is not the same risk as Unity LDoS in 2026. CUCM controls calling — it's load-bearing. Unity runs voicemail — it's annoying when it breaks but usually not business-stopping. Expressway past LDoS is a perimeter issue (Jabber and MRA users lose reachability). IOS-XE past LDoS is a core-routing issue. Prioritize remediation by business impact, not by calendar proximity.
This tool exists because the alternative is five browser tabs on Cisco.com and a manual spreadsheet. The data is scraped weekly; every answer links back to the source page so you can verify.
A weekly GitHub Actions job scrapes Cisco's official EoS/EoL notice listings into normalized JSON. Each result links back to the Cisco source.
EoS = last date sold. LDoS = last date supported. LDoS is the date that matters.
Every Monday at 02:00 UTC. If source data is > 90 days old, a staleness warning appears.
We track the ~10 most common versions per product. Email us to add niche builds.
Yes — copy/download the result or fetch the raw JSON from /data/cisco/*-eol.json.
Still the most common production CUCM in mid-market healthcare.
Current mainstream production version.
Pre-X14 Expressway still running at the perimeter.
The Network & UC Health Assessment pulls every component's current version and LDoS in one written report — CUCM, Unity, UCCX, Expressway, IOS-XE, UCS — with a sequenced upgrade roadmap.