logstash end of life dates — full support timeline
8 of 10 tracked logstash 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 |
|---|---|---|---|---|
| 9.4 | 2026-05-08 | not announced | 9.4.4 | supported |
| 9.3 | 2026-02-03 | 2026-05-08 | 9.3.8 | ended |
| 9.2 | 2025-10-21 | 2026-03-31 | 9.2.8 | ended |
| 9.1 | 2025-07-22 | 2026-01-07 | 9.1.10 | ended |
| 8.19 | 2025-07-14 | 2027-07-15 | 8.19.19 | supported |
| 8.18 | 2025-04-09 | 2025-10-21 | 8.18.8 | ended |
| 9.0 | 2025-03-17 | 2025-09-30 | 9.0.8 | ended |
| 8.17 | 2024-12-04 | 2025-08-06 | 8.17.10 | ended |
| 7 | 2019-04-05 | 2026-01-15 | 7.17.29 | ended |
| 6 | 2017-11-08 | 2022-02-10 | 6.8.23 | ended |
Who is affected
Anyone running an unsupported logstash 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/logstash, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next logstash deadline
You are reading this because a logstash 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 logstash and related deadline as it is announced, with exact dates and primary sources.
Watch logstash deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.