Website Down Checker

Each region resolves the hostname's DNS, then makes a live HTTP GET request to the site and follows up to 5 redirects. Bare domains are checked over HTTPS first; if the HTTPS connection or TLS handshake fails, HTTP is tried once as a fallback and labeled explicitly — it's never silently substituted. A URL with an explicit http:// or https:// is checked exactly as entered, with no fallback.

Each region gives up after 10 seconds. A region that can't complete a check at all is reported as "check unavailable from this region" — that's distinct from the site actually being down, and it's excluded from the up/down count.

Region placement is approximate and best-effort, not a guarantee of the exact physical location a check ran from.

These checks run from datacenter networks, not residential connections — some sites deliberately block or challenge automated traffic like this, which shows up as "blocked automated check" rather than "down."

Results are cached for up to 60 seconds per site, so back-to-back checks of the same site may return an identical cached result rather than running fresh every time — this is always labeled on-screen.

User reports are anonymous "I'm having problems too" clicks from other visitors, deduplicated per visitor for 15 minutes so one person can't inflate the count, shown as a rolling 24-hour history. They're a crowd signal, not a verified measurement.

Scope: this checks HTTP(S) reachability of the site's origin only — not a specific page, not APIs on other ports, and not regional CDN cache health.