Check the response your service should return
For HTTP and HTTPS monitors, set an expected status code or a keyword in the response. Configure the timeout between 1 and 30 seconds; new monitors default to 10 seconds. TCP monitors check whether a connection can be established to a public IP and port, without sending telnet commands.
Understand response times and confirmed failures
Review DNS, connection, TLS and response measurements alongside check history. Choose how many consecutive failures confirm an outage. Slow-response alerts are optional. A response timeout after connection is reported as excessive slowness, separately from a confirmed outage.
Match check frequency to your operation
Free includes 3 monitors with checks every 5 minutes. Starter includes 25 monitors and Pro includes 100, with checks from every minute. Intervals are approximate and depend on check duration and available capacity. Group services by project and select environments such as production or staging.