Websites and APIs
Give us your site's address and we'll load it on a schedule. If it stops working, you'll hear about it in Discord.
The basics
Add a monitor, paste your site's address (starting with https://), and pick how often to check it. That's all most people need.
You can check every 5, 10, or 30 minutes straight away. To check every 1 or 3 minutes, first prove the site is yours (see below).
Optional settings
| Word to look for | A word or phrase that must be on the page. Useful when your site loads but shows an error. |
|---|---|
| Expected result | Which response codes count as working. The default, 200, means “loaded fine”. |
| Wait time | How long to wait for the page before counting it as down. |
| Failures before alerting | How many failed checks in a row before we call it down. Two by default, to avoid alerts for a single blip. |
| Headers | For APIs that need a key. We store it encrypted and never show it again. |
No false alarms
When a check fails, we check again 30 seconds later. If it fails again, we ask a second location to check too. Only if both agree do we mark your site as down.
Proving a site is yours
In project settings, add your domain. Then either add the DNS record we show you, or upload the small file we give you to your site. Once that's done, every monitor on that domain can check every minute.
Security certificates
For https:// sites, we warn you 14 days and 3 days before your certificate runs out.
If your firewall blocks us
Our checks identify themselves as Statusbeat-Monitor/1.0 (+https://statusbeat.app/bot). If your firewall or bot protection blocks that, every check will fail. More about our checks.