Account

What new tool do you want?

Web & SEO

Is It Down? Website Down Checker

Check if a website is down for everyone or just you — status code, response time and a plain-English explanation of what's wrong.

How to use

  1. 1Enter the website.
  2. 2See whether it responds from our server, with the status and response time.
  3. 3If it's up for us but not for you, follow the tips to fix your connection.

Frequently asked questions

It's up here but I still can't open it — why?

The problem is between you and the site: your Wi-Fi, DNS cache, ISP, VPN, firewall or browser cache. Try another network or browser.

What does a 503 mean?

The site is temporarily unavailable — usually maintenance or overload.

Where is the check made from?

From our server in the United States, with a 15-second limit.

Why 'down for me' and 'down for everyone' need different checks entirely

When a site won't load, the problem sits somewhere on a long chain — your device, your Wi-Fi, your ISP's DNS, a VPN, or the actual server — and a frustrated user has no easy way to tell which link in that chain broke without a second vantage point. This tool provides exactly that second vantage point: a request made from an independent server, so a result showing the site responding normally tells you with real confidence that the problem is somewhere between you and the site, not with the site itself.

Worked example: Is It Down? Website Down Checker

A site that returns a 200 status from this tool's US-based server but won't load in your own browser points the troubleshooting squarely at your side of the connection — worth trying a different network (phone hotspot instead of home Wi-Fi), clearing DNS cache, or disabling a VPN, each of which are the FAQ's suggested next steps, rather than assuming the site itself is broken and waiting for someone else to fix it. A result showing a 503 status instead means the server itself reported it's temporarily unable to handle the request — commonly deliberate (planned maintenance) or overload (a traffic spike exceeding the server's capacity) rather than a hard crash.

Why one check from one location has real limits

A single check from one US-based server with a 15-second timeout, as this tool's own FAQ states, confirms reachability from that one specific vantage point — it can't rule out a regional outage affecting only users in a different part of the world, or a CDN edge node failure that happens to not affect the specific route this check takes. A truly global, continuously-monitored uptime service checking from many locations is the right tool for mission-critical monitoring; this is built for the much more common 'is it just me right now' question.

Why the 15-second timeout itself is a meaningful data point

A request that never completes within 15 seconds is reported differently from one that comes back with an error status, and that distinction matters: a fast error response (like an immediate 500) usually means the server is up and actively rejecting or failing the request, while a hard timeout with no response at all more often points to a server that's completely overwhelmed, a DNS resolution failure, or a network path that's dropping packets before reaching the destination at all. Treating 'timed out' and 'errored' as the same outcome would hide which of those two very different failure modes is actually happening.

A worked example: diagnosing a DNS-only problem

If this tool reports a site responding normally with a 200 status, but your own browser shows a 'DNS_PROBE_FINISHED' or similar resolution error, the fault is isolated specifically to DNS on your side — your device or network literally cannot translate the domain name into an IP address, even though the server behind that address is working fine. Flushing your local DNS cache or switching to a public resolver like 1.1.1.1 or 8.8.8.8 typically resolves exactly this scenario, which is a different fix from the broader 'try another network or browser' advice needed for a more general connectivity problem.

Related tools

More: Web & SEO