Monitor any TCP port on your servers 24/7. Verify that databases, mail servers, and custom services are accepting connections and responding properly.
TCP port monitoring is the process of continuously checking whether a specific TCP port on a server is open, accepting connections, and responding within an acceptable timeframe. Every network service - from web servers and databases to email systems and caching layers - listens on a specific TCP port. When that port becomes unreachable, the service is effectively offline, even if the underlying server hardware is still running.
Traditional website monitoring only checks HTTP and HTTPS endpoints, which covers web servers but leaves your entire backend infrastructure unmonitored. Your database server could crash, your Redis cache could stop responding, your SMTP mail server could reject connections - and a basic website uptime monitor would never detect these failures. TCP port monitoring fills this critical gap by checking the actual ports where your services listen for connections.
UptimeMonitorX's TCP port monitoring works by establishing a real TCP connection to the specified host and port at your chosen interval. If the connection succeeds and completes within the configured timeout, the service is marked as up. If the connection is refused, times out, or the host is unreachable, UptimeMonitorX immediately sends an alert through all your configured notification channels. This approach catches not only complete server failures but also service-level crashes, firewall changes, and network routing issues.
Monitor any TCP port on any publicly accessible server. Whether it is a MySQL database on port 3306, PostgreSQL on 5432, MongoDB on 27017, SMTP mail on port 25 or 587, FTP on port 21, SSH on port 22, or a custom application running on a non-standard port - UptimeMonitorX checks it all around the clock.
UptimeMonitorX establishes a real TCP connection to your specified host and port to verify that the service is not only running but actively accepting connections. This goes beyond a simple ping - it confirms that the actual service bound to that port is responsive and functional.
Set connection timeout thresholds per monitor to match the expected behavior of each service. Fast services like Redis caches might warrant a 5-second timeout, while heavier database connections might need 15 seconds or more. You control the sensitivity of each monitor.
Track TCP connection establishment times with millisecond precision over time. Monitor trends in connection latency to identify network degradation, server load issues, or infrastructure problems before they escalate into full outages affecting your users.
Receive instant notifications via 17+ channels including Email, Slack, Discord, Telegram, MS Teams, PagerDuty, Google Chat, Twilio SMS & more the moment a monitored TCP port becomes unreachable. Configure multiple notification channels per monitor for redundancy so critical alerts always reach the right team member.
Maintain a complete incident history for every monitored port with precise downtime start time, duration, and recovery timestamp. Use historical incident data to identify patterns, correlate failures across services, and improve your infrastructure reliability.
Choose monitoring intervals from every 1 minute to every 60 minutes based on the criticality of each service. Mission-critical database servers can be checked every minute, while less critical background services might only need checks every 15 or 30 minutes.
Generate detailed SLA compliance reports for your TCP-monitored services showing uptime percentages, incident counts, total downtime duration, and response time trends. Share these reports with clients, management, or compliance teams as proof of service reliability.
You can monitor any valid TCP port from 1 to 65535. Common examples include port 3306 (MySQL), 5432 (PostgreSQL), 27017 (MongoDB), 6379 (Redis), 22 (SSH), 21 (FTP), 25 (SMTP), 587 (SMTP TLS), 143 (IMAP), and any custom port your application uses.
No. UptimeMonitorX performs TCP checks externally over the internet. There is no agent, daemon, or software to install on your servers. The only requirement is that the port is reachable from the public internet - meaning it should not be blocked by a firewall for external access.
Ping monitoring checks whether the server itself is reachable at the network level using ICMP packets. TCP port monitoring goes deeper - it checks whether a specific service running on a particular port is accepting connections. A server can be pingable but have a crashed database service, which TCP monitoring would catch but ping monitoring would not.
Free plan includes 5 monitors. No credit card required - set up in seconds.
Get Started Free