Documentation

Select product

InfluxDB 3

  • InfluxDB 3 Core New
  • InfluxDB 3 Enterprise New
  • InfluxDB Clustered
  • InfluxDB 3 Cloud New
  • InfluxDB Cloud Serverless
  • InfluxDB Cloud Dedicated
  • InfluxDB 3 Explorer New

InfluxDB 2

  • InfluxDB OSS v2
  • InfluxDB Cloud (TSM)
  • Flux

InfluxDB 1

  • InfluxDB OSS v1
  • InfluxDB Enterprise
  • InfluxDB Cloud 1

Telegraf

  • Telegraf
  • Telegraf Controller New
  • Telegraf Enterprise New

Other products

  • Chronograf
  • Kapacitor

    Enterprise_influxdbs


    Was this page helpful?

    Thank you for your feedback!


    Support and feedback

    Thank you for being part of our community! We welcome and encourage your feedback and bug reports for and this documentation. To find support, use the following resources:

    • InfluxDB Community Slack (Preferred)
    • InfluxData Community
    • InfluxDB Subreddit

    Customers with an annual or support contract can contact InfluxData Support.

    Edit this page Submit docs issue

    On this page

    © 2026 InfluxData, Inc.

    Where are you running InfluxDB?

    Customize your InfluxDB Enterprise URL and we’ll update code examples for you.

    • InfluxDB Cloud
    • InfluxDB OSS or Enterprise
    AWS
    • US West (Oregon)

    GCP
    Azure
    Default
    Custom

    For more information, see InfluxDB Enterprise HTTP settings.

    Thank you for your feedback!

    Let us know what we can do better:

    Thank you!

    No thanks

    InfluxDB OSS 2.9.0: API tokens are hashed by default

    Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

    View InfluxDB OSS 2.9.0 release notes

    Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

    Also new in 2.9.0:

    • Configurable backup compression
    • Restore support for backups containing hashed tokens
    • Tighter Edge Data Replication queue validation
    • Flux upgrade
    • Compaction reliability improvements

    Explorer 1.11 is now available

    Six new visualization types, plus password and SSO sign-in and user management for InfluxDB 3 Enterprise.
    • Password and SSO sign-in with role-based access.
    • Manage Users page under a new Security section.
    • New visualizations: Area, Single Stat, Gauge, Pie, Scatter, and Ranking.
    • EXPLAIN and EXPLAIN ANALYZE in the SQL editor.

    Explorer 1.11 release notes

    InfluxDB 3.12 is now available

    Back up your catalog before you upgrade. Rolling back to 3.11.x requires restoring that backup.
    • Add columns to existing tables with influxdb3 update table.
    • Faster queries and startup with DataFusion 52.5.
    • New defaults: finite --max-concurrent-queries and an enforced WAL buffer limit.

    Upgrade guide | Release notes | Announcement

    InfluxDB 3 Enterprise 3.12 is now available

    Back up your catalog before you upgrade. Rolling back to 3.11.x requires restoring that backup.
    • Faster bulk import, including from object storage.
    • Distributed compaction (beta).
    • Schema enforcement per database.
    • User authentication and RBAC are generally available.

    Upgrade guide | Release notes | Announcement

    Telegraf Controller 1.1 now available

    Telegraf Controller 1.1 adds high availability (Telegraf Enterprise), global constants, configuration groups, configuration aliases, and configuration versioning.

    Telegraf Controller 1.1 lets teams make fleet-wide configuration changes with a single edit using global constants, configuration groups, and configuration aliases. Configuration versioning makes every change traceable, comparable, and reversible. High availability, available with Telegraf Enterprise, automatically fails over between Controller instances so agents can continue pulling configurations and reporting health if an instance goes down.

    • Read the announcement
    • See the release notes
    • Download and install Telegraf Controller 1.1

    InfluxDB OSS 1.13.0 is now available

    InfluxDB OSS 1.13.0 adds mTLS support, adaptive TSI cache sizing, and a hardening option to mitigate SSRF.

    View InfluxDB OSS 1.13.0 release notes

    Key updates in InfluxDB OSS 1.13.0:

    • mTLS support for the HTTP, OpenTSDB, and subscriber services.
    • Adaptive TSI cache sizing—the series ID set cache can grow and shrink based on measured query hit rate.
    • hardening-enabled option to mitigate server-side request forgery (SSRF) in Flux HTTP requests.

    For details, see the InfluxDB OSS 1.13.0 release notes.

    InfluxDB Docker latest tag changing to InfluxDB 3 Core

    On September 15, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

    If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

    docker pull influxdb:2