NetApp ONTAP End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all NetApp ONTAP versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
NetApp ONTAP 9.19.1 is supported until July 31, 2031, its end-of-support date. Active support for NetApp ONTAP 9.19.1 ends on July 31, 2029; after that date the vendor ships no further fixes for this version, and support alone continues until that end-of-life date. The next NetApp ONTAP version to reach end of life is 9.10.1, on January 31, 2027. 10 of 20 tracked NetApp ONTAP versions are past end of life; the most recent to reach it, 9.9.1, did so on June 30, 2026. The full NetApp ONTAP lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9.0 | — | Sep 1, 2016 | Dec 31, 2019 | 2504 days past EOL | EOL |
| 9.1 | — | Jan 12, 2017 | Jan 31, 2022 | 1742 days past EOL | EOL |
| 9.2 | — | Jun 29, 2017 | Jul 31, 2020 | 2291 days past EOL | EOL |
| 9.3 | — | Jan 11, 2018 | Jan 31, 2023 | 1377 days past EOL | EOL |
| 9.4 | — | Jun 28, 2018 | Jun 30, 2021 | 1957 days past EOL | EOL |
| 9.5 | — | Nov 1, 2018 | Jan 31, 2024 | 1012 days past EOL | EOL |
| 9.6 | — | May 1, 2019 | Jun 30, 2024 | 861 days past EOL | EOL |
| 9.7 | — | Nov 1, 2019 | Jul 31, 2025 | 465 days past EOL | EOL |
| 9.8 | — | Oct 1, 2020 | Dec 31, 2025 | 312 days past EOL | EOL |
| 9.9.1 | — | Jun 1, 2021 | Jun 30, 2026 | 131 days past EOL | EOL |
| 9.10.1 | — | Jan 1, 2022 | Jan 31, 2027 | 84 days remaining | Warning |
| 9.11.1 | — | Jul 1, 2022 | Jul 31, 2027 | 265 days remaining | Active |
| 9.12.1 | — | Feb 1, 2023 | Feb 28, 2028 | 477 days remaining | Active |
| 9.13.1 | — | Jun 1, 2023 | Jun 30, 2028 | 600 days remaining | Active |
| 9.14.1 | — | Jan 1, 2024 | Jan 31, 2029 | 815 days remaining | Active |
| 9.15.1 | — | May 1, 2024 | Jul 31, 2029 | 996 days remaining | Active |
| 9.16.1 | — | Jan 1, 2025 | Jan 31, 2030 | 1180 days remaining | Active |
| 9.17.1 | — | Jan 15, 2026 | Sep 30, 2030 | 1422 days remaining | Active |
| 9.18.1 | — | Feb 4, 2026 | Jan 31, 2031 | 1545 days remaining | Active |
| 9.19.1 | — | Jul 1, 2026 | Jul 31, 2031 | 1726 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/netapp-ontap)
NetApp ONTAP lifecycle status — the real story
NetApp gives every ONTAP release three phases. Full Support includes technical support, root cause analysis, security vulnerability evaluation and Service Updates (P-releases). Limited Support keeps technical support and root cause analysis, but NetApp states that Service Updates, including any form of software update, are not provided. Self-Service Support leaves only the documentation online; after it the version is Obsolete.
On this site the end of life date is NetApp's End of Version Support, the end of Limited Support, because that is the last day NetApp supports the release at all. The active support date is the End of Full Support, and it is the date that matters for security: after it no update of any kind ships for that release. End of Self-Service Support, about three years after End of Version Support, is not shown as extended support because it is not a support phase.
Verified against the vendor's lifecycle documentation on October 17, 2026.
NetApp ONTAP release and support pattern
Across the 20 release lines with a published release date, NetApp ONTAP has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 5.1 years from its release to its end-of-life date.
Of the 20 release lines tracked, 10 are past end of life and 10 are still within support. The newest line, 9.19.1, was released July 1, 2026. The next scheduled end of life is 9.10.1 on January 31, 2027 — 83 days from this build. The longest-supported line currently published is 9.19.1, to July 31, 2031.
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 NetApp ONTAP end of life mean for your organization?
When a version of NetApp ONTAP 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 NetApp ONTAP 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 NetApp ONTAP 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.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
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, check whether the vendor or a third party sells extended support with security patches for your NetApp ONTAP version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
NetApp ONTAP has 10 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for NetApp ONTAP is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."