Find out whether a website answers our Cloudflare edge right now and get a plain UP or DOWN verdict, with the HTTP code and response time behind it.
Pro tip: Unstable means it answered some probes but not all — suspect rate limiting, firewall rules, or a flaky origin.
When a page will not load you cannot always tell whether the site is genuinely offline or whether something local, like your Wi-Fi, VPN, or DNS, is the culprit. This tool answers from a different vantage point: our Cloudflare edge sends one HTTP request to the address, follows any redirects, and reports whether it got a usable response. That gives you a second opinion that rules your own network in or out.
The result is summarised as a single verdict with three supporting numbers, so you can act on it without parsing raw output.
The verdict is deliberately binary. UP means the server answered with a status that shows it is alive and serving, and DOWN means it did not. The exact rule matters: any status from 200 up to 499 counts as UP, with one exception, while 5xx server errors and a 429 rate-limit response count as DOWN.
That has a useful consequence. A 404 still returns an UP verdict, because the server is clearly running and responding even though that particular path is missing. A 500 or a 503, by contrast, means the server itself is failing to serve, so it is reported as DOWN. If the host cannot be reached at all, or the request times out, that is DOWN as well.
The verdict is built from one request collected the instant you run it, so it describes that moment rather than guaranteeing anything about the next hour. A site can recover or fail again seconds later. For an outage you are actively watching, run the check a couple of times a minute apart to confirm the state is steady rather than a one-off blip, and watch whether the HTTP code stays the same.
A DOWN verdict means our edge could not get a healthy response, which is not always the same as the site being broken for everyone. A firewall, a geo-block, or a bot filter that refuses our identified tool request can produce a DOWN result while real users in another region load the page normally. A 429 in particular often just means we hit a rate limit, not that the site is down for humans. Conversely, an UP verdict confirms the server responded, but it does not promise that every page, database, or checkout behind it is working, and remember a 4xx still reads as UP. Only publicly reachable hosts can be probed; private and loopback addresses are refused.
Input: https://example-shop.com
Output: Status: DOWN • HTTP code: 503 • Response time: 60 ms • example-shop.com appears to be down or unreachable from our edge.
A fast 503 from the edge points to the site itself, not your connection.
Input: https://example.com/typo-url
Output: Status: UP • HTTP code: 404 • Response time: 150 ms • example.com appears to be up and reachable for us right now.
The server is clearly alive; only that one path is missing, so the verdict is UP.
No. The probe runs from our edge, not your device, which is exactly why it can tell you whether the issue is the site itself or something local to you.
A 404 proves the server is running and answering requests; it just does not have that specific page. The verdict reflects whether the host is serving, so a 404 counts as UP while a 5xx counts as DOWN.
The host may be refusing our automated request through a firewall, a regional block, or rate limiting while still serving you. The verdict reflects only what our edge could reach, and a 429 or a block both read as DOWN.
It means the server responded. Pages, logins, or payment flows further inside the application could still be failing independently, and a 4xx page also reads as UP.
No. This check is a single probe with a clean UP or DOWN answer. To gauge consistency over several requests, use the online ping tool, which samples the URL multiple times.
It reflects the moment you run it. Re-running after a short wait confirms whether the UP or DOWN state, and the HTTP code behind it, is holding steady.
Our editorial and data-source notes explain how each check works and where estimates come from.