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

F5 BIG-IP

Active
Security & Networking Latest Version: 21.0.0 Latest Release: Nov 6, 2025

F5 BIG-IP is an application delivery controller providing load balancing, security, and traffic management.

Versions

8

Latest Version

21.0.0

Active Support

4

EOL

4

Lifecycle Timeline

Today
21.0
21.0
17.5
17.5
17.1
17.1
17.0
17.0
16.1
16.1
16.0
16.0
15.1
15.1
15.0
15.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
21.0Nov 6, 2025Aug 6, 2026Aug 6, 202621.0.0No
Active
17.5Feb 27, 2025Jan 1, 2029Jan 1, 202917.5.1
Yes
Active
17.1Mar 14, 2023Mar 31, 2027Mar 31, 202717.1.3
Yes
Active
17.0Apr 26, 2022Jul 31, 2023Jul 31, 202317.0.0No
EOL
16.1Jul 7, 2021Jul 1, 2026Jul 1, 202616.1.6
Yes
Active
16.0Jul 16, 2020Oct 7, 2021Oct 7, 202116.0.1.1No
EOL
15.1Dec 11, 2019Dec 31, 2025Dec 31, 202515.1.10
Yes
EOL
15.0May 23, 2019Aug 23, 2020Aug 23, 202015.0.1No
EOL

Frequently Asked Questions

Which versions of F5 BIG-IP have reached end of life?
The following F5 BIG-IP versions have reached end of life and no longer receive security updates: 17.0, 16.0, 15.1, 15.0. It is recommended to upgrade to a supported version.
Is it safe to continue using F5 BIG-IP 17.0?
F5 BIG-IP 17.0 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 F5 BIG-IP?
The latest version of F5 BIG-IP is 21.0.0, released in the 21.0 release cycle.
How many versions of F5 BIG-IP are currently supported?
F5 BIG-IP currently has 4 actively supported version(s): 21.0, 17.5, 17.1, 16.1.
When does F5 BIG-IP 21.0 reach end of life?
F5 BIG-IP 21.0 is scheduled to reach end of life on Aug 6, 2026.
What should I do when F5 BIG-IP reaches end of life?
When a F5 BIG-IP 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.