All features
TCP port monitoring

TCP port monitoring for everything that isn't a website

Databases, mail servers, game servers and message brokers don't serve web pages. A TCP check opens a connection to the host and port and tells you the moment it's refused or times out.

Any service, any port

PostgreSQL on 5432, SMTP on 25, Redis on 6379, or your own service on any port from 1 to 65535.

Connection time tracked

See how long each connection takes on the monitor's response-time chart.

Safe by design

Checks can't be pointed at private or internal network addresses, so the feature can't be used to probe your internal network.

See it in Spot Downtime

The real app, with a demo team's monitors. Included on every plan, Free too.

A TCP port monitor for a Postgres database with connection times
A database port, checked every minute, with how long each connection took.

What is TCP port monitoring?

Much of what keeps a product running isn't a web page. Databases, mail servers, caches, message brokers, SSH and game servers all listen on a TCP port. A TCP port monitor opens a connection to that host and port on a schedule. If the connection is refused, times out or the host can't be found, the monitor goes down and your team is alerted.

It works with any service that accepts TCP connections, on any port from 1 to 65535, with no agent to install and no credentials to share.

What a port check tells you, and what it doesn't

A successful connection proves the service is running, listening and reachable through your firewall. That catches crashed processes, servers that didn't come back after a reboot, broken firewall rules and DNS records pointing to the wrong machine.

It doesn't log in or run a query, so it can't tell you a database is returning wrong data. For services with an HTTP health endpoint, add an API monitor with assertions next to the port check.

Common ports to monitor

PostgreSQL on 5432, MySQL on 3306, Redis on 6379, MongoDB on 27017, SMTP on 25 or 587, IMAP on 993, RabbitMQ on 5672 and SSH on 22 are the usual candidates. Each check records how long the connection took, so the chart also shows when a service starts slowing down.

Checks come from the public internet and private addresses are blocked, so the service must be reachable from outside. If you restrict access by IP address, allow Spot Downtime's published checker addresses.

How to set it up

  1. 1Click Add monitor and choose TCP port.
  2. 2Enter the host and port, like db.example.com:5432.
  3. 3Pick how often to check and save.

The details

Counts as up
The TCP connection opens within 10 seconds
Counts as down
Refused, timed out, host not found, or a private or reserved address
Ports
1–65535
Plan
All plans, including Free

Questions

Does it log in to my database?
No. It only opens and closes a connection, so it needs no credentials and sends no data.
Can I check a server on my private network?
No. Checks run from the public internet and private addresses are blocked. The service must be reachable from outside.

Set up TCP port monitoring in under a minute

Included on the Free plan. No card needed.

Create a free account