boundary end of life dates — full support timeline
3 of 6 tracked boundary 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 |
|---|---|---|---|---|
| 0.21 | 2025-12-11 | not announced | 0.21.3 | supported |
| 0.20 | 2025-09-25 | not announced | 0.20.3 | supported |
| 0.19 | 2025-02-10 | not announced | 0.19.5 | supported |
| 0.18 | 2024-10-14 | 2025-12-11 | 0.18.2 | ended |
| 0.17 | 2024-07-31 | 2025-09-25 | 0.17.2 | ended |
| 0.16 | 2024-04-30 | 2025-02-10 | 0.16.3 | ended |
Who is affected
Anyone running an unsupported boundary 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/boundary, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next boundary deadline
You are reading this because a boundary 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 boundary and related deadline as it is announced, with exact dates and primary sources.
Watch boundary deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.