Uptime Checker

What it does

The Uptime Checker tells you whether a website is reachable right now. It makes a single request to the URL you enter from our European location (and, where available, a second US location), and reports the HTTP status code, the response time, and a simple Online / Warning / Down verdict for each region.

Use it for a quick "is it just me, or is the site really down?" check, to confirm a site is back after maintenance, or to see whether a site responds differently from another part of the world.

How to use it

1. Paste the website address (e.g. example.com) into the box. You can leave off the https:// — we add it for you.
2. Press Check. The result usually appears within a few seconds.
3. Read the overall verdict at the top, then the per-region rows (EU and US) for the status code, response time and any error reason.

What the results mean

Result	What it means
Online	The site responded successfully (a normal 2xx/3xx status) within a reasonable time. It is up.
Warning	The site responded, but slowly (around 2.5 seconds or more). It is up, but visitors may notice a lag.
Down	The site did not respond successfully — it timed out, refused the connection, returned a server error, or was blocked. See the reason shown next to the region.

Errors & warnings explained

Message	What it means
Connection timed out	The server did not respond in time. It may be overloaded, very slow, or unreachable from that region.
DNS error	The domain name could not be resolved to an IP address. Check the spelling, or the domain's DNS may be misconfigured or expired.
SSL/TLS certificate error	The secure connection could not be established — often an expired, mismatched or untrusted certificate. Try the SSL Expiry Checker for detail.
Connection refused	The server actively rejected the connection. The web server may be down or not listening on that port.
Too many redirects	The URL kept redirecting in a loop and never settled on a final page.
Server error (5xx)	The server was reached but returned a 5xx error (e.g. 500, 502, 503) — the site is up but its application is failing.
Client error (4xx)	The server returned a 4xx error such as 404 (page not found). The address may be wrong or the page removed.
Blocked (401 / 403)	The server returned "unauthorised" or "forbidden". The page may require a login, or a firewall is blocking our checker.
Blocked by bot protection	A bot-protection service (e.g. a Cloudflare challenge) intercepted the request. The site is likely up for normal visitors — automated checks just can't see past the challenge.
Empty response	The connection opened but the server sent nothing back. Often a crashing or restarting web server.
That doesn't look like a valid address	The text entered couldn't be read as a website address. Try the bare domain, like yourwebsite.com.
That address can't be checked	You entered a local, private or internal address (e.g. localhost or 192.168.x.x). The tool only checks public websites.
Too many checks	You've run several checks quickly and hit the rate limit. Wait a minute and try again.

Good to know

• Free and no login required. We don't store the URLs you check — only an anonymous record that a check happened.
• Rate limited to roughly 8 checks per minute per network to keep the tool fast for everyone.
• The European location is always available; the US location appears when our secondary vantage is online (otherwise it shows "Coming soon" / "Temporarily unavailable").
• This is a one-off, on-demand check. To be told automatically when a site goes down, set up continuous monitoring with an account.

Related guides

• Response Time Checker
• SSL Expiry Checker
• Homepage Health Checker