Uptime
Website Down Checker
Find out whether a site is down for everyone or just for you — and if it is answering, what it actually returned.
What This Tool Does
This tool requests the site from our own infrastructure and reports exactly what came back: whether a connection could be made, the HTTP status code, and how long the response took.
Because the request comes from our network rather than yours, the result is independent of your connection, your DNS resolver, your ISP and your browser. That is the entire point. “It does not load for me” and “it is down” are different claims, and telling someone to contact their host when the real problem is their own DNS cache wastes everybody’s afternoon.
Requests currently come from a single location rather than several regions. That is enough to tell a genuine outage apart from a problem on your own connection, which is the main question — but it cannot yet distinguish a regional outage from a global one. Every result says which kind of measurement produced it.
How to Read Your Results
Reachable
Whether a connection could be established and a response received at all. This is the headline answer. A failure here means the server did not respond — it may be off, overloaded, or blocked by a firewall.
HTTP status
What the server said. This is where “down” usually gets more precise.
- 200 — the server returned a normal page.
- 301 or 302 — the URL redirects. The site is up; trace the chain with the Redirect Checker if it ends somewhere unexpected.
- 403 — access refused. Often a firewall or security service blocking automated requests rather than an outage.
- 404 — that specific page does not exist, but the server is fine. Check the URL.
- 500, 502, 503, 504 — the server is running but failed to produce a page. An application problem, not a hosting outage.
Outage scope
Whether failures are global or limited to some locations. A regional split points at network routing, a CDN edge, or a geographic firewall rule rather than the server being off.
Response time
How long a complete response took. Flagged above 3 seconds, because that is roughly where visitors and monitoring services start treating slow as down. A site this slow is technically up and practically broken.
Common Problems and Fixes
We can reach it and you cannot
The problem is local. Test mobile data first — it uses different DNS and different routing, so it isolates the cause in one step. If mobile works, flush your DNS cache, try a public resolver like 1.1.1.1, disable any VPN, and try a private browser window.
The server returns a 5xx error
The hosting is fine and the application is not. Check your server’s error logs, which will name the actual fault. A 502 or 504 specifically means the front end web server could not get a response from the application behind it — often a crashed process that a restart will clear, though the restart is a treatment rather than a cure.
The domain does not resolve
Nothing is being tested about the server, because there is no address to connect to. Two things to rule out, in order: check the domain has not expired with the WHOIS Lookup, then check its nameservers and A records with the DNS Checker. An expired domain produces symptoms identical to an outage.
It returns 403 but works in a browser
A firewall or bot-protection service is blocking automated requests. Our probes identify themselves honestly rather than impersonating a browser, so some security products refuse them. That is a correct outcome rather than a fault, and it means this tool cannot tell you much about that site.
It responds but takes several seconds
The site is up and struggling. Common causes are an overloaded server, a slow database, or a traffic spike. The Website Speed Test breaks down where the time is going.
What This Tool Cannot Tell You
- Whether the site actually works. We check that the server responds, not that the page renders, the JavaScript runs, or the checkout completes. A broken site can return a perfect 200.
- Why it is down. We report what the server returned. The cause is in your server logs.
- Anything about a site that blocks automated requests. A 403 from a security product tells you about the firewall, not the site.
- Whether it was down a minute ago. This is a spot check, not monitoring. Use a dedicated uptime service for continuous alerting.
- Whether an outage is regional. Multi-region probing is built but not currently switched on, so failures cannot yet be localised to a region.
Frequently Asked Questions
Is my website down, or is it just me?
That is the question this tool exists to answer. We request the site from our own infrastructure, entirely separately from your connection.
If we reach it and you cannot, the problem is between you and the site: a stale DNS cache, a VPN or proxy, an ISP routing issue, or a browser extension. If we cannot reach it either, the problem is at the site.
It says the site is up but it will not load for me. What now?
Work outwards from your own machine. Try a different browser, then a private window with extensions disabled, then a different network entirely — mobile data is the quickest test because it uses different DNS and different routing.
If mobile data works and your home connection does not, flush your DNS cache and try a public resolver such as 1.1.1.1. If every device on your network fails but mobile data works, the problem is your router or your ISP.
What does a 500 or 502 error mean?
It means the server is running and answering, which is genuinely different from being down. The machine is up; the application on it failed.
A 500 is an error inside the application. A 502 or 504 usually means a web server that cannot reach the application behind it — a crashed process, or one too busy to answer. A 503 typically means maintenance mode or an overloaded server. All four point at the application or its configuration rather than the hosting being off.
The domain does not resolve. Is that the same as down?
No, and the distinction matters because the fix is completely different. If DNS does not resolve there is no address to connect to, so nothing about the server is being tested at all.
The site may be running perfectly with broken DNS records in front of it. Check the domain's nameservers and A records with the DNS Checker, and check that the domain has not expired with the WHOIS Lookup — an expired domain stops resolving and looks exactly like a server outage.
How often can I check?
Results are cached for 60 seconds, which is short enough that a recovery shows up almost immediately while stopping a page refresh from hammering a server that is already struggling.
This is a spot check, not monitoring. If you need to know the moment a site comes back, a dedicated uptime monitoring service will poll continuously and alert you.
Why might your check succeed when the site is genuinely broken?
We request the page and report what the server returned. We do not render it, run its JavaScript, or check whether the content is correct.
A site can return a perfectly good 200 while displaying a database error, an empty page, or a checkout that does not work. This tool answers whether the server is responding, not whether the site is functioning.