EOL.WikiEOL.Wiki
← ← Back to all products

OpenStack

Active
Cloud & PlatformsLatest Version: 2026.1Latest Release: N/A

Support summary

OpenStack currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

3

0 lts

Versions

33

Latest Version

N/A

Active Support

3

EOL

26

Lifecycle Timeline

Oct 6, 2021As of Sep 19, 2026
2026.1Active · Date not announced
2025.2Active · Date not announced
2025.1Active · Date not announced
2024.2EOL · Apr 29, 2026
2024.1Unknown · Unmaintained; EOL not announced
2023.2EOL · Apr 30, 2025
2023.1Unknown · Unmaintained; EOL not announced
ZedUnknown · Unmaintained; EOL not announced
YogaUnknown · Unmaintained; EOL not announced
XenaEOL · Dec 19, 2025
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

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2026.1GazpachoApr 1, 2026MaintainedDate not announced-No
Active
2025.2FlamingoOct 1, 2025MaintainedDate not announced-No
Active
2025.1EpoxyApr 2, 2025MaintainedDate not announced-No
Active
2024.2DalmatianOct 2, 2024EndedApr 29, 2026-No
EOL
2024.1CaracalApr 3, 2024UnmaintainedUnmaintained; EOL not announced-No
Unknown
2023.2BobcatOct 4, 2023EndedApr 30, 2025-No
EOL
2023.1AntelopeMar 22, 2023UnmaintainedUnmaintained; EOL not announced-No
Unknown
ZedOct 5, 2022UnmaintainedUnmaintained; EOL not announced-No
Unknown
YogaMar 30, 2022UnmaintainedUnmaintained; EOL not announced-No
Unknown
XenaOct 6, 2021EndedDec 19, 2025-No
EOL
WallabyApr 14, 2021EndedDec 19, 2025-No
EOL
VictoriaOct 14, 2020EndedDec 19, 2025-No
EOL
UssuriMay 13, 2020EndedFeb 20, 2024-No
EOL
TrainOct 16, 2019EndedFeb 20, 2024-No
EOL
SteinApr 10, 2019EndedJan 4, 2024-No
EOL
RockyAug 30, 2018EndedAug 16, 2023-No
EOL
QueensFeb 28, 2018EndedJan 18, 2023-No
EOL
PikeAug 30, 2017EndedOct 13, 2022-No
EOL
OcataFeb 22, 2017EndedJun 15, 2021-No
EOL
NewtonOct 6, 2016EndedOct 25, 2017-No
EOL
MitakaApr 7, 2016EndedApr 10, 2017-No
EOL
LibertyOct 15, 2015EndedNov 17, 2016-No
EOL
KiloApr 30, 2015EndedMay 2, 2016-No
EOL
JunoOct 16, 2014EndedDec 7, 2015-No
EOL
IcehouseApr 17, 2014EndedJul 2, 2015-No
EOL
HavanaOct 17, 2013EndedSep 30, 2014-No
EOL
GrizzlyApr 4, 2013EndedMar 29, 2014-No
EOL
FolsomSep 27, 2012EndedNov 19, 2013-No
EOL
EssexApr 5, 2012EndedMay 6, 2013-No
EOL
DiabloSep 22, 2011EndedMay 6, 2013-No
EOL
CactusApr 15, 2011EndedEnded; date not announced-No
EOL
BexarFeb 3, 2011EndedEnded; date not announced-No
EOL
AustinOct 21, 2010EndedEnded; date not announced-No
EOL

Data sources

Last verified

Sep 19, 2026

This source tracks release series and support commitments. Unpublished patch versions and release dates are left blank.

Frequently Asked Questions

Which versions of OpenStack have reached end of life?
The following OpenStack versions have reached end of life and no longer receive security updates: 2024.2, 2023.2, Xena, Wallaby, Victoria, Ussuri, Train, Stein (and 18 more). It is recommended to upgrade to a supported version.
Is it safe to continue using OpenStack 2024.2?
OpenStack 2024.2 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 OpenStack?
The latest version of OpenStack is 2026.1, released in the 2026.1 release cycle.
How many versions of OpenStack are currently supported?
OpenStack currently has 3 actively supported version(s): 2026.1, 2025.2, 2025.1.
When does OpenStack 2026.1 reach end of life?
OpenStack 2026.1 does not have a specific end-of-life date announced yet.
What should I do when OpenStack reaches end of life?
When a OpenStack 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.