Methodology
How we decide whether a website is up or down.
A live check, not a cached one
Every time you open a status page, we send a fresh HTTP request to that domain right then — we don't show you a cached result from an hour ago. The response code and response time you see reflect what the server did at that exact moment.
How we classify the result
- No response(DNS failed or the connection timed out) — shown as "couldn't locate this website."
- 2xx / 3xx, or 405 — the server answered normally. Shown as UP.
- 429 (rate-limited) — the server is reachable and actively responding, just throttling automated requests like ours. Shown as UP, not down.
- 4xx — the server is reachable but this specific page returned an error (e.g. a dead link). Shown as Up — returns error, not a flat "Down," because a reachable server with a broken page is a different problem than an outage.
- 5xx — the server itself is failing to handle the request. Shown as Down — server error.
We treat the distinction between "unreachable," "reachable but erroring," and "genuinely down" as important — collapsing every non-200 response into a single red "Down" badge, like some checkers do, mislabels sites that are actually up and simply returned an error page.
User reports add context, not the verdict
The live check above is what determines a site's status. User reports and comments run alongside it — they're useful for catching problems that a plain HTTP check can't see (a page that loads but is broken, a login that silently fails, a feature that's misbehaving for real users) and for giving early signal before a status check reflects it. But we don't infer "down" purely from report volume — the badge you see is always backed by an actual request to the server, not just how many people complained.
No bot throttling against the sites we check
Checks run one at a time, triggered by real visits to a status page — we don't run background sweeps that hammer thousands of domains at once. If a site rate-limits our request (429), we report it as up, not down, since that's a sign the server is working.