What a website monitor checks
Each check requests your URL exactly like a browser would: it follows redirects, validates the HTTPS certificate and measures how long the response takes. You choose which status codes count as healthy, whether a phrase must be present on the page, and how many failed checks it takes before an alert is sent.
The result of every check is stored, so you get response-time graphs, 30 to 365 days of uptime history and a monthly uptime percentage you can share with clients.
- Status code validation (2xx by default, any range you choose)
- Keyword must or must not appear on the page
- Response-time threshold alerts on Pro
- SSL certificate and domain expiry warnings 30, 7 and 1 day ahead
- Custom headers, basic auth and POST bodies for logged-in pages
How fast you know
Free monitors run every 5 minutes. Pro and Team check every 60 seconds, or every 30 seconds if you enable it. A failed check is retried before the alert goes out, so a single network hiccup does not wake you up, but a real outage reaches you within one to two minutes.
Where the alert goes
Email, Telegram, Slack, Discord, Microsoft Teams, PagerDuty, Opsgenie and webhooks are included. Send different monitors to different channels, silence alerts during maintenance windows and escalate to a second person if nobody reacts.
Hosted in the EU
Checks run from Frankfurt and all data stays in EU data centres. That matters if your customers, or your legal department, ask where monitoring data goes.