Port 15692 RABBITMQ EXPORTER
Port 15692 is the community default for RabbitMQ exporter, using TCP.
What is port 15692 used for?
Port 15692 is widely used by RabbitMQ exporter (TCP), a community convention rather than an IANA assignment. Prometheus metrics endpoint exposed by the RabbitMQ exporter (community convention). It sits above the registered range, where most numbers are transient client ports. A fixed high port is worth documenting precisely because tooling often assumes the default.
Ports are the transport-layer address a service listens on. A client that wants to reach RabbitMQ exporter connects to port 15692. 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 15692 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.
Because this number is not IANA-assigned, a different application may legitimately use it on a machine you do not control. Always identify the actual listening process before deciding that the port belongs to this technology.
Browse all Monitoring and metrics ports
This port number is not assigned by IANA. The entry documents a widely adopted community convention.
Check and block port 15692
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 = :15692'Check on Windows
Get-NetTCPConnection -LocalPort 15692 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 15692/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 15692 -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 15692 safe to expose?
RabbitMQ's Prometheus exporter exposes queue and connection metrics. Restrict it to your monitoring 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 15692 is usually used
Most traffic on port 15692 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 15692 on a schedule.
- Dashboards and alerting rules querying the same endpoint.
- Incident reviews comparing metrics before and after a deployment.
Scrape RabbitMQ exporter metrics
Read the first lines of the exporter's Prometheus metrics.
curl -s http://127.0.0.1:15692/metrics | headCommon problems with port 15692
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 15692. 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 = :15692' or sudo lsof -i :15692. 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 15692 at a glance
| Port number | 15692 |
|---|---|
| Service name | RabbitMQ exporter |
| Transport protocol | TCP |
| Category | Monitoring and metrics |
| Range | High port (10001–65535) |
| Risk level | Medium |
| Reference | Community convention (not IANA-assigned) |
| Registry description | Prometheus metrics endpoint exposed by the RabbitMQ exporter (community convention) |
| Source | Community convention |
Frequently asked questions
What is port 15692 used for?
Port 15692 (RABBITMQ EXPORTER) uses TCP. Prometheus metrics endpoint exposed by the RabbitMQ exporter (community convention) (community convention, not an IANA assignment).
How do I check if port 15692 is open?
On Linux run `sudo ss -tlpn 'sport = :15692'`. On Windows run `Get-NetTCPConnection -LocalPort 15692 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 15692; empty output usually means nothing is bound to it.
How do I block port 15692?
With UFW run `sudo ufw deny 15692/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 15692 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 15692 safe to expose?
RabbitMQ's Prometheus exporter exposes queue and connection metrics. Restrict it to your monitoring 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.
Related ports
- Port 15672 · rabbitmq-managementRabbitMQ management web UI and HTTP API port
- Port 15740 · ptpPicture Transfer Protocol
- Port 12322 · warehouseWarehouse Monitoring Syst
- Port 18242 · iclidCheckpoint router monitoring
- Port 12321 · warehouse-sssWarehouse Monitoring Syst SSS
- Port 19999 · dnp-secDistributed Network Protocol - secured
Primary data: IANA Service Name and Transport Protocol Port Number Registry. This number is a community convention, not an IANA assignment.
Last reviewed 2026-10-30 · Methodology · About · Privacy