Documentation
How can we help?
Guides for setting up monitors, getting the right people alerted and keeping your users informed, plus answers when something looks wrong.
Where should I start?
- Step 1
Start monitoring in five minutes
Watch your first URL, get an email when it breaks, and confirm both work before you walk away. - Step 2
Add a monitor
Watch a website or API endpoint and learn within minutes when it goes down, slows down or serves the wrong page. - Step 3
Choose who gets alerted
Send outage notices to the right inbox, Slack or Discord channel, PagerDuty service or webhook, and control how often they repeat. - Step 4
Publish a status page
Give your customers one public address that shows whether your services are up, so they stop asking support. - Step 5
Inviting Team Members
Invite new members to your team via email. Manage pending invitations and control access to your monitoring.
Browse by section
Getting Started
Your first monitor and alert, in five minutes.1 pageGuides
Step-by-step tasks: monitors, alerts, status pages, cron jobs and flows.6 pagesFix a problem
What to check when alerts, checks or cron jobs don't behave as expected.4 pagesConcepts
How each monitor type, alerts, status pages, maintenance and reports work.10 pagesTeam & Settings
Members and roles, invites, verified domains and API keys.4 pagesAPI Reference
Authenticate, page through results, and handle errors and rate limits.6 pagesAPI Resources
Every endpoint, with its fields, scopes and examples.14 pages