Skip to content

Docs

Checks & monitors

Four check types, each verifying a different kind of failure. Add one from the dashboard's Add check form, or through the REST API.

HTTP

Requests a URL and evaluates the response: a healthy status code counts as up, a timeout or a server error counts as down. Runs from RealUptime's own cloud probes, so it can only reach targets that are reachable from the public internet. Use the Monitor agent instead for anything behind a firewall.

TCP

Opens a connection to a host and port and confirms it accepts one, the right check for a database, a cache, or any service that speaks its own protocol rather than HTTP. Can also complete a TLS handshake and track the certificate's expiry, warning you before it lapses. See TCP checks for the full detail.

DNS

Resolves a hostname and confirms the record still exists, optionally checking it against an expected value. Leave the expected value blank to alert only when the record stops resolving entirely, or set it to also catch a record that still resolves but no longer points where it should, a repointed record that looks healthy to every other kind of check.

Heartbeat

The inverse of the other three: instead of RealUptime reaching out, your job checks in with RealUptime on its own schedule. Built for cron jobs, backup scripts, and queue workers that run on a schedule rather than serving requests. See heartbeat monitors for the ping contract, arming, and the grace period.

Intervals

HTTP, TCP, and DNS checks run every 60 seconds from each region you select. Heartbeat monitors run on whatever interval your job dictates, from 60 seconds up to 24 hours, plus a grace period you set for extra slack past the interval before a late ping counts as down.

Regions

RealUptime's cloud probes check from four regions: US-East, US-West, Europe, and Asia-Pacific. Pick which of the four probe an HTTP, TCP, or DNS check when you create it, all four by default, and change the selection later from the check's own settings. A heartbeat check has no region: nothing reaches out for it, so there is nothing to select. The Monitor agent has its own region too, wherever you run it, alongside the four cloud regions on any check it is bound to.