Uptime Tracker runs each monitor on its own schedule, confirms any failure before calling it an outage, and only then opens an incident and sends alerts. A single failed check never pages you on its own.
Check intervals
Each monitor has a Check interval (seconds) between 15 and 3,600 seconds, limited by your plan's fastest interval:
| Plan | Fastest interval |
|---|---|
| Free | 300 seconds (5 minutes) |
| Starter | 60 seconds |
| Team | 30 seconds |
Each check also has a Timeout (seconds) between 1 and 30 seconds, at least 2 seconds shorter than the interval. Domain-expiry monitors are the exception: they run hourly from a cached registry answer.
How a failure is confirmed
When a check fails, the probe re-checks the target quickly before deciding anything. A monitor is marked down only after two consecutive failures. This filters out one-off network blips and short restarts that would otherwise wake you up for nothing.
Monitoring currently runs from one probe location. Additional probe regions are planned; once they exist, confirmations from other regions will also be required before a monitor is marked down.
How recovery works
A monitor that is down needs two consecutive successful checks before it counts as recovered. When that happens, the incident is resolved and a recovery notification goes to the same destinations.
What counts as a failure
- HTTP(S): a connection error, a timeout, an unexpected status code (by default anything outside 2xx/3xx), a missing keyword, or an invalid, expired, untrusted or wrong-hostname TLS certificate. Redirects are followed, up to 5 hops.
- TCP, ping, gRPC, SMTP, IMAP: the connection or handshake does not succeed within the timeout.
- DNS: the record does not resolve, or no answer contains the expected value.
- Heartbeat: no ping arrives within the expected interval plus the grace period.
Unknown results and platform errors
If a result is uncertain, for example because of a problem on our side rather than yours, the monitor shows unknown instead of a fake up or down. Probe and platform errors are not counted as your downtime, so they do not lower your availability figures.
How availability is calculated
Availability is time-weighted per monitor. Outages are backdated to the first failed check, not the moment confirmation finished, so the figures reflect real impact. Time inside a maintenance window is excluded from availability. Paused monitors do not count toward uptime or plan slots.
What an alert contains
Alerts include the monitor name, a redacted target (for HTTP monitors, only the host is shown) and the reason for the failure, so a message never leaks tokens from a URL's query string.
Frequently asked questions
Will one failed check send me an alert?
No. A monitor is marked down only after two consecutive failures, and only then are an incident and alerts created.
Do you check from multiple regions?
Not yet. Monitoring currently runs from one probe location, and additional probe regions are planned.
Why does my monitor show unknown?
Unknown means the result was uncertain, for example because of a probe or platform error. These periods are not counted as your downtime.
