← ← Back to all products
All badges & lifecycle API →
TarantoolEnd of Life (EOL) Dates & Support Status
Active
DatabasesLatest Version: 2.11.10Latest Release: Sep 21, 2026
Tarantool is an in-memory computing platform combining a database and application server.
Support summary
Tarantool 3.3 reaches EOL in 63 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Nov 29, 2026
Tarantool 3.3 · 63 days left
Supported cycles
7
2 lts
Versions
19
Latest Version
2.11.10
Active Support
7
EOL
12
Lifecycle Timeline
May 24, 2023As of Sep 27, 2026
3.8Active · Date not announced
3.7Active · Date not announced
3.6Active · Date not announced
3.5Active · Date not announced
3.4Active · Apr 14, 2027
3.3Active · Nov 29, 2026
3.2EOL · Aug 26, 2026
3.1EOL · Aug 26, 2024
3.0EOL · Apr 16, 2024
2.11Active · May 24, 2027
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 |
|---|---|---|---|---|---|---|
| 3.8 | Jul 10, 2026 | Maintained | Date not announced | 3.8.1 | No | Active |
| 3.7 | Apr 22, 2026 | Maintained | Date not announced | 3.7.1 | No | Active |
| 3.6 | Dec 12, 2025 | Maintained | Date not announced | 3.6.4 | No | Active |
| 3.5 | Aug 27, 2025 | Maintained | Date not announced | 3.5.2 | No | Active |
| 3.4 | Apr 15, 2025 | Maintained | Apr 14, 2027 | 3.4.2 | No | Active |
| 3.3 | Nov 29, 2024 | Maintained | Nov 29, 2026 | 3.3.5 | No | Active |
| 3.2 | Aug 26, 2024 | Ended | Aug 26, 2026 | 3.2.4 | No | EOL |
| 3.1 | Apr 16, 2024 | Ended | Aug 26, 2024 | 3.1.2 | No | EOL |
| 3.0 | Dec 26, 2023 | Ended | Apr 16, 2024 | 3.0.2 | No | EOL |
| 2.11 | May 24, 2023 | Maintained | May 24, 2027 | 2.11.10 | Yes | Active |
| 2.10 | May 22, 2022 | Ended | Sep 14, 2023 | 2.10.8 | No | EOL |
| 2.8 | Dec 30, 2020 | Ended | Apr 25, 2022 | 2.8.4 | No | EOL |
| 2.7 | Oct 23, 2020 | Ended | Aug 19, 2021 | 2.7.3 | No | EOL |
| 2.6 | Jul 17, 2020 | Ended | Apr 21, 2021 | 2.6.3 | No | EOL |
| 2.5 | Apr 20, 2020 | Ended | Dec 30, 2020 | 2.5.3 | No | EOL |
| 2.4 | Jan 10, 2020 | Ended | Oct 23, 2020 | 2.4.3 | No | EOL |
| 2.3 | Aug 2, 2019 | Ended | Jul 17, 2020 | 2.3.3 | No | EOL |
| 2.2 | Mar 22, 2019 | Ended | Apr 20, 2020 | 2.2.3 | No | EOL |
| 1.10 | Mar 7, 2018 | Ended | May 24, 2023 | 1.10.15 | Yes | EOL |
Data sources
Embed this badge
Show Tarantool'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/tarantool/)HTML
<a href="https://eol.wiki/tarantool/"><img src="https://eol.wiki/badge/tarantool.svg" alt="Tarantool end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Tarantool have reached end of life?
The following Tarantool versions have reached end of life and no longer receive security updates: 3.2, 3.1, 3.0, 2.10, 2.8, 2.7, 2.6, 2.5 (and 4 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Tarantool 3.2?
Tarantool 3.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 Tarantool?
The latest version of Tarantool is 2.11.10, released in the 2.11 release cycle.
How many versions of Tarantool are currently supported?
Tarantool currently has 7 actively supported version(s): 3.8, 3.7, 3.6, 3.5, 3.4, 3.3, 2.11.
When does Tarantool 3.8 reach end of life?
Tarantool 3.8 does not have a specific end-of-life date announced yet.
What should I do when Tarantool reaches end of life?
When a Tarantool 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.