InfluxDB End of Service Life Dates
InfluxDB has published end-of-service-life dates for 10 products in our catalog. 0 reach EOSL within the next 12 months and 10 are already past OEM support. Third-party support keeps those releases covered after the vendor stops shipping patches: issue management, vulnerability remediation and compliance maintenance.
InfluxDB products reaching EOSL in 2026(3)
| Model | EOSL date | |
|---|---|---|
| InfluxDB 3.7 | Apr 2, 2026 | Get price |
| InfluxDB 3.8 | Jun 17, 2026 | Get price |
| InfluxDB 3.9 | Jul 30, 2026 | Get price |
InfluxDB products reaching EOSL in 2025(7)
| Model | EOSL date | |
|---|---|---|
| InfluxDB 3.0 | Jun 25, 2025 | Get price |
| InfluxDB 3.1 | Jul 30, 2025 | Get price |
| InfluxDB 3.2 | Aug 26, 2025 | Get price |
| InfluxDB 3.3 | Sep 29, 2025 | Get price |
| InfluxDB 3.4 | Oct 30, 2025 | Get price |
| InfluxDB 3.5 | Nov 19, 2025 | Get price |
| InfluxDB 3.6 | Dec 18, 2025 | Get price |
InfluxDB EOSL: Frequently Asked Questions
What does end of service life (EOSL) mean for InfluxDB equipment?
EOSL is the date after which InfluxDB no longer sells support contracts or ships updates for a product. The equipment keeps working; only the OEM's willingness to support it ends. Third-party maintenance takes over from that date with engineering support and replacement parts.
Can I get support for InfluxDB products that are already past EOSL?
Yes. 10 InfluxDB products in this list are already past their EOSL date and all remain supportable. We hold spares for every model we quote and cover equipment for 5+ years past the OEM date.
How far ahead should I plan for a InfluxDB EOSL date?
Start 6 to 12 months before the EOSL date. That is enough time to compare the OEM's final renewal against third-party maintenance, decide whether to extend or refresh, and move coverage without a gap. We return an indicative price within 24 hours and a firm quote within 48.