Prometheus End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Prometheus 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 |
|---|---|---|---|---|---|
| 2.36 | 2.36.2 | May 30, 2022 | Jul 11, 2022 | 1500 days past EOL | EOL |
| 2.37 LTS | 2.37.9 | Jul 14, 2022 | Jul 31, 2023 | 1115 days past EOL | EOL |
| 2.38 | 2.38.0 | Aug 16, 2022 | Sep 27, 2022 | 1422 days past EOL | EOL |
| 2.39 | 2.39.2 | Oct 5, 2022 | Nov 16, 2022 | 1372 days past EOL | EOL |
| 2.40 | 2.40.7 | Nov 7, 2022 | Dec 19, 2022 | 1339 days past EOL | EOL |
| 2.41 | 2.41.0 | Dec 20, 2022 | Jan 31, 2023 | 1296 days past EOL | EOL |
| 2.42 | 2.42.0 | Jan 31, 2023 | Mar 14, 2023 | 1254 days past EOL | EOL |
| 2.43 | 2.43.1 | Mar 21, 2023 | May 2, 2023 | 1205 days past EOL | EOL |
| 2.44 | 2.44.0 | May 14, 2023 | Aug 6, 2023 | 1109 days past EOL | EOL |
| 2.45 LTS | 2.45.6 | Jun 23, 2023 | Jul 31, 2024 | 749 days past EOL | EOL |
| 2.46 | 2.46.0 | Jul 25, 2023 | Sep 5, 2023 | 1079 days past EOL | EOL |
| 2.47 | 2.47.2 | Sep 6, 2023 | Oct 18, 2023 | 1036 days past EOL | EOL |
| 2.48 | 2.48.1 | Nov 15, 2023 | Dec 28, 2023 | 965 days past EOL | EOL |
| 2.49 | 2.49.1 | Jan 15, 2024 | Feb 26, 2024 | 905 days past EOL | EOL |
| 2.50 | 2.50.1 | Feb 22, 2024 | Apr 4, 2024 | 867 days past EOL | EOL |
| 2.51 | 2.51.2 | Mar 19, 2024 | Apr 30, 2024 | 841 days past EOL | EOL |
| 2.52 | 2.52.0 | May 8, 2024 | Jun 19, 2024 | 791 days past EOL | EOL |
| 2.53 LTS | 2.53.5 | Jun 16, 2024 | Jul 31, 2025 | 384 days past EOL | EOL |
| 2.54 | 2.54.1 | Aug 9, 2024 | Sep 20, 2024 | 698 days past EOL | EOL |
| 2.55 | 2.55.1 | Oct 22, 2024 | Dec 3, 2024 | 624 days past EOL | EOL |
| 3.0 | 3.0.1 | Nov 14, 2024 | Dec 26, 2024 | 601 days past EOL | EOL |
| 3.1 | 3.1.0 | Jan 2, 2025 | Feb 13, 2025 | 552 days past EOL | EOL |
| 3.2 | 3.2.1 | Feb 17, 2025 | Mar 31, 2025 | 506 days past EOL | EOL |
| 3.3 | 3.3.1 | Apr 15, 2025 | May 27, 2025 | 449 days past EOL | EOL |
| 3.4 | 3.4.2 | May 17, 2025 | Jun 28, 2025 | 417 days past EOL | EOL |
| 3.5 LTS | 3.5.5 | Jul 14, 2025 | Jul 31, 2026 | 19 days past EOL | EOL |
| 3.6 | 3.6.0 | Sep 17, 2025 | Nov 2, 2025 | 290 days past EOL | EOL |
| 3.7 | 3.7.3 | Oct 15, 2025 | Nov 26, 2025 | 266 days past EOL | EOL |
| 3.8 | 3.8.1 | Nov 28, 2025 | Jan 9, 2026 | 222 days past EOL | EOL |
| 3.9 | 3.9.1 | Jan 6, 2026 | Feb 17, 2026 | 183 days past EOL | EOL |
| 3.10 | 3.10.0 | Feb 25, 2026 | Apr 8, 2026 | 133 days past EOL | EOL |
| 3.11 | 3.11.3 | Apr 2, 2026 | May 14, 2026 | 97 days past EOL | EOL |
| 3.12 | 3.12.0 | May 28, 2026 | Jul 9, 2026 | 41 days past EOL | EOL |
| 3.13 LTS | 3.13.2 | Jul 1, 2026 | Jul 31, 2027 | 346 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/prometheus)
What does Prometheus end of life mean for your organization?
When a version of Prometheus 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 Prometheus 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 Prometheus 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, extended support vendors provide continued security patches for EOL Prometheus versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Prometheus has 33 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 Prometheus 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."