Netapp Ontap End of Life Dates
other
Developers rely on accurate and timely information to manage their infrastructure, and when it comes to Netapp Ontap, staying on top of end-of-life dates is crucial for maintaining security and support. Netapp Ontap is a robust data management platform created to help organizations efficiently manage their data storage and protection needs, with its origins dating back to the early days of network-attached storage. The product is maintained by Netapp, a leading provider of data management and storage solutions, and developers use it due to its reliability, scalability, and comprehensive feature set.
The end-of-life landscape for Netapp Ontap is complex, with a total of 10 versions, out of which 4 have already reached their end-of-life, leaving 6 active versions currently supported. The most recent version to reach end-of-life was 9.12.1, which ceased to be supported on February 28, 2026. Looking ahead, version 9.13.1 is next in line to expire, with its end-of-life date set for June 30, 2026, giving developers a clear deadline to plan their upgrades. This information is essential for planning and ensuring that systems remain secure and supported.
Given the current security landscape, Netapp Ontap has a spotless record with 0 tracked CVEs, and consequently, 0 critical CVEs. This implies that none of the versions are particularly vulnerable, with no version being more affected than others due to the absence of any known vulnerabilities. As a result, developers do not need to take immediate action regarding security patches for Netapp Ontap. However, they should still prioritize upgrading to a supported version before the next end-of-life date to ensure continuous support and to mitigate any potential future risks that may arise.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 9.19.1 | Jul 1, 2026 | — | Jul 31, 2029 | in 1012d | — | — | Active | |
| 9.18.1 | Feb 4, 2026 | — | Jan 31, 2029 | in 831d | — | — | Active | |
| 9.17.1 | Jan 15, 2026 | — | Sep 30, 2028 | in 708d | — | — | Active | |
| 9.16.1 | Jan 1, 2025 | — | Feb 26, 2028 | in 491d | — | — | Active | |
| 9.15.1 | May 1, 2024 | — | Jul 31, 2027 | in 281d | — | — | Active | |
| 9.14.1 | Jan 1, 2024 | — | Jan 31, 2027 | in 100d | — | — | Active | |
| 9.13.1 | Jun 1, 2023 | — | Jun 30, 2026 | 115d ago | — | — | EOL | |
| 9.12.1 | Feb 1, 2023 | — | Feb 28, 2026 | 237d ago | — | — | EOL | |
| 9.11.1 | Jul 1, 2022 | — | Jul 31, 2025 | 449d ago | — | — | EOL | |
| 9.10.1 | Jan 1, 2022 | — | Jan 31, 2025 | 630d ago | — | — | EOL | |
| 9.9.1 | Jun 1, 2021 | — | Jun 30, 2024 | 845d ago | — | — | EOL | |
| 9.8 | Oct 1, 2020 | — | Dec 31, 2023 | 1027d ago | — | — | EOL | |
| 9.7 | Nov 1, 2019 | — | Jul 31, 2023 | 1180d ago | — | — | EOL | |
| 9.6 | May 1, 2019 | — | Jun 30, 2022 | 1576d ago | — | — | EOL | |
| 9.5 | Nov 1, 2018 | — | Jan 31, 2022 | 1726d ago | — | — | EOL | |
| 9.4 | Jun 28, 2018 | — | Jun 30, 2019 | 2672d ago | — | — | EOL | |
| 9.3 | Jan 11, 2018 | — | Jan 31, 2021 | 2091d ago | — | — | EOL | |
| 9.2 | Jun 29, 2017 | — | Jul 31, 2018 | 3006d ago | — | — | EOL | |
| 9.1 | Jan 12, 2017 | — | Jan 31, 2020 | 2457d ago | — | — | EOL | |
| 9.0 | Sep 1, 2016 | — | Dec 31, 2017 | 3218d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
