InfoFounding Members35 lifetime licenses available — view the offer > https://uptriva.com/foundingInfoMCP launch announcementConnect Claude, Cursor or any MCP client with your API token — let an agent create monitors, manage incidents and configure alerts. Read the docs → https://uptriva.com/docs/api/mcp
All check types
Network & Protocols

TCP Port Monitoring

TCP monitoring opens a real connection to host:port on every interval and measures handshake time. If it speaks TCP — databases, mail relays, game servers, custom protocols — this check covers it.

Any port, any protocol — answer the only question that matters

What it checks

  • TCP connect success and handshake latency
  • Port availability on any reachable host
  • Firewall or listener failures at connection time

Set it up

  1. 1Add a TCP monitor with host and port
  2. 2Tune failure thresholds for flapping services
  3. 3Escalate through your on-call chain

FAQ

What is the difference between TCP and HTTP checks?

TCP proves the port accepts connections; HTTP proves the application layer responds correctly. A wedged service can pass TCP while failing HTTP — use both on critical paths.

Related check types

Ping MonitoringRaw reachability with real ICMP — not a TCP shortcutUDP MonitoringThe protocol nobody monitors until DNS or a game port diesDNS MonitoringYour site can be up while nobody can resolve it

Start monitoring in minutes

External probes plus internal agents, escalation chains and status pages — free tier, no card required.

Start free Read the docs