← ← Back to all products
All badges & lifecycle API →
Hashicorp ConsulEnd of Life (EOL) Dates & Support Status
Active
Server SoftwareLatest Version: 2.0.4Latest Release: Sep 9, 2026
HashiCorp Consul is a service mesh and networking solution providing service discovery and configuration.
Support summary
Hashicorp Consul 1.22 reaches EOL in 34 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Oct 31, 2026
Hashicorp Consul 1.22 · 34 days left
Supported cycles
3
3 lts
Versions
18
Latest Version
2.0.4
Active Support
3
EOL
15
Lifecycle Timeline
Nov 15, 2022As of Sep 27, 2026
2.0Active · Apr 30, 2028
1.22Active · Oct 31, 2026
1.21Active · Apr 30, 2027
1.20EOL · May 24, 2026
1.19EOL · Oct 27, 2025
1.18EOL · Apr 30, 2026
1.17EOL · Oct 14, 2024
1.16EOL · Jun 12, 2024
1.15EOL · Apr 30, 2025
1.14EOL · Nov 3, 2023
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 |
|---|---|---|---|---|---|---|
| 2.0 | May 24, 2026 | Maintained | Apr 30, 2028 | 2.0.4 | No | Active |
| 1.22 | Oct 27, 2025 | Maintained | Oct 31, 2026 | 1.22.7 | No | Active |
| 1.21 | May 6, 2025 | Maintained | Apr 30, 2027 | 1.21.5 | Yes | Active |
| 1.20 | Oct 14, 2024 | Ended | May 24, 2026 | 1.20.6 | No | EOL |
| 1.19 | Jun 12, 2024 | Ended | Oct 27, 2025 | 1.19.2 | No | EOL |
| 1.18 | Feb 26, 2024 | Ended | Apr 30, 2026 | 1.18.2 | Yes | EOL |
| 1.17 | Nov 3, 2023 | Ended | Oct 14, 2024 | 1.17.4 | No | EOL |
| 1.16 | Jun 26, 2023 | Ended | Jun 12, 2024 | 1.16.7 | No | EOL |
| 1.15 | Feb 23, 2023 | Ended | Apr 30, 2025 | 1.15.11 | Yes | EOL |
| 1.14 | Nov 15, 2022 | Ended | Nov 3, 2023 | 1.14.11 | No | EOL |
| 1.13 | Aug 9, 2022 | Ended | Jun 26, 2023 | 1.13.9 | No | EOL |
| 1.12 | Apr 19, 2022 | Ended | Feb 23, 2023 | 1.12.9 | No | EOL |
| 1.11 | Dec 14, 2021 | Ended | Nov 15, 2022 | 1.11.11 | No | EOL |
| 1.10 | Jun 22, 2021 | Ended | Aug 9, 2022 | 1.10.12 | No | EOL |
| 1.9 | Nov 24, 2020 | Ended | Apr 19, 2022 | 1.9.17 | No | EOL |
| 1.8 | Jun 18, 2020 | Ended | Dec 14, 2021 | 1.8.19 | No | EOL |
| 1.7 | Feb 11, 2020 | Ended | Jun 22, 2021 | 1.7.14 | No | EOL |
| 1.6 | Aug 23, 2019 | Ended | Nov 24, 2020 | 1.6.10 | No | EOL |
Data sources
Embed this badge
Show Hashicorp Consul'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/consul/)HTML
<a href="https://eol.wiki/consul/"><img src="https://eol.wiki/badge/consul.svg" alt="Hashicorp Consul end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Hashicorp Consul have reached end of life?
The following Hashicorp Consul versions have reached end of life and no longer receive security updates: 1.20, 1.19, 1.18, 1.17, 1.16, 1.15, 1.14, 1.13 (and 7 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Hashicorp Consul 1.20?
Hashicorp Consul 1.20 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 Hashicorp Consul?
The latest version of Hashicorp Consul is 2.0.4, released in the 2.0 release cycle.
How many versions of Hashicorp Consul are currently supported?
Hashicorp Consul currently has 3 actively supported version(s): 2.0, 1.22, 1.21.
When does Hashicorp Consul 2.0 reach end of life?
Hashicorp Consul 2.0 is scheduled to reach end of life on Apr 30, 2028.
What should I do when Hashicorp Consul reaches end of life?
When a Hashicorp Consul 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.