Not every service speaks HTTP. Mail servers, databases, game servers, SSH and countless custom applications listen on their own TCP ports. Port monitoring confirms that the service is actually accepting connections — not just that the machine is online.
Uppinger opens a TCP connection to the port you specify on a schedule. If the port stops accepting connections, the service has likely crashed or been firewalled, and you get an alert.
How Port Monitoring works
Add host and port
Enter the hostname or IP and the TCP port number you want to watch (for example 25, 443, 5432, 22).
We test the connection
Uppinger attempts a TCP handshake on the port at your chosen interval.
Detect service failures
A refused or timed-out connection means the service is down, even if the server still pings.
Instant alerts
You are notified by email, SMS, Slack or Telegram the moment the port stops responding.
Why use Uppinger for port monitoring
- ✓Monitor SMTP, IMAP, databases, SSH, game servers and custom ports
- ✓Detects crashed services that still leave the server online
- ✓Catches firewall and configuration mistakes
- ✓Multi-location checks for reliable results
- ✓Alerts via email, SMS, Slack and Telegram
Frequently asked questions
What is TCP port monitoring?
Port monitoring opens a TCP connection to a specific port on a host to confirm that the service listening on that port is accepting connections.
Which ports can I monitor?
Any TCP port — common examples are 25 and 587 for mail, 5432 for PostgreSQL, 3306 for MySQL, 22 for SSH, and any custom application port.
Why not just use ping?
Ping only confirms the server is reachable. Port monitoring confirms the specific service is actually running and accepting connections.
Other monitor types
Start port monitoring for free
No credit card required. Set up your first monitor in under 60 seconds.
Start Free Monitoring