← ← Back to all products
All badges & lifecycle API →
Couchbase ServerEnd of Life (EOL) Dates & Support Status
Active
DatabasesLatest Version: 8.0.3Latest Release: Sep 1, 2026
Couchbase Server is a distributed NoSQL cloud database with memory-first architecture for enterprise applications.
Support summary
Couchbase Server currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Mar 31, 2027
Couchbase Server 7.6 · 185 days left
Supported cycles
2
0 lts
Versions
22
Latest Version
8.0.3
Active Support
2
EOL
20
Lifecycle Timeline
Feb 28, 2018As of Sep 27, 2026
8.0Active · Oct 31, 2028
7.6Active · Mar 31, 2027
7.2EOL · Jul 31, 2026
7.1EOL · Jan 31, 2024
7.0EOL · Jan 31, 2023
6.6EOL · Jan 31, 2023
6.5EOL · Feb 28, 2021
6.0EOL · Jul 31, 2020
5.5EOL · Jul 31, 2020
5.1EOL · Jan 31, 2019
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 |
|---|---|---|---|---|---|---|
| 8.0 | Oct 21, 2025 | Maintained | Oct 31, 2028 | 8.0.3 | No | Active |
| 7.6 | Mar 25, 2024 | Maintained | Mar 31, 2027 | 7.6.12 | No | Active |
| 7.2 | Jun 1, 2023 | Ended | Jul 31, 2026 | 7.2.9 | No | EOL |
| 7.1 | May 10, 2022 | Ended | Jan 31, 2024 | 7.1.6 | No | EOL |
| 7.0 | Jul 29, 2021 | Ended | Jan 31, 2023 | 7.0.5 | No | EOL |
| 6.6 | Aug 12, 2020 | Ended | Jan 31, 2023 | 6.6.6 | No | EOL |
| 6.5 | Jan 21, 2020 | Ended | Feb 28, 2021 | 6.5.2 | No | EOL |
| 6.0 | Oct 31, 2018 | Ended | Jul 31, 2020 | 6.0.5 | No | EOL |
| 5.5 | Jul 23, 2018 | Ended | Jul 31, 2020 | 5.5.6 | No | EOL |
| 5.1 | Feb 28, 2018 | Ended | Jan 31, 2019 | 5.1.3 | No | EOL |
| 5.0 | Oct 26, 2017 | Ended | Aug 31, 2018 | 5.0.1 | No | EOL |
| 4.6 | Feb 16, 2017 | Ended | Aug 31, 2018 | 5.0.1 | No | EOL |
| 4.5 | Jun 27, 2016 | Ended | Apr 30, 2018 | 4.5.1 | No | EOL |
| 4.1 | Dec 10, 2015 | Ended | Apr 30, 2018 | 4.1.2 | No | EOL |
| 4.0 | Oct 6, 2015 | Ended | Apr 30, 2017 | 4.0.0 | No | EOL |
| 3.1 | Aug 31, 2015 | Ended | Feb 28, 2017 | 3.1.3 | No | EOL |
| 3.0 | Dec 17, 2014 | Ended | Apr 30, 2016 | 3.0.3 | No | EOL |
| 2.5 | Feb 28, 2014 | Ended | Dec 31, 2015 | 2.5.0 | No | EOL |
| 2.2 | Sep 30, 2013 | Ended | Mar 31, 2015 | 2.2.0 | No | EOL |
| 2.1 | Jun 26, 2013 | Ended | Dec 31, 2014 | 2.1.0 | No | EOL |
| 2.0 | Dec 31, 2012 | Ended | Jun 30, 2014 | 2.0.0 | No | EOL |
| 1.8 | Jul 31, 2012 | Ended | Jan 31, 2014 | 1.8.0 | No | EOL |
Data sources
Embed this badge
Show Couchbase Server'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/couchbase-server/)HTML
<a href="https://eol.wiki/couchbase-server/"><img src="https://eol.wiki/badge/couchbase-server.svg" alt="Couchbase Server end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Couchbase Server have reached end of life?
The following Couchbase Server versions have reached end of life and no longer receive security updates: 7.2, 7.1, 7.0, 6.6, 6.5, 6.0, 5.5, 5.1 (and 12 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Couchbase Server 7.2?
Couchbase Server 7.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 Couchbase Server?
The latest version of Couchbase Server is 8.0.3, released in the 8.0 release cycle.
How many versions of Couchbase Server are currently supported?
Couchbase Server currently has 2 actively supported version(s): 8.0, 7.6.
When does Couchbase Server 8.0 reach end of life?
Couchbase Server 8.0 is scheduled to reach end of life on Oct 31, 2028.
What should I do when Couchbase Server reaches end of life?
When a Couchbase Server 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.