Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Monitors

Port monitors (TCP and UDP)

A port monitor checks that a service is listening on a port. Use it for mail servers, databases, SSH, game servers and anything else that is not a web page.

There are two kinds. Port (TCP) is for most services. Port (UDP) is for services that answer over UDP, such as game servers, DNS, NTP, VoIP and SNMP.

What you need first

  • The public host name or IP address of the server.
  • The port number, from 1 to 65535.
  • The port must be reachable from the internet. If a firewall only lets in known addresses, see Allowing our checks through a firewall.
  • For UDP: the packet the service expects. Most UDP services stay silent when they get a packet they do not understand, and silence counts as a failure.

Only public internet addresses work. Private and internal addresses are refused when you save.

Set up a TCP port monitor

  1. Open Monitors and press Add monitor.
  2. Choose Port (TCP).
  3. In Host, type the host name or IP address, for example mail.example.com.
  4. In Port, type the port number. A port check cannot be saved without one.
  5. Give it a Friendly name, such as "Mail server SMTP".
  6. Choose Check every, look over Where alerts go, and press Start monitoring.

Each check opens a connection to the port and closes it straight away. If the connection opens, the check passes. The time shown is how long it took to connect. Nothing is sent to the service.

Common ports

ServiceUsual port
SSH22
Mail (SMTP)25 or 587
Mail (IMAP over TLS)993
MySQL and MariaDB3306
PostgreSQL5432
Remote Desktop3389

Your server may use different ports. Check its settings if you are not sure.

Set up a UDP port monitor

  1. Open Monitors, press Add monitor and choose Port (UDP).
  2. Fill in Host and Port.
  3. In Packet to send, type the request the service answers. You can write bytes as \x escapes. The placeholder shows a Source engine game server query: \xff\xff\xff\xffTSource Engine Query\x00. If you leave it empty, a single zero byte is sent.
  4. Optionally, fill in Reply must contain with text the answer should include. Leave it empty to accept any reply.
  5. Give it a Friendly name, choose Check every, and press Start monitoring.

A UDP check passes only when a reply comes back within the timeout, and contains your text if you set one.

More settings

Both kinds share the settings under More settings: Timeout (seconds) (default 10, from 1 to 30), Down when this many locations agree (default 2), Each of them after this many failed checks in a row (default 2), Check from, Alert when slower than (ms, optional), Repeat the down alert every (minutes, 0 = once) and Send a "back online" message when it recovers. How checks work explains how the cities vote.

Send a test

Open Alerts and press Send test on each channel to see that alerts reach you. Then open the monitor: after the first round, By location should show a time from each city.

When it does not work

  • Every city shows "Connection refused" or "Timed out". "Connection refused" means the server is there but nothing listens on that port. "Timed out" usually means a firewall drops the connection. Check that the service is running, that it listens on the public address and not only on 127.0.0.1, and that the firewall lets the port in.
  • "No UDP reply on port ...". Nothing came back. Make sure the packet is one the service answers. A test from your own computer with a tool for that service will tell you what it expects.
  • "Reply did not contain ...". A reply came back but did not include your text. The match is exact, including upper and lower case.
  • "A port is a number from 1 to 65535." The port field has something other than a number in it.
  • One city fails, the others pass. Usually a routing problem near that city. See A monitor says down but my site works.
← Ping monitor DNS monitor →

Still stuck? Email [email protected] and say which guide you were following.