TCP port monitoring for services that are not just web pages

UptimeSure can open a TCP connection to a configured host and port and record whether that connection succeeds before the timeout. This is useful for service reachability without pretending to validate the application protocol running on top.

A TCP monitor attempts a network connection to one host and one port. The legacy `ping` monitor in V1 is also TCP Reachability and is not ICMP echo.

Connection refusal, timeout, DNS/network failure or target-policy rejection produces a failed check.

Confirmed failures create incidents and recoveries close them. The dashboard and monitor detail show the service’s current state and recent checks.

What UptimeSure checks

TCP connection establishment
Port bounds
Timeout
Connection latency/error

Common use cases

Database listener reachability
SMTP/IMAP service ports
SSH bastion availability
Custom TCP daemons

Configuration

Host
Port
Interval
Timeout
Confirmation threshold

Alerts and recovery

All normal alert-channel types can be linked to a TCP monitor, with optional delay and recovery delivery.

Example

Example: attempt a TCP connection to db.example.com:5432 every five minutes and confirm DOWN after two failed attempts.

Frequently asked questions

Is TCP Reachability ICMP ping?

No. UptimeSure V1 does not claim ICMP monitoring.

Does a successful connect prove the application is healthy?

No. It proves the TCP service accepted a connection; use an HTTP/API monitor when application-level response validation is required.

Can private addresses be monitored?

Private/reserved targets are blocked by default for safety unless the deployment operator deliberately enables private targets.

Explore UptimeSure

Start monitoring

Open UptimeSure