Documentation

InfluxDB ports

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Enabled ports

8086

The default port that runs the InfluxDB HTTP service. Configure this port in the configuration file.

Resources API Reference

8088

The default port used by the RPC service for RPC calls made by the CLI for backup and restore operations (influxdb backup and influxd restore). Configure this port in the configuration file.

Resources Backup and Restore

Disabled ports

2003

The default port that runs the Graphite service. Enable and configure this port in the configuration file.

Resources Graphite README

4242

The default port that runs the OpenTSDB service. Enable and configure this port in the configuration file.

Resources OpenTSDB README

8089

The default port that runs the UDP service. Enable and configure this port in the configuration file.

Resources UDP README

25826

The default port that runs the Collectd service. Enable and configure this port in the configuration file.

Resources Collectd README


Was this page helpful?

Thank you for your feedback!


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:

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