Port monitoring checks whether a specific TCP port on your server is open and accepting connections. A server can answer a ping while the service running on it has stopped responding. Port monitoring catches that gap by testing the port itself, so you know the actual service, your mail server, database, or SSH, is reachable and not just the machine.
What metrics are monitored?
A port monitor tracks:
- Port status: whether the port is open and accepting connections, or down
- Response time: how long the port takes to accept the connection
- Availability over time: uptime percentage and incident history
Checks run from multiple global locations, so a single regional network blip doesn't trigger a false alert. On paid plans you can also set slow-response alerts and recurring notifications.
Why use port monitoring?
Some of your most important services don't run on the web port. Email (SMTP, IMAP, POP3), databases (MySQL, PostgreSQL), SSH, FTP, and DNS each listen on their own port, and an HTTP or ping check won't tell you when one of them goes down. Port monitoring watches those services directly. If your SMTP port stops accepting connections, you find out before customers report that email isn't arriving.