Down for everyone, or just you?
When a site won’t load, the first question is whether it’s the site or your connection. This tool requests the URL from our server on Cloudflare’s network, follows up to 10 redirects and waits up to 15 seconds. If it loads here and not for you, the problem is local.
What the verdicts mean
- Up. The server answered with a 2xx or 3xx status. We show the time to first byte and the final URL after redirects.
- Responding with an error. The server answered, but with a 4xx status: 404 (not found), 403 (forbidden, often bot protection) or 429 (too many requests). The site is up; this URL isn’t serving a page. We also use this verdict for redirect loops.
- Down. A 5xx status (the server or an upstream app failed), a timeout, or no connection at all. When nothing answers, we look up the domain’s DNS to tell a missing or expired domain (no A or AAAA records, or NXDOMAIN) apart from a server that isn’t responding.
Common causes, and where to look
- 502, 503 or 504: the CDN or proxy is up but your app behind it isn’t. Check your host’s status page and app logs.
- Timeouts: an overloaded server, a firewall dropping traffic, or a long-running request.
- No DNS records: an expired domain, changed nameservers, or a deleted record. The DNS lookup shows what’s there now.
- Redirect loops: often an http/https or www rule fighting with a CDN setting. The HTTP header checker shows every hop.
Search engines notice long outages too: repeated 5xx responses make Google crawl less, and pages that stay down for days can drop from the index. Short blips don’t hurt.