Documentation

Data retention in InfluxDB Cloud

The InfluxDB Cloud retention enforcement service checks for and removes data with timestamps beyond the defined retention period of the bucket the data is stored in. This service is designed to automatically delete “expired” data and optimize disk usage without any user intervention.

Bucket retention period

A bucket retention period is the duration of time that a bucket retains data. Retention periods can be infinite or as short as an hour. Points in a bucket with timestamps beyond the defined retention period (relative to now) are flagged for deletion (also known as “tombstoned”).

View bucket retention periods

Use the influx bucket list command to view the retention period buckets in your organization.

When does data actually get deleted?

The InfluxDB Cloud retention enforcement service runs hourly and tombstones all points with timestamps beyond the bucket retention period. Tombstoned points persist on disk, but are filtered from all query results until the next compaction cycle, when they are removed from disk. Compaction cycle intervals vary.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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