How we avoid false alerts
The fastest way to lose a client's trust is to tell them their site is down when it isn't. For an agency, a false alarm is worse than a missed one — it's the reason people stop believing their monitoring. So accuracy isn't a feature here; it's the whole point.
A single failed check is never enough. We only send a "site down" alert after 2 consecutive failed checks, so a momentary network blip on our side — or a one-second hiccup on the host — never pages you or your client. A real outage still alerts on the very next check.
If you deploy our free edge probes, a site is marked down only when at least two regions agree. One region losing its route to your host doesn't become a false alarm — the other regions have to see it too.
When a data source can't give a trustworthy answer, we say so instead of guessing. Low-traffic sites simply show no real-user speed data rather than a fabricated number; checks that can't be verified cleanly are dropped, not reported as a scary red result. No false positives by construction.
Deploying or doing maintenance? Mute a site for 1, 4, or 24 hours. Checks keep running and recording — only the alerts are paused — and the mute auto-expires, so a site that's genuinely still down afterward alerts normally. Expected changes don't cry wolf.
When several things break on a site at once, we group them into a single notification per site per run — so an incident is one clear, useful message, not an inbox flood that trains you to ignore alerts.
Sitefolio itself scores an A on our own security-headers checker. We run our product on our own site — if a check would embarrass us, we fix the check.
Try the checks yourself
Every claim above is something you can verify. Run a free check, then decide.
Start free → — add a site and see monitoring you can actually forward to a client.