Documentation

Data retention in InfluxDB Cloud Serverless

InfluxDB Cloud Serverless enforces bucket retention periods at query time. Any points with timestamps beyond a bucket’s retention period are filtered out of query results, even though the data may still exist.

Bucket retention period

A bucket retention period is the duration of time that a bucket retains data. Retention periods are designed to automatically delete expired data and optimize storage without any user intervention.

Retention periods can be as short as an hour or infinite. Points in a bucket with timestamps beyond the defined retention period (relative to now) are not queryable, but may still exist in storage until fully deleted.

View bucket retention periods

Use the influx bucket list command to view your buckets’ retention periods.

When does data actually get deleted?

InfluxDB routinely deletes Parquet files containing only expired data. InfluxDB retains expired Parquet files for at least 100 days for disaster recovery. After the disaster recovery period, expired Parquet files are permanently deleted and can’t be recovered.


Was this page helpful?

Thank you for your feedback!


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.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-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 Serverless