Skip to content
Database

InfluxDB Releases

Track every InfluxDB release from latest stable to end-of-life. Version timelines, architecture shifts, query language evolution, and migration guidance.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

1.8
2.x
3.0
2022 2023 2024 2025 2026 2027 2028 2029
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

1.x 2.x High Difficulty
Est. 1-3 days

Breaking Changes

  • New data model: databases→buckets, retention policies→bucket retention
  • Flux query language (InfluxQL still supported)
  • Token-based authentication replaces username/password
  • Organizations and users model
  • Continuous queries replaced by Tasks
  • Kapacitor functionality partially merged

Migration Notes

Use the influx upgrade CLI tool for in-place upgrade of OSS. The tool migrates databases to buckets, users to tokens, and continuous queries to tasks. Telegraf configs need DBRP mapping updates. Budget significant time for Flux query migration if moving off InfluxQL.

2.x 3.0 High Difficulty
Est. 1-2 weeks

Breaking Changes

  • Completely new storage engine (Arrow/DataFusion/Parquet)
  • Flux query language deprecated (use SQL or InfluxQL)
  • No in-place upgrade — parallel deployment required
  • API changes (v3 write API)
  • New partitioning and retention model

Migration Notes

This is NOT an upgrade, it is a migration to a new system. Export data from 2.x, reimport into 3.0. Rewrite Flux queries to SQL or InfluxQL. Deploy 3.0 in parallel, validate, then cut over. The new engine is significantly faster but the migration is substantial.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
InfluxDB 1.x Critical Medium EOL Dropped Critical EOL — migrate to 2.x or directly to 3.0
InfluxDB 2.x Medium Low Maintenance Full Medium Supported but Flux is deprecated — plan 3.0 migration
InfluxDB 3.0 None Low Active Full Low Current — recommended for new deployments

Risk combines EOL status, query language deprecation, and architecture migration effort. Assessed as of March 2026.

Architecture Comparison

Side-by-side feature differences across major versions.

Feature 1.x 2.x 3.0
Storage engine TSM TSM Arrow/Parquet
Query languages InfluxQL Flux + InfluxQL SQL + InfluxQL
Data model Database/RP Org/Bucket Database/Table
Web UI Chronograf Built-in Built-in
Authentication User/pass Tokens Tokens
Clustering (OSS) No No Community Edition
License MIT MIT (OSS) Apache 2.0 / MIT
Compression ratio Good Good Excellent (Parquet)

Embed Badges

Add live InfluxDB status badges to your README, docs, or dashboard.

Health Status

Overall support health

InfluxDB Health Status
![InfluxDB Health Status](https://img.releaserun.com/badge/health/influxdb.svg)

EOL Countdown

Next end-of-life date

InfluxDB EOL Countdown
![InfluxDB EOL Countdown](https://img.releaserun.com/badge/eol/influxdb.svg)

Latest Version

Current stable release

InfluxDB Latest Version
![InfluxDB Latest Version](https://img.releaserun.com/badge/v/influxdb.svg)

CVE Status

Known vulnerabilities

InfluxDB CVE Status
![InfluxDB CVE Status](https://img.releaserun.com/badge/cve/influxdb.svg)

Frequently Asked Questions

Common questions about InfluxDB releases and lifecycle.

What are the differences between InfluxDB 1.x, 2.x, and 3.0?
Each major version is a fundamentally different architecture. 1.x uses InfluxQL, TSM storage, and a simple write API. 2.x adds Flux query language, a web UI, organizations/buckets, and unified platform. 3.0 is a complete rewrite using Apache Arrow, DataFusion, and Parquet, with SQL and InfluxQL support (Flux deprecated).
Should I use InfluxDB or Prometheus?
Prometheus is pull-based, optimized for monitoring and alerting, and has a massive ecosystem (Grafana, AlertManager). InfluxDB is push-based, better for IoT/sensor data with variable schemas, and offers longer-term storage. For infrastructure monitoring, Prometheus is the standard. For IoT or high-cardinality time series, consider InfluxDB.
Is InfluxDB 3.0 open source?
InfluxDB 3.0 Core and Community are open source under Apache 2.0 and MIT licenses respectively. This is a return to open source after InfluxDB 2.x Cluster was proprietary. The 3.0 engine is built on Apache DataFusion and Arrow.
What happened to Flux query language?
Flux is deprecated in InfluxDB 3.0. The 3.0 engine supports SQL (via DataFusion) and InfluxQL. Flux was powerful but had a steep learning curve and poor performance at scale. SQL compatibility is the direction forward.
How hard is migrating between InfluxDB versions?
Migration between major versions is significant. 1.x→2.x requires tooling (influx upgrade CLI). 2.x→3.0 requires data export/reimport because the storage engine is completely different. There is no in-place upgrade from 2.x to 3.0. Plan for a parallel deployment migration.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.