Is It Down? Website Down Checker
Find out whether a website is down for everyone or just for you. The check runs from an external server and shows the HTTP status code and response time.
Is the site down for everyone or just me?
The tool requests the website from an external server and shows the HTTP status code and the response time. That resolves the key question during an outage: is the site down globally, or is the problem on your end? If the external server loads the site and gets a 200 while it will not load for you, the cause is local. If the external check also returns an error, the problem is on the server, at the hosting provider or in the site configuration, and that is where it needs fixing.
How to read HTTP status codes
The status code tells you right away what is going on:
2xx: success, the page is served normally (usually200).3xx: redirect, the site forwards to another address (for example a301to HTTPS).403: access forbidden: file permissions, server rules or an IP block.404: page not found, a wrong address or removed content.5xx: a server-side error:500,502,503,504.
What to do for each response
5xx codes mean you need to look at the server. A 500 usually points to a bug in code or configuration, 502 and 504 mean the web server did not get a timely response from the backend (PHP, an app server or the database), and 503 means the service is overloaded or down for maintenance. In those cases check the server logs and service status, and your hosting provider's status page. If the site returns 200 externally but not for you, look for local causes: stale DNS records, browser or OS cache, or an issue with your ISP or network. Try another device or mobile data, clear the cache and flush DNS. The response time shows how fast the server delivers the page: a sharp rise in latency often comes right before a full outage.