xcp ng end of life dates — full support timeline
6 of 7 tracked xcp ng releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 8.3 | 2024-10-07 | 2028-11-30 | 8.3.0 | supported |
| 8.2 LTS | 2020-11-13 | 2025-06-25 | 8.2.1 | ended |
| 8.1 | 2020-03-31 | 2021-03-31 | 8.1.0 | ended |
| 8.0 | 2019-07-25 | 2020-11-13 | 8.0.0 | ended |
| 7.6 | 2018-10-31 | 2020-03-30 | 7.6.0 | ended |
| 7.5 | 2018-08-10 | 2019-07-25 | 7.5.0 | ended |
| 7.4 | 2018-03-31 | 2018-10-31 | 7.4.0 | ended |
Who is affected
Anyone running an unsupported xcp ng release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/xcp-ng, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next xcp ng deadline
You are reading this because a xcp ng release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every xcp ng and related deadline as it is announced, with exact dates and primary sources.
Watch xcp ng deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.