CockroachDB End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all CockroachDB versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.7 | May 10, 2017 | Nov 10, 2018 | 2829 days past EOL | EOL |
| 1.1 | 1.1.9 | Oct 12, 2017 | Apr 12, 2019 | 2676 days past EOL | EOL |
| 2.0 | 2.0.7 | Apr 4, 2018 | Oct 4, 2019 | 2501 days past EOL | EOL |
| 2.1 | 2.1.11 | Oct 30, 2018 | Apr 30, 2020 | 2292 days past EOL | EOL |
| 19.1 | 19.1.11 | Apr 30, 2019 | Oct 30, 2020 | 2109 days past EOL | EOL |
| 19.2 | 19.2.12 | Nov 12, 2019 | May 12, 2021 | 1915 days past EOL | EOL |
| 20.1 | 20.1.17 | May 12, 2020 | Nov 12, 2021 | 1731 days past EOL | EOL |
| 20.2 | 20.2.19 | Nov 10, 2020 | May 10, 2022 | 1552 days past EOL | EOL |
| 21.1 | 21.1.21 | May 18, 2021 | Nov 18, 2022 | 1360 days past EOL | EOL |
| 21.2 | 21.2.17 | Nov 16, 2021 | May 16, 2023 | 1181 days past EOL | EOL |
| 22.1 | 22.1.22 | May 24, 2022 | Nov 24, 2023 | 989 days past EOL | EOL |
| 22.2 | 22.2.19 | Dec 5, 2022 | Jun 5, 2024 | 795 days past EOL | EOL |
| 23.1 LTS | 23.1.30 | May 15, 2023 | Nov 15, 2024 | 632 days past EOL | EOL |
| 23.2 LTS | 23.2.31 | Feb 5, 2024 | Aug 5, 2025 | 369 days past EOL | EOL |
| 24.1 LTS | 24.1.32 | May 20, 2024 | Nov 20, 2025 | 262 days past EOL | EOL |
| 24.2 | 24.2.10 | Aug 12, 2024 | Feb 12, 2025 | 543 days past EOL | EOL |
| 24.3 | 24.3.34 | Nov 18, 2024 | May 18, 2026 | 83 days past EOL | EOL |
| 25.1 | 25.1.10 | Feb 18, 2025 | TBD | Supported | Active |
| 25.2 | 25.2.22 | May 9, 2025 | Nov 12, 2026 | 95 days remaining | Warning |
| 25.3 | 25.3.7 | Aug 4, 2025 | Feb 4, 2026 | 186 days past EOL | EOL |
| 25.4 | 25.4.14 | Nov 3, 2025 | May 3, 2027 | 267 days remaining | Active |
| 26.1 | 26.1.8 | Feb 2, 2026 | Aug 2, 2026 | 7 days past EOL | EOL |
| 26.2 | 26.2.5 | Apr 27, 2026 | Oct 27, 2027 | 444 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cockroachdb)
What does CockroachDB end of life mean for your organization?
When a version of CockroachDB 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL CockroachDB 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 CockroachDB 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL CockroachDB versions. This is a bridge, not a permanent solution — plan your migration in parallel.
CockroachDB has 19 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for CockroachDB exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.