Down for everyone, or just for you?

Our server requests your homepage the way a visitor's browser would, from a neutral network that isn't your office wifi or your phone. We time the response, read the status code, and classify failures by type — DNS, connection refused, timeout, certificate, or server error. Hard failures get checked twice before we call an outage, because one dropped packet shouldn't send you into crisis mode.

Good news, mostly: the site is serving fine and the problem is local to your device or network. Usual suspects: your router's DNS cache, a corporate firewall, a VPN, or a recent DNS change still propagating to your region. Try another network and a private window. If specific customers report the same thing for more than a day, it's worth a proper look.

Note the failure type — it points at the fix. Server errors mean the machine is up but the site is broken (code or database). DNS failures mean the domain itself isn't resolving (check registration and nameservers). Refused connections and timeouts usually mean the host. Then either call your host with those specifics, or hand it to us: emergency repair exists for exactly this hour.

The honest census: expired domains and certificates (calendar problems), botched updates (change problems), resource exhaustion under traffic (capacity problems), and host outages (their problems). Almost none of it is random — which is why the failure type matters more than the fact of the outage. We wrote a whole guide on the checks that catch these before customers do.

Really free, no email required. A down checker you have to sign up for is useless in the exact moment you need it. If your site turns out to be down and you want it fixed, you know where the emergency lane is — that's the entire business model, out loud.