Is It Down?
Check if a website is down for everyone or just you. We test from our edge servers so you know if it's a global outage or a local issue.
How the Down Checker Works
We send an HTTP request to the URL from our Netlify edge infrastructure. If the server responds with any status code, the site is up and reachable. If the connection times out or is refused, the site is down globally.
This lets you distinguish between "the site is broken everywhere" vs. "something in my network path is blocking access."
If the Site Is Up but You Can't Access It
- Flush your DNS cache:
ipconfig /flushdns(Windows) orsudo dscacheutil -flushcache(Mac) - Try a different DNS server (8.8.8.8 or 1.1.1.1)
- Check if your ISP is blocking the domain
- Try a different network (mobile data vs WiFi)
- Check if the site has geo-restrictions
- Clear your browser cache and cookies
HTTP Status Code Reference
| Code | Meaning | Site Status |
|---|---|---|
200 | OK — Page loaded successfully | UP |
301/302 | Redirect — Being forwarded to another URL | UP |
403 | Forbidden — Server up, access denied | UP (restricted) |
404 | Not Found — Server up, page missing | UP (error) |
500 | Internal Server Error | DOWN |
502/503 | Bad Gateway / Service Unavailable | DOWN |
| Timeout | No response received | DOWN |
Frequently Asked Questions
Use this tool to test from our servers. If the check shows the site is up but you can't reach it, the problem is local — clear DNS cache, try a different network, or use a VPN. If our check shows it's down, it's a global outage.
Common causes: outdated DNS cache, ISP routing issues, local firewall, your IP being blocked, or geographic restrictions. Try flushing DNS, switching networks, or using a different DNS server like 1.1.1.1.
Codes 200–399 mean the site is up. 400–499 means the site is up but rejecting the request (404, 403, etc). 500–599 means the server is up but erroring. Connection failures mean the site is completely unreachable.
You can run checks as often as needed. For ongoing monitoring, check every few minutes during an incident. For production monitoring, consider a dedicated uptime service that checks from multiple regions automatically.