CockroachDB End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 26.4.0

CockroachDB end of life (EOL) and end of support (EOS) dates: 19 CockroachDB versions have reached EOL, including CockroachDB 26.1 (EOL date: Aug 02, 2026) — no longer receiving security updates or patches. CockroachDB 26.3 reaches its End of Support date on Feb 19, 2027 — plan your upgrade path now. CockroachDB 26.4.0 is the current supported release, with support through Apr 26, 2028 — 5 versions in active support. Also see MariaDB EOSL information for related end-of-life information.

CockroachDB end of life dates timeline — release schedule chart of the 8 most recent CockroachDB versions, mapping active support and security support windows against their EOL dates
CockroachDB end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent CockroachDB releases of 25 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact CockroachDB EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported CockroachDB Releases - Active EOS/EOSL Support (5)

Release Released Assistance Support Maintenance Support Latest LTS
26.4 (3 weeks and 6 days ago) (in 1 year and 5 months) (in 11 months) 26.4.0 (3 weeks and 6 days ago) -
26.2 (LTS) (6 months ago) (in 1 year and 10 months) (in 10 months) 26.2.12 (2 weeks and 5 days ago) LTS
25.4 (LTS) (1 year ago) (in 1 year and 5 months) (in 5 months) 25.4.21 (2 weeks and 5 days ago) LTS
25.2 (LTS) (1 year and 6 months ago) (in 1 year) (in 3 weeks and 4 days) 25.2.29 (1 week and 5 days ago) LTS
24.3 (LTS) (2 years ago) (in 5 months) (6 months ago) 24.3.37 (1 month and 2 days ago) LTS

CockroachDB Releases Nearing End of Life - Support Ending Soon (1)

Important: The following CockroachDB releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Released Assistance Support Maintenance Support Latest LTS
26.3 (3 months ago) (in 2 months) (in 2 months) 26.3.0 (2 months ago) -

CockroachDB End of Life (EOL) Releases - No Longer Supported (19)

Release Released Assistance Support Maintenance Support Latest LTS
26.1 (9 months ago) (3 months ago) (3 months ago) 26.1.8 (4 months ago) -
25.3 (1 year and 3 months ago) (9 months ago) (9 months ago) 25.3.7 (10 months ago) -
25.1 (1 year and 9 months ago) (1 year and 3 months ago) (1 year and 3 months ago) 25.1.10 (1 year and 3 months ago) -
24.2 (2 years and 3 months ago) (1 year and 9 months ago) (1 year and 9 months ago) 24.2.10 (1 year and 9 months ago) -
24.1 (LTS) (2 years and 6 months ago) (1 month and 1 day ago) (1 year and 1 month ago) 24.1.34 (1 month and 2 days ago) LTS
23.2 (LTS) (2 years and 9 months ago) (4 months ago) (1 year and 4 months ago) 23.2.31 (4 months ago) LTS
23.1 (LTS) (3 years and 6 months ago) (1 year ago) (2 years ago) 23.1.30 (2 years ago) LTS
22.2 (3 years and 11 months ago) (2 years and 5 months ago) (2 years and 11 months ago) 22.2.19 (2 years and 8 months ago) -
22.1 (4 years and 5 months ago) (2 years and 11 months ago) (3 years and 5 months ago) 22.1.22 (3 years and 3 months ago) -
21.2 (5 years ago) (3 years and 6 months ago) (4 years ago) 21.2.17 (4 years and 1 month ago) -
21.1 (5 years and 6 months ago) (4 years ago) (4 years and 6 months ago) 21.1.21 (4 years and 3 months ago) -
20.2 (6 years ago) (4 years and 6 months ago) (5 years ago) 20.2.19 (4 years and 9 months ago) -
20.1 (6 years and 6 months ago) (5 years ago) (5 years and 6 months ago) 20.1.17 (5 years and 6 months ago) -
19.2 (7 years ago) (5 years and 6 months ago) (6 years ago) 19.2.12 (5 years and 10 months ago) -
19.1 (7 years and 6 months ago) (6 years ago) (6 years and 6 months ago) 19.1.11 (6 years and 4 months ago) -
2.1 (8 years ago) (6 years and 6 months ago) (7 years ago) 2.1.11 (6 years and 10 months ago) -
2.0 (8 years and 7 months ago) (7 years and 1 month ago) (7 years and 7 months ago) 2.0.7 (7 years and 11 months ago) -
1.1 (9 years and 1 month ago) (7 years and 7 months ago) (8 years and 1 month ago) 1.1.9 (8 years and 1 month ago) -
1.0 (9 years and 6 months ago) (8 years ago) (8 years and 6 months ago) 1.0.7 (8 years and 9 months ago) -

Running an unsupported database is a risk you can avoid. This guide explains CockroachDB end of life for every release, so you can see exactly when Cockroach Labs stops patching your self-hosted distributed SQL cluster and which cockroach version you should be on.

CockroachDB End of Life and Its Support Levels

