Registered port (1024–10000) Medium risk

Port 8086 INFLUXDB

Quick answer

Port 8086 is most commonly used by InfluxDB. The IANA registry lists TCP / UDP for this number.

TransportTCP / UDP
RiskMedium
Typical useDatabases

What is port 8086 used for?

Port 8086 is most commonly used by InfluxDB. InfluxDB exposes its HTTP API on port 8086 by default; the IANA registry assigns the number to d-s-n. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.

Ports are the transport-layer address a service listens on. A client that wants to reach d-s-n connects to port 8086. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.

Use the commands below to confirm whether port 8086 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.

Browse all Databases ports

Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Gary_Hampton].

Check and block port 8086

Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.

Check on Linux

sudo ss -tlpn 'sport = :8086' sudo ss -ulpn 'sport = :8086'

Check on Windows

Get-NetTCPConnection -LocalPort 8086 -State Listen -ErrorAction SilentlyContinue Get-NetUDPEndpoint -LocalPort 8086 -ErrorAction SilentlyContinue

Block with UFW

sudo ufw deny 8086/tcp sudo ufw deny 8086/udp

Block with iptables

sudo iptables -A INPUT -p tcp --dport 8086 -j DROP sudo iptables -A INPUT -p udp --dport 8086 -j DROP

These commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.

Is port 8086 safe to expose?

Medium

InfluxDB's HTTP API can expose metrics and allow writes or queries. Require authentication and keep it on a private network. Expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.

Where port 8086 is usually used

Most traffic on port 8086 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.

Demo

Check InfluxDB health

The health endpoint returns JSON and needs no database credentials.

curl -s http://127.0.0.1:8086/health

Common problems with port 8086

Connection refused or timed out

Refused usually means the host is reachable but nothing is listening on port 8086. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.

Port already in use

Find the process holding the port with sudo ss -tlpn 'sport = :8086' or sudo lsof -i :8086. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.

Firewall rule did not survive a reboot

UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.

The port is blocked but still reachable

A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.

Port 8086 at a glance

Port number8086
IANA service named-s-n
Commonly used byInfluxDB
Transport protocolTCP / UDP
CategoryDatabases
RangeRegistered port (1024–10000)
Risk levelMedium
Registered assignee[Gary_Hampton]
Registry descriptionDistributed SCADA Networking Rendezvous Port
SourceIANA Service Name and Transport Protocol Port Number Registry

Frequently asked questions

What is port 8086 used for?

Port 8086 (INFLUXDB). The IANA registry lists TCP / UDP for this number. InfluxDB exposes its HTTP API on port 8086 by default; the IANA registry assigns the number to d-s-n.

How do I check if port 8086 is open?

On Linux run `sudo ss -tlpn 'sport = :8086'` and `sudo ss -ulpn 'sport = :8086'`. On Windows run `Get-NetTCPConnection -LocalPort 8086 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 8086 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 8086; empty output usually means nothing is bound to it.

How do I block port 8086?

With UFW run `sudo ufw deny 8086/tcp` and `sudo ufw deny 8086/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 8086 -j DROP` and `sudo iptables -A INPUT -p udp --dport 8086 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.

Is port 8086 safe to expose?

InfluxDB's HTTP API can expose metrics and allow writes or queries. Require authentication and keep it on a private network. Nevertheless, expose this port only when the service is actually needed. Keep it patched, prefer an encrypted alternative, and limit source addresses with a firewall allowlist.

See all Databases ports

Primary data: IANA Service Name and Transport Protocol Port Number Registry.

Last reviewed 2026-10-30 · Methodology · About · Privacy