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 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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

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