Documentation

Cancel your InfluxDB Cloud subscription

To cancel your InfluxDB Cloud (TSM) subscription, complete the following steps:

  1. Stop reading and writing data.
  2. Export data and other artifacts.
  3. Cancel service.

Stop reading and writing data

To stop being charged for InfluxDB Cloud, pause all writes and queries.

Export data and other artifacts

To export data and artifacts, follow the steps below.

Exported data and artifacts can be used in an InfluxDB OSS instance.

Export tasks

For details, see Export a task.

Export dashboards

For details, see Export a dashboard.

Save Telegraf configurations

  1. Click the Load Data icon in the navigation bar.

  2. Select the Telegraf tab. A list of existing Telegraf configurations appears.

  3. Click the name of a Telegraf configuration.

  4. Click Download Config to save.

Export data

To export all your data, query your data out in time-based batches and store it in to an external system or an InfluxDB OSS instance.

For information about automatically exporting and migrating data from InfluxDB Cloud to InfluxDB OSS, see: Migrate data from InfluxDB Cloud to InfluxDB OSS.

Cancel service

Cancelling your usage-based plan will delete your organization.

  1. Click the account name in the header of your InfluxDB Cloud user interface (UI) and select Billing.

  2. Do one of the following:

  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through AWS Marketplace, click the AWS link, click Unsubscribe, and then click Yes, cancel subscription.
  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through GCP Marketplace, click the GCP link, click Unsubscribe, and then click Yes, cancel subscription.
  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through InfluxData, click Cancel Service. Select I understand and agree to these conditions, and then click I understand, Cancel Service. Click Confirm and Cancel Service. Your payment method is charged your final balance immediately upon cancellation of service.

Was this page helpful?

Thank you for your feedback!


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

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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

InfluxDB Cloud powered by TSM