EOL.Wiki EOL.Wiki
← ← Back to all products

NetApp ONTAP

Active
Cloud & Platforms Latest Version: 9.16.1 Latest Release: N/A

NetApp ONTAP is a data management software for unified storage across flash, disk, and cloud.

Versions

8

Latest Version

N/A

Active Support

5

EOL

3

Lifecycle Timeline

Today
9.16.1
9.16.1
9.15.1
9.15.1
9.14.1
9.14.1
9.13.1
9.13.1
9.12.1
9.12.1
9.11.1
9.11.1
9.10.1
9.10.1
9.9.1
9.9.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
9.16.1Jan 1, 2025-Jan 31, 2028-No
Active
9.15.1May 1, 2024-Jul 31, 2027-No
Active
9.14.1Jan 1, 2024-Jan 31, 2027-No
Active
9.13.1Jun 1, 2023-Jun 30, 2026-No
Active
9.12.1Feb 1, 2023-Feb 28, 2026-No
Active
9.11.1Jul 1, 2022-Jul 31, 2025-No
EOL
9.10.1Jan 1, 2022-Jan 31, 2025-No
EOL
9.9.1Jun 1, 2021-Jun 30, 2024-No
EOL

Frequently Asked Questions

Which versions of NetApp ONTAP have reached end of life?
The following NetApp ONTAP versions have reached end of life and no longer receive security updates: 9.11.1, 9.10.1, 9.9.1. It is recommended to upgrade to a supported version.
Is it safe to continue using NetApp ONTAP 9.11.1?
NetApp ONTAP 9.11.1 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of NetApp ONTAP?
The latest version of NetApp ONTAP is 9.16.1, released in the 9.16.1 release cycle.
How many versions of NetApp ONTAP are currently supported?
NetApp ONTAP currently has 5 actively supported version(s): 9.16.1, 9.15.1, 9.14.1, 9.13.1, 9.12.1.
When does NetApp ONTAP 9.16.1 reach end of life?
NetApp ONTAP 9.16.1 is scheduled to reach end of life on Jan 31, 2028.
What should I do when NetApp ONTAP reaches end of life?
When a NetApp ONTAP version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.