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

Vitess

Active
Databases Latest Version: 23.0.2 Latest Release: Feb 10, 2026

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

Versions

11

Latest Version

23.0.2

Active Support

2

EOL

9

Lifecycle Timeline

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

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
23Nov 4, 2025-Nov 4, 202623.0.2No
Active
22Apr 29, 2025-Apr 29, 202622.0.3No
Active
21Oct 29, 2024-Oct 29, 202521.0.6No
EOL
20Jun 27, 2024-Jun 27, 202520.0.8No
EOL
19Mar 6, 2024-Mar 6, 202519.0.10No
EOL
18Nov 6, 2023-Nov 7, 202418.0.8No
EOL
17Jun 27, 2023-Jun 27, 202417.0.7No
EOL
16Feb 28, 2023-Feb 28, 202416.0.7No
EOL
15Oct 25, 2022-Oct 25, 202315.0.5No
EOL
14Jun 28, 2022-Jun 28, 202314.0.5No
EOL
13Feb 22, 2022-Feb 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: 21, 20, 19, 18, 17, 16, 15, 14 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Vitess 21?
Vitess 21 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 23.0.2, released in the 23 release cycle.
How many versions of Vitess are currently supported?
Vitess currently has 2 actively supported version(s): 23, 22.
When does Vitess 23 reach end of life?
Vitess 23 is scheduled to reach end of life on Nov 4, 2026.
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.