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

Vitess

Active
Databases Latest Version: 24.0.1 Latest Release: May 7, 2026

Vitess is a database clustering system for horizontal scaling of MySQL through sharding.

Versions

12

Latest Version

24.0.1

Active Support

2

EOL

10

Lifecycle Timeline

Today
24
24
23
23
22
22
21
21
20
20
19
19
18
18
17
17
16
16
15
15
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
24May 7, 2026YesMay 7, 202724.0.1No
Active
23Nov 4, 2025YesNov 4, 202623.0.4No
Active
22Apr 29, 2025NoApr 29, 202622.0.4No
EOL
21Oct 29, 2024NoOct 29, 202521.0.6No
EOL
20Jun 27, 2024NoJun 27, 202520.0.8No
EOL
19Mar 6, 2024NoMar 6, 202519.0.10No
EOL
18Nov 6, 2023NoNov 7, 202418.0.8No
EOL
17Jun 27, 2023NoJun 27, 202417.0.7No
EOL
16Feb 28, 2023NoFeb 28, 202416.0.7No
EOL
15Oct 25, 2022NoOct 25, 202315.0.5No
EOL
14Jun 28, 2022NoJun 28, 202314.0.5No
EOL
13Feb 22, 2022NoFeb 22, 202313.0.3No
EOL

Frequently Asked Questions

Which versions of Vitess have reached end of life?
The following Vitess versions have reached end of life and no longer receive security updates: 22, 21, 20, 19, 18, 17, 16, 15 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Vitess 22?
Vitess 22 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 Vitess?
The latest version of Vitess is 24.0.1, released in the 24 release cycle.
How many versions of Vitess are currently supported?
Vitess currently has 2 actively supported version(s): 24, 23.
When does Vitess 24 reach end of life?
Vitess 24 is scheduled to reach end of life on May 7, 2027.
What should I do when Vitess reaches end of life?
When a Vitess 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.