Uptime Monitoring

A background worker checks each of your websites on its own schedule, records the result, and alerts you when its state changes.

Monitor settings

Setting	Range	Default	Description
URL	http / https	n/a	The address to check.
Method	GET, HEAD, POST	GET	HTTP method used for the check.
Check interval	10 – 86400 s	60	Time between checks.
Timeout	1 – 60 s	10	A request slower than this counts as a failure. Cannot exceed the interval.
Expected status	100 – 599	200	Any other status code counts as a failure.
Keyword	optional	none	Text that must appear in the response body (not used with HEAD).
Failure threshold	1 – 10	2	Consecutive failures before the site is marked DOWN.

Status	Meaning
`PENDING`	Created or resumed, waiting for the first result.
`UP`	The last check passed.
`DOWN`	The failure threshold was reached.
`PAUSED`	Checks are stopped.

A check fails. The failure counter increases, but the status stays the same until the threshold is reached. This avoids alerts for one-off blips.
When the counter reaches the threshold the monitor becomes DOWN, an incident opens, and a [internal] down alert is sent.
When a check passes again the monitor becomes UP, the incident is resolved with its duration, and a recovery alert is sent.

Pausing a monitor ends any ongoing incident without sending a recovery alert.

Redirects are followed (up to 5) unless your expected status is itself a redirect code. Redirects to private or internal addresses are blocked.

On Settings you can reduce noise:

Cooldown: suppress a new down alert for a monitor if it already alerted within the last N minutes. Useful for flapping sites.
Mute schedule: hours (UTC) during which internal alerts are not delivered. They are still recorded in your feed as Muted.

By default, localhost and private IP ranges cannot be monitored. This protects the server from being used to probe internal networks.