Is Website Down?

    Check if a website is down for everyone or just you. Enter a URL below to verify its status.

    How Does This Tool Work?

    Our website down checker performs multiple tests to determine if a website is accessible. We first verify the domain's DNS records exist, then attempt to connect to the website's server to confirm it's responding to requests.

    This helps you quickly determine whether a website issue is on your end (local network, ISP, or device) or if the website is actually experiencing problems that affect everyone.

    Why Websites Go Down

    Server Issues

    Web servers can crash due to hardware failures, software bugs, or being overwhelmed by too many visitors at once.

    Network Problems

    Issues with internet infrastructure, routing problems, or DDoS attacks can make websites unreachable.

    Maintenance

    Websites often go offline temporarily for scheduled maintenance, updates, or security patches.

    DNS Issues

    Problems with domain name servers can prevent your browser from finding the website's server address.

    What To Do If A Website Is Down

    • Wait and retry - Many outages are temporary. Try again in a few minutes.
    • Clear your browser cache - Sometimes cached data can cause loading issues.
    • Try a different browser or device - This helps determine if the issue is on your end.
    • Check social media - Many companies post updates about outages on Twitter/X or their status pages.
    • Use a VPN - If the site is blocked in your region, a VPN might help access it.

    In-depth guide

    When a website seems unreachable, the first question is always: is it down for everyone, or just for me? A server-side check answers that in a few seconds. Our tool issues an HTTP request from our infrastructure — not your browser — and reports the actual response code, response time, and reachability. If we can reach the site and you can't, the problem is between you and the site (your network, ISP, DNS, or VPN). If we can't reach it either, the site itself is down.

    Why the check has to come from a different network

    Outages have many causes that look identical from your browser: a misconfigured local DNS, a captive portal, an ISP routing problem, a corporate firewall blocking the domain, a stale browser cache, a Cloudflare edge node failing in your region, or an actual origin server crash. Running the request from an independent network eliminates the first five from suspicion. If a third-party check succeeds, you know the site is up and the fault is local; if it fails, the outage is real.

    How to read the response

    A 200-range response (200, 204, 206) means the site is up and serving content. A 301 or 302 means the site is alive but redirecting — usually to HTTPS or a regional variant. A 403 means the site is up but refusing the request, often because of bot protection. A 404 at the domain root usually means the site isn't configured correctly at the host. A 500-range response (500, 502, 503, 504) means the site is partially up — the network layer is working but the application is failing. A timeout (no response at all) usually points to a DNS failure, a firewall drop, or a fully offline server.

    If only you are affected

    When the site is up for the world but not for you, the fastest fixes in order: flush your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS); try a different DNS resolver (1.1.1.1 or 8.8.8.8 instead of your ISP's default); try the site over a mobile hotspot to bypass your home or office network; disable any VPN or browser extension that might be intercepting traffic; clear browser cache and try an incognito window. If those don't help, the problem is probably an ISP routing issue on the path between you and the site — out of your control, usually resolved within an hour.

    Frequently asked questions