Documentation
Getting started
Create an account, enter a URL, and we start checking it immediately. No configuration required to begin.
Adding a monitor
A monitor needs a name and a URL. Everything else — check interval, expected status, timeouts — has a sensible default and can be changed under Advanced options.
Understanding uptime
Uptime is calculated as successful checks divided by total eligible checks in a time window (24 hours, 7, 30, or 90 days). Paused monitoring doesn't count as downtime.
Incidents
An incident is created automatically after a monitor fails a configurable number of consecutive checks (3, by default) — a single failed check never creates one. Incidents move through investigating, identified, monitoring, and resolved.
Status pages
A status page shows the live status of the services you choose, their uptime history, and public incident updates. Anyone with the link can view it; you control whether it's indexed by search engines.
Deleting a status page
Open Status pages and choose Delete on the page, or use the Danger zone at the bottom of its edit page. You confirm by typing the page's name. The public URL stops working immediately and the page no longer counts toward your plan. Your monitors and their history are not affected. Only organization owners and admins can delete status pages.
Notifications
Email alerts are sent when a monitor goes down, recovers, or its SSL certificate is close to expiring. Webhook delivery is also supported for connecting your own tools.
SSL monitoring
HTTPS monitors automatically track certificate expiration and alert at 30, 14, 7, and 3 days remaining — independently of whether the site is otherwise up.
API
A versioned REST API is available under /api/v1. Create an API key under Settings and send it as an Authorization: Bearer header to read monitors and incidents. Other endpoints, such as creating or changing monitors and status pages, require a signed-in session.
Troubleshooting
If a monitor shows a failure, open "View technical details" on the relevant check for the exact HTTP status or error code — the summary view intentionally stays in plain language.