ICMP ping checks verify that a host is reachable on the network. Beacony sends a ping to your server's IP or hostname and measures round-trip time. If the host stops responding, you get alerted immediately.
TCP port checks verify that a specific port is open and accepting connections. Useful for services that don't expose an HTTP endpoint — databases, SSH servers, SMTP relays, game servers, and more.
Verify SSH access is available on your servers
Check your mail server is accepting connections
Monitor database port availability
Ensure your Postgres instance is reachable
Track Redis port health alongside your app
Monitor any custom port for game or media servers
Ping (ICMP) checks whether a host is reachable at the network layer — it tells you the machine is alive. Port monitoring checks whether a specific TCP port is open and accepting connections — a host can respond to ping while a service like MySQL or SSH is down. Use both together for full server monitoring coverage.
No. Beacony checks from cloud infrastructure and cannot reach private IP ranges (10.x, 192.168.x, 172.16.x). For monitoring internal background jobs or workers, use Heartbeat monitoring instead — your job pings a unique Beacony URL to confirm it ran.
Checks run at your configured interval, from every 30 seconds up to every 24 hours. Beacony requires consecutive failures before opening an incident to avoid false alerts. Once confirmed, your alert arrives in under 60 seconds.
TCP port monitoring is supported for any port from 1 to 65535 — databases (MySQL :3306, Postgres :5432, Redis :6379), mail servers (SMTP :25/:587), SSH (:22), and custom ports. ICMP is used for ping. HTTP/HTTPS endpoints have a dedicated monitor type with status code and content checks.