influxdb end of life dates — full support timeline
9 of 13 tracked influxdb 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 |
|---|---|---|---|---|
| 3.10 | 2026-06-17 | not announced | 3.10.5 | supported |
| 3.9 | 2026-04-02 | not announced | 3.9.11 | supported |
| 3.8 | 2025-12-18 | 2026-06-17 | 3.8.3 | ended |
| 3.7 | 2025-11-19 | 2026-04-02 | 3.7.0 | ended |
| 3.6 | 2025-10-30 | 2025-12-18 | 3.6.0 | ended |
| 3.5 | 2025-09-29 | 2025-11-19 | 3.5.0 | ended |
| 3.4 | 2025-08-26 | 2025-10-30 | 3.4.2 | ended |
| 3.3 | 2025-07-29 | 2025-09-29 | 3.3.0 | ended |
| 3.2 | 2025-06-25 | 2025-08-26 | 3.2.1 | ended |
| 3.1 | 2025-05-28 | 2025-07-30 | 3.1.0 | ended |
| 3.0 | 2025-04-14 | 2025-06-25 | 3.0.3 | ended |
| 2 | 2020-11-09 | not announced | 2.9.1 | supported |
| 1 | 2016-09-07 | not announced | 1.12.4 | supported |
Who is affected
Anyone running an unsupported influxdb 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/influxdb, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next influxdb deadline
You are reading this because a influxdb 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 influxdb and related deadline as it is announced, with exact dates and primary sources.
Watch influxdb deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.