Documentation
Troubleshooting
Common questions when something does not look right.
- Getting started
Getting started
Help
Troubleshooting
Common questions when something does not look right.
My site is up but the monitor says down
- Check the error on the monitor page: a 403 or 429 usually means a firewall, WAF or rate limiter is blocking our IPs. See Allowlisting.
- Expected status codes: endpoints behind authentication return 401 or 403 by design; add that code to the expected list or configure auth on the monitor.
- Timeouts: increase the timeout if the page is legitimately slow, or fix the slow dependency.
- Keyword monitors are case-insensitive but exact: make sure the text appears in the raw HTML, not only after JavaScript runs.
I am not receiving alerts
- Open Alert contacts and send a test. The delivery status tells you whether the channel works.
- Confirm the contact is attached to the monitor.
- Check Down alerts only is not hiding recovery messages, and that a maintenance window is not active.
- Look in spam for the first email from [email protected] and mark it as safe.
Uptime percentage looks wrong
Uptime is calculated from checks, excluding maintenance windows. A brief outage of one check counts as downtime for that check's share of the period, so a 5-minute monitor shows a bigger dip for the same incident than a 30-second one.
Status page custom domain shows an error
Verify the CNAME points exactly at monitermysite.com and that no proxy in front of it rewrites the Host header. DNS changes can take up to 24 hours to propagate.
Still stuck?
Email [email protected] with the monitor name and the time of the issue. Growth and Summit plans get priority support.
Didn’t find what you need?
We answer every email, usually within one business day.