Port 9093 PROMETHEUS ALERTMANAGER
Port 9093 is most commonly used by Prometheus Alertmanager. The IANA registry lists TCP for this number.
What is port 9093 used for?
Port 9093 is most commonly used by Prometheus Alertmanager. Prometheus Alertmanager commonly listens on port 9093. 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 copycat connects to port 9093. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 9093 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 Monitoring and metrics ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Microtec_Informatique].
Check and block port 9093
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 = :9093'Check on Windows
Get-NetTCPConnection -LocalPort 9093 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 9093/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 9093 -j DROPThese 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 9093 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 9093 is usually used
Most traffic on port 9093 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Scrapers such as Prometheus pulling metrics from port 9093 on a schedule.
- Dashboards and alerting rules querying the same endpoint.
- Incident reviews comparing metrics before and after a deployment.
Check Alertmanager health
The health endpoint confirms Alertmanager is up before you debug notification routes.
curl -s http://127.0.0.1:9093/-/healthyCommon problems with port 9093
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 9093. 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 = :9093' or sudo lsof -i :9093. 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 9093 at a glance
| Port number | 9093 |
|---|---|
| IANA service name | copycat |
| Commonly used by | Prometheus Alertmanager |
| Transport protocol | TCP |
| Category | Monitoring and metrics |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Microtec_Informatique] |
| Registry description | Copycat database replication service |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 9093 used for?
Port 9093 (PROMETHEUS ALERTMANAGER). The IANA registry lists TCP for this number. Prometheus Alertmanager commonly listens on port 9093.
How do I check if port 9093 is open?
On Linux run `sudo ss -tlpn 'sport = :9093'`. On Windows run `Get-NetTCPConnection -LocalPort 9093 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 9093; empty output usually means nothing is bound to it.
How do I block port 9093?
With UFW run `sudo ufw deny 9093/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 9093 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 9093 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 9092 · XmlIpcRegSvcXml-Ipc Server Reg
- Port 9100 · hp-pdl-datastrPDL Data Streaming Port
- Port 9091 · xmltec-xmlmailxmltec-xmlmail
- Port 9090 · websmWebSM
- Port 9411 · ZipkinZipkin trace collector, API and web UI port (community convention; not…
- Port 5162 · snmpssh-trapSNMP Notification over SSH Transport Model
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy