erlang end of life dates — full support timeline
10 of 13 tracked erlang 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 |
|---|---|---|---|---|
| 29 | 2026-05-11 | 2029-05-11 | 29.0.4 | supported |
| 28 | 2025-05-20 | 2028-05-20 | 28.5.0.4 | supported |
| 27 | 2024-05-17 | 2027-05-20 | 27.3.4.15 | supported |
| 26 | 2023-05-15 | 2026-05-26 | 26.2.5.21 | ended |
| 25 | 2022-05-17 | 2025-05-17 | 25.3.2.21 | ended |
| 24 | 2021-05-10 | 2024-05-10 | 24.3.4.17 | ended |
| 23 | 2020-05-11 | 2024-03-14 | 23.3.4.20 | ended |
| 22 | 2019-05-10 | 2024-03-18 | 22.3.4.27 | ended |
| 21 | 2018-06-19 | 2021-06-19 | 21.3.8.24 | ended |
| 20 | 2017-06-21 | 2020-06-21 | 20.3.8.26 | ended |
| 19 | 2016-06-21 | 2019-06-21 | 19.3.6.13 | ended |
| 18 | 2015-06-23 | 2018-11-09 | 18.3.4.11 | ended |
| 17 | 2014-04-07 | 2018-10-11 | 17.5.6.10 | ended |
Who is affected
Anyone running an unsupported erlang 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/erlang, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next erlang deadline
You are reading this because a erlang 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 erlang and related deadline as it is announced, with exact dates and primary sources.
Watch erlang deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.