Down for everyone, or just you?
When a site will not load, the first question is whether the problem is the site or your connection. This tool requests the page from Cloudflare's network, far from your browser, Wi-Fi and DNS cache. If it answers here, the site is up and the issue is closer to you.
Reading the result
- Up (2xx or 3xx). The server answered normally. If you still cannot reach it, try another network, flush your DNS cache, or check whether a browser extension, VPN or firewall is blocking it.
- Up, but returns an error (4xx). The server is running but refuses this URL: a 404 for a missing page, 403 for blocked access, or 401 behind a login. The site is not down; the page is.
- Down (5xx). The server or its upstream failed. 500 is an application error, 502 and 504 mean a proxy could not reach the origin, and 503 often means maintenance or overload.
- No answer. DNS did not resolve, the connection was refused, or nothing replied within 10 seconds.
If it is your site
- Check your host or CDN status page.
- Look at the most recent deploy. Most outages follow a change.
- Confirm DNS still points where you expect with the DNS lookup.
- Check the certificate has not expired with the SSL checker.
Short outages rarely hurt rankings: Google retries before dropping pages. Outages that last days, or a site that answers 200 with an error page, do. A server that returns 503 with a Retry-After header during maintenance tells crawlers to come back later instead of indexing the error.