Monitor any specific port on your server.

Make sure any service on your server is still available with the Port monitoring.

Start monitoring for free
Port monitoring hero
GitHub logo
Slack logo
Gitlab logo
n8n logo
Canva logo
 OVHcloud logo
Akamai logo
rmit-logo
Atlassian logo
Intel logo
Electronic Arts (EA) logo
IBM logo
Adyen logo
Stanford University logo
BBC logo
Moody's logo
Siemens logo

Monitor any port on your server.

Make sure databases and other services running on different ports on your server are always available. We support any port, including HTTPS, FTP, SSH, ...

Monitor any port on your server

Make sure your email service
runs smoothly.

Set up a POP3, IMAP and SMTP port monitoring and know about any issues with your essential email services.

Make sure your email service
runs smoothly

Port monitoring for your DNS server.

With port monitor watching your DNS port you always know whether essential DNS connection is okay.

Port monitoring for your DNS server

Choose your preferred type of notifications.

Get instant alerts via email, SMS, voice call or through one of many integrations (such as Slack, Zapier, Splunk, etc.)

Choose your preferred type of notifications

Easy setup: 3 clicks to create

a port monitoring.

Be the first who knows that your website is down. Reliable monitoring warns you before any significant troubles and saves you money.

Advanced features for advanced users.

Recurring notifications

Set threshold and recurrence parameters so that you don't miss any serious outage.

Maintenance windows

Set up maintenance windows to pause the monitoring during the maintenance.

Multi-location checks

Create monitors with specific monitoring regions you can choose and catch issues that only appear in specific locations.

SMS and voice call notifications

No internet? We can call or text you when something goes wrong.

Know more than

just up or down.

Multi-location checks, response time tracking, SSL and domain expiry alerts. The details that turn raw uptime data into something you can actually act on.

All you really care about 

monitored in one place.

From Websites and APIs to servers and cron jobs, UptimeRobot watches every layer. Nine monitor types, one dashboard.

Build trust with

public status pages.

Be transparent. Share your uptime with the public and inform your customers about any planned (or unplanned) outages.

Status page
Add your team members
to keep them notified

Add your team members

to keep them notified.

You can invite all your team members to access your monitors, keep them notified and manage incidents. Choose from three levels of user access: read, write and notify-only.

What users love about

our keyword monitoring.

Get inspired by

the uses cases.

Improved network security by keeping an eye on open ports

Tracking status and performance of network devices

Enhanced troubleshooting and reduced incident response time

We strive for minimal downtime, but if something goes wrong UptimeRobot makes sure that we know about it quickly.

We switched to using UptimeRobot years ago as they offered the same services we were getting from a different provider but at a fraction of the cost.

4everproxy logo

Frequently asked questions.

Port monitoring checks whether a specific TCP port on a server is open and accepting connections. UptimeRobot attempts to connect to the port you specify, and if the connection succeeds, the service is marked as up. If the connection fails or times out, you receive an alert.

Unlike a basic ping check, port monitoring verifies that the actual service behind the port is available, not just that the server itself is online.

UptimeRobot supports monitoring any TCP port, including standard ports for web servers, email services, databases, DNS, SSH, FTP, and custom applications.

Common examples include:

  • 80 and 443 for HTTP and HTTPS
  • 22 for SSH
  • 25, 465, and 587 for SMTP
  • 3306 for MySQL
  • 5432 for PostgreSQL

If your service uses a non-standard port, you can enter any custom TCP port manually when creating the monitor.

Port monitoring checks whether a specific service is accepting TCP connections on a given port. Ping monitoring checks whether the server itself is reachable over the network using ICMP.

A server can still respond to ping requests while services like SSH, databases, or mail servers are down. Port monitoring goes one step further by verifying that the actual service behind the port is running and accessible.

For broader visibility, many teams use both ping and port monitoring together.

Monitor any service your users, applications, or infrastructure depend on. Common examples include:

  • Web servers on ports 80 and 443
  • SSH on port 22
  • SMTP, IMAP, and POP3 email services
  • Databases like MySQL and PostgreSQL
  • DNS services on port 53

Port monitoring detects when a service stops accepting connections, even if the server itself is still online.

Yes, port monitoring is a reliable way to monitor mail server availability. UptimeRobot supports SMTP (25, 465, 587), IMAP (143, 993), and POP3 (110, 995) ports.

If any of those services stops accepting connections, you receive an alert immediately. Email issues often go unnoticed longer than website outages, so monitoring mail ports directly helps catch problems earlier.

To create a port monitor in UptimeRobot, enter the hostname or IP address of your server, specify the TCP port you want to check, and choose how often the monitor should run.

You can also configure alert integrations like email, Slack, Microsoft Teams, SMS, or PagerDuty notifications. When the monitor is saved, UptimeRobot starts checking the port automatically and alerts you if the service stops accepting connections.

Yes, UptimeRobot includes free port monitoring with automatic uptime checks, response time tracking, and email alerts.

Paid plans add faster monitoring intervals, more monitors, and additional notification integrations like Slack, Microsoft Teams, SMS, voice calls, and PagerDuty alerts.

Yes, each port monitor checks one specific server and TCP port combination, so monitoring multiple ports on the same server requires separate monitors.

For instance, you can monitor HTTPS on port 443, SSH on port 22, and MySQL on port 3306 at the same time. Each monitor runs independently and sends alerts separately, making it easier to identify which service is affected.

Relevant articles.

Top 10 Port Monitoring Tools

Top 10 Port Monitoring Tools

Looking for the best cost-effective port monitoring that meets all your needs? Read our detailed guide focusing on key features and pricing.

Read more
Server Administrator’s Guide to POP3 and IMAP Monitoring

Server Administrator’s Guide to POP3 and IMAP Monitoring

Monitor key mail server ports like POP3 and IMAP to enhance uptime and reduce costs. Discover essential monitoring tips.

Read more
SMTP Monitoring Uncovered

SMTP Monitoring Uncovered

Why is SMTP monitoring important and key to maintaining secure and uninterrupted email services? Learn about the whole story on our blog.

Read more
4.7
stars out of 5
284+ reviews on

Get your FREE account now, 50 monitors included!

No credit card required!

Available also on: