Documentation

Delete a database

Use the influxdb3 delete database command, the HTTP API, or InfluxDB 3 Explorer to delete a database from InfluxDB 3 Core.

Deleting a database cannot be undone

Deleting a database is a destructive action. Once a database is deleted, data stored in that database cannot be recovered.

Delete a database using the influxdb3 CLI

Provide the following:

  • Name of the database to delete
influxdb3 delete database 
DATABASE_NAME

Replace the following:

  • DATABASE_NAME: the name of the database to delete

Enter yes to confirm that you want to delete the database.

Delete a database using the HTTP API

To delete a database using the HTTP API, send a DELETE request to the /api/v3/configure/database endpoint:

DELETE localhost:8181/api/v3/configure/database

Include the following in your request:

  • Query parameters:
    • db: Database name to delete
  • Headers:
curl --request DELETE "localhost:8181/api/v3/configure/database?db=
DATABASE_NAME
"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Replace the following:

  • DATABASE_NAME: the name of the database to delete
  • AUTH_TOKEN: your admin token

Response

A successful deletion returns HTTP status 200 with no content body.

Delete a database using InfluxDB 3 Explorer

You can also delete databases using the InfluxDB 3 Explorer web interface:

  1. If you haven’t already, see how to get started with Explorer and connect to your InfluxDB 3 Core server.
  2. In Explorer, click Databases in the left navigation.
  3. Find the database you want to delete in the list.
  4. Click the Delete icon (trash can) next to the database name.
  5. In the confirmation dialog, type the database name to confirm.
  6. Click Delete Database.

This action cannot be undone. All data in the database will be permanently deleted.

For more information, see Manage databases with InfluxDB 3 Explorer.


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