When a release reaches end-of-life, Cockroach Labs ships no more fixes for it. Before that point, every release moves through two support levels:

  • Maintenance support: the release gets bug and security fixes, so it stays safe and stable in production.
  • Assistance support: the release gets critical security fixes only, which is a holding pattern while you plan your move.

Treat the second tier as a countdown, not a comfortable place to stay. A database cluster that depends on resilience and transactional guarantees should not sit on patches limited to the worst vulnerabilities for long.

Maintenance Window for a Regular Release and an Innovation Release

A new major version arrives once per quarter, and each release cycle alternates between two types. The numbers follow three-component calendar versioning, so a name like 26.2.9 tells you the year, the quarter's release and the patch release.

  • A regular release receives one year of maintenance, then six months of assistance.
  • An innovation release receives six months of maintenance and no assistance tier.

New versions reach cloud clusters about two weeks before binaries are published for downloads, so hosted users always see the database's next release first.

Long-Term Support: How an LTS Release Works

A regular release can be promoted to Long-Term Support(LTS) once it shows steady stability and performance. An LTS release gets one year of maintenance counted from its first LTS patch, followed by one year of assistance. That makes an LTS build the sensible pick for production, because it roughly doubles the time before your next forced move.

CockroachDB EOL Dates for Each Major Version

Use this table to find your EOL date. It lists recent production releases using dates tracked at the time of writing; the latest release is at the top.

VersionReleasedMaintenance support endsAssistance support ends
26.319 Aug 202619 Feb 202719 Feb 2027
26.227 Apr 202623 Sep 202723 Sep 2028
26.12 Feb 20262 Aug 20262 Aug 2026
25.43 Nov 20253 May 20273 May 2028
25.34 Aug 20254 Feb 20264 Feb 2026
25.29 May 202517 Dec 202617 Dec 2027
24.318 Nov 20245 May 20265 May 2027
24.120 May 202421 Oct 202521 Oct 2026

Versions 26.2, 25.4, 25.2, 24.3 and 24.1 are the long-term ones, and 24.1 has now run out of every kind of support. For scripts and dashboards, the tracking site publishes the same data as JSON, an RSS feed and a calendar file, so you can alert on a date automatically.

Legacy Public Kubernetes Operator Deprecation

The newer Kubernetes operator is now generally available for self-hosted production use. Along with it, Cockroach Labs announced the deprecation of the legacy public operator and the StatefulSet-based Helm charts. Both will reach end-of-life after a 12-month maintenance window that begins once version 27.3 ships in summer 2027, which is the end-of-life timeline to plan against.

The reason is practical. A plain StatefulSet does not understand the database, so it cannot decommission a node safely or weigh cluster health during a rollout. The new operator uses database-aware custom resources, supports Helm, GitOps tools and air-gapped setups, and maps locality to node labels for Kubernetes deployment.

Rolling Upgrades and Zero-Downtime Migration Before EOL

You do not need an outage to leave the legacy tooling. The operator's automatic migration controller replaces nodes one at a time, checks cluster health between steps and preserves your disks and certificates. It is zero-downtime by design and supports a full rollback at any phase, so a stalled step never traps you.

The same reconciliation loop performs rolling upgrades and blocks unsafe changes before they start. It also adds multi-region topology, Prometheus metrics for observability and declarative config you can keep next to your Terraform code.

Self-Hosted Core Offering EOL and Licensing

Support dates are not the only retirement that matters. From 18 November 2024, Cockroach Labs retired the free Core edition and moved to a single enterprise build. Versions from 24.3 onward, plus later patches to earlier series, ship under the CockroachDB Software License. This licensing change is free for individual developers but affects companies, so read the terms before you upgrade. Source code stays public on GitHub, and the project documentation lists every install path.

CockroachDB Cloud Deprecation Rules Versus Self-Hosted

CockroachDB Cloud follows its own support policy, separate from the table above. The managed cloud platform patches each cloud cluster for you, so you do not track a self-hosted EOL date, and it adds security and compliance controls for regulated teams. Plan names changed over time (Serverless became Basic, Dedicated became Advanced) and a Standard tier now adds scalability at a lower cost, but every CockroachDB Cloud plan runs the same database engine as your own nodes.

That makes a move to the cloud a practical way out of EOL tracking when your team cannot meet the patch cadence. The PostgreSQL wire protocol and transactional consistency stay the same, and each cloud cluster stays current without a maintenance project on your side.

Planning an Upgrade Ahead of EOL

Work through these steps well before your date arrives:

  1. Run cockroach version on each node and compare it with the table.
  2. Pick a target: the newest LTS build for stability, or the latest release if you want new features.
  3. Test the upgrade on a staging cluster first.
  4. Move legacy operator or chart deployments to the new operator.
  5. Subscribe to the feeds so the next date never surprises you.

Checking Your Supported Release Before Deprecation Hits

A supported release is any version still inside its maintenance or assistance period. If yours is not, upgrade first and tune later. Remember that 26.1 and 25.3 already ended, and 24.1 lost its last tier on 21 October 2026, so clusters on those lines need attention now, unless they already run on CockroachDB Cloud, where the vendor handles upgrades in the cloud for you.

EOL dates of related software products