← ← Back to all products
All badges & lifecycle API →
Azul ZuluEnd of Life (EOL) Dates & Support Status
Active
Runtimes & JDKsLatest Version: 27.28.101Latest Release: Sep 15, 2026
Azul Zulu is a certified, fully compliant OpenJDK build by Azul Systems with enterprise support.
Support summary
Azul Zulu 26 reaches EOL in 3 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Sep 30, 2026
Azul Zulu 26 · 3 days left
Supported cycles
7
7 lts
Versions
22
Latest Version
27.28.101
Active Support
7
EOL
15
Lifecycle Timeline
Mar 12, 2022As of Sep 27, 2026
27Active · Mar 31, 2027
26Active · Sep 30, 2026
25Active · Sep 30, 2033
24EOL · Sep 16, 2025
23EOL · Mar 18, 2025
22EOL · Sep 17, 2024
21Active · Sep 30, 2031
20EOL · Sep 19, 2023
19EOL · Mar 31, 2023
18EOL · Sep 30, 2022
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 27 | Sep 15, 2026 | Maintained | Mar 31, 2027 | 27.28.101 | No | Active |
| 26 | Mar 17, 2026 | Maintained | Sep 30, 2026 | 26.32.203 | No | Active |
| 25 | Sep 16, 2025 | Maintained | Sep 30, 2033 | 25.36.205 | Yes | Active |
| 24 | Mar 18, 2025 | Ended | Sep 16, 2025 | 24.32.13 | No | EOL |
| 23 | Sep 17, 2024 | Ended | Mar 18, 2025 | 23.32.11 | No | EOL |
| 22 | Mar 19, 2024 | Ended | Sep 17, 2024 | 22.32.15 | No | EOL |
| 21 | Sep 19, 2023 | Maintained | Sep 30, 2031 | 21.52.203 | Yes | Active |
| 20 | Mar 21, 2023 | Ended | Sep 19, 2023 | 20.32.11 | No | EOL |
| 19 | Sep 20, 2022 | Ended | Mar 31, 2023 | 19.32.13 | No | EOL |
| 18 | Mar 12, 2022 | Ended | Sep 30, 2022 | 18.32.13 | No | EOL |
| 17 | Sep 15, 2021 | Maintained | Sep 30, 2029 | 17.68.203 | Yes | Active |
| 16 | Mar 16, 2021 | Ended | Sep 30, 2021 | 16.32.15 | No | EOL |
| 15 | Sep 15, 2020 | Ended | Mar 31, 2023 | 15.46.17 | No | EOL |
| 14 | Mar 17, 2020 | Ended | Sep 30, 2020 | 14.29.23 | No | EOL |
| 13 | Sep 17, 2019 | Ended | Mar 31, 2023 | 13.54.17 | No | EOL |
| 12 | Mar 19, 2019 | Ended | Sep 30, 2019 | 12.3.11 | No | EOL |
| 11 | Sep 25, 2018 | Maintained | Jan 31, 2032 | 11.90.205 | Yes | Active |
| 10 | Mar 27, 2018 | Ended | Sep 30, 2018 | 10.3.5 | No | EOL |
| 9 | Sep 21, 2017 | Ended | Mar 31, 2018 | 9.0.7.1 | No | EOL |
| 8 | Apr 8, 2014 | Maintained | Dec 31, 2030 | 8.96.0.205 | Yes | Active |
| 6 | Jan 21, 2014 | Ended | Dec 31, 2018 | N/A | Yes | EOL |
| 7 | Sep 25, 2013 | Ended | Jul 31, 2022 | 7.56 | Yes | EOL |
Data sources
Embed this badge
Show Azul Zulu's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/azul-zulu/)HTML
<a href="https://eol.wiki/azul-zulu/"><img src="https://eol.wiki/badge/azul-zulu.svg" alt="Azul Zulu end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Azul Zulu have reached end of life?
The following Azul Zulu versions have reached end of life and no longer receive security updates: 24, 23, 22, 20, 19, 18, 16, 15 (and 7 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Azul Zulu 24?
Azul Zulu 24 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 Azul Zulu?
The latest version of Azul Zulu is 27.28.101, released in the 27 release cycle.
How many versions of Azul Zulu are currently supported?
Azul Zulu currently has 7 actively supported version(s): 27, 26, 25, 21, 17, 11, 8.
When does Azul Zulu 27 reach end of life?
Azul Zulu 27 is scheduled to reach end of life on Mar 31, 2027.
What should I do when Azul Zulu reaches end of life?
When a Azul Zulu 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.