Tarantool End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Tarantool versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Tarantool 3.9 is supported, with no end-of-life or end-of-support date announced yet. The next Tarantool version to reach end of life is 3.3, on November 29, 2026. 12 of 20 tracked Tarantool versions are past end of life; the most recent to reach it, 3.2, did so on August 26, 2026. The full Tarantool lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.10 LTS | 1.10.15 | Mar 7, 2018 | May 24, 2023 | 1263 days past EOL | EOL |
| 2.2 | 2.2.3 | Mar 22, 2019 | Apr 20, 2020 | 2392 days past EOL | EOL |
| 2.3 | 2.3.3 | Aug 2, 2019 | Jul 17, 2020 | 2304 days past EOL | EOL |
| 2.4 | 2.4.3 | Jan 10, 2020 | Oct 23, 2020 | 2206 days past EOL | EOL |
| 2.5 | 2.5.3 | Apr 20, 2020 | Dec 30, 2020 | 2138 days past EOL | EOL |
| 2.6 | 2.6.3 | Jul 17, 2020 | Apr 21, 2021 | 2026 days past EOL | EOL |
| 2.7 | 2.7.3 | Oct 23, 2020 | Aug 19, 2021 | 1906 days past EOL | EOL |
| 2.8 | 2.8.4 | Dec 30, 2020 | Apr 25, 2022 | 1657 days past EOL | EOL |
| 2.10 | 2.10.8 | May 22, 2022 | Sep 14, 2023 | 1150 days past EOL | EOL |
| 2.11 LTS | 2.11.10 | May 24, 2023 | May 24, 2027 | 198 days remaining | Active |
| 3.0 | 3.0.2 | Dec 26, 2023 | Apr 16, 2024 | 935 days past EOL | EOL |
| 3.1 | 3.1.2 | Apr 16, 2024 | Aug 26, 2024 | 803 days past EOL | EOL |
| 3.2 | 3.2.4 | Aug 26, 2024 | Aug 26, 2026 | 73 days past EOL | EOL |
| 3.3 | 3.3.5 | Nov 29, 2024 | Nov 29, 2026 | 22 days remaining | Warning |
| 3.4 | 3.4.2 | Apr 14, 2025 | Apr 14, 2027 | 158 days remaining | Warning |
| 3.5 | 3.5.2 | Aug 27, 2025 | TBD | Supported | Active |
| 3.6 | 3.6.4 | Dec 12, 2025 | TBD | Supported | Active |
| 3.7 | 3.7.2 | Apr 22, 2026 | TBD | Supported | Active |
| 3.8 | 3.8.2 | Jul 10, 2026 | TBD | Supported | Active |
| 3.9 | 3.9.0 | Oct 23, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/tarantool)
Tarantool release and support pattern
Across the 20 release lines with a published release date, Tarantool has shipped a new line roughly every 4 months (median interval). A line typically stays supported for about 1.1 years from its release to its end-of-life date (measured on the 15 lines with both dates published). 2 of the 20 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 20 release lines tracked, 12 are past end of life and 8 are still within support. The newest line, 3.9, was released October 23, 2026. The next scheduled end of life is 3.3 on November 29, 2026 — 21 days from this build. The longest-supported line currently published is 2.11, to May 24, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Tarantool end of life mean for your organization?
When a version of Tarantool reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Tarantool should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Tarantool reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Tarantool version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Tarantool has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Tarantool is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."