EOL.Wiki EOL.Wiki
← ← Back to all products

InfluxDB

Active
Databases Latest Version: 3.8.1 Latest Release: Jan 12, 2026

InfluxDB is a purpose-built time series database for metrics, events, and real-time analytics.

Versions

11

Latest Version

3.8.1

Active Support

4

EOL

7

Lifecycle Timeline

Today
3.8
3.8
3.7
3.7
3.6
3.6
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
2
2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.8Dec 18, 2025-No3.8.1No
Active
3.7Nov 19, 2025-No3.7.0No
Active
3.6Oct 30, 2025-Dec 18, 20253.6.0No
EOL
3.5Sep 29, 2025-Nov 19, 20253.5.0No
EOL
3.4Aug 26, 2025-Oct 30, 20253.4.2No
EOL
3.3Jul 29, 2025-Sep 29, 20253.3.0No
EOL
3.2Jun 25, 2025-Aug 26, 20253.2.1No
EOL
3.1May 28, 2025-Jul 30, 20253.1.0No
EOL
3.0Apr 14, 2025-Jun 25, 20253.0.3No
EOL
2Nov 9, 2020-No2.8.0No
Active
1Sep 7, 2016-No1.12.2No
Active

Frequently Asked Questions

Which versions of InfluxDB have reached end of life?
The following InfluxDB versions have reached end of life and no longer receive security updates: 3.6, 3.5, 3.4, 3.3, 3.2, 3.1, 3.0. It is recommended to upgrade to a supported version.
Is it safe to continue using InfluxDB 3.6?
InfluxDB 3.6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of InfluxDB?
The latest version of InfluxDB is 3.8.1, released in the 3.8 release cycle.
How many versions of InfluxDB are currently supported?
InfluxDB currently has 4 actively supported version(s): 3.8, 3.7, 2, 1.
When does InfluxDB 3.8 reach end of life?
InfluxDB 3.8 does not have a specific end-of-life date announced yet.
What should I do when InfluxDB reaches end of life?
When a InfluxDB version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.