RunTheTests

Is This Site Down?

Check whether a site answers from outside your own network.

We request the page once from a Cloudflare edge and report what came back. Private and internal addresses are refused.

How this check works

The address is requested once from a Cloudflare edge server and the response is reported back: status code, how long it took, and every redirect along the way. Because the request comes from our infrastructure rather than your browser, it distinguishes a site that is genuinely down from one your own network or ISP cannot reach.

What the results mean

Status
The HTTP code the server returned. 200 is normal; 4xx means the server is running but rejected the request; 5xx means the server itself is failing.
Response time
Measured from a Cloudflare edge to the site. It reflects the site’s speed, not your connection’s.
Redirects
Each hop between the address you gave and the page that finally answered. Long chains slow every visitor and often signal a misconfiguration.
Final address
Where the chain ended. If this is not what you expected, a redirect rule is sending traffic somewhere unintended.

Common problems and fixes

The site loads for me but this says 403
The server is filtering automated requests by user agent or by IP reputation. The site is up — it just will not answer a checker. This is common behaviour behind bot protection.
It reports down but the site is fine elsewhere
One check from one location cannot prove an outage. Repeat it, and compare against a check from your own browser before concluding anything.
The check refuses my address
Private, loopback and reserved addresses are rejected deliberately. A checker that would fetch internal addresses on request is a security hole, not a feature.

Frequently asked questions

Does this mean the site is down for everyone?

No. It means one request from one Cloudflare location did not get a usable answer. Outages are regional far more often than they are total, and plenty of sites deliberately block automated checkers. Treat a failure as one data point, not a verdict.

Why can I not check an address on my own network?

Because we would be making the request, not you. A tool that fetches any address on request can be pointed at internal services and cloud metadata endpoints — a server-side request forgery vector. Private, loopback and reserved ranges are refused, and every redirect is re-checked so a public address cannot bounce into one.

Do you record what I check?

No. The address is used to make the request and is not logged or stored.

More in Connection