Server Status Checker
Check whether any web server is up, what it returns, and how fast it responds.
A server status checker tells you whether a web server is online and how it’s responding right now. Instead of guessing from a browser error, you get the raw signal: the HTTP status code the server returned and how many milliseconds it took. That’s enough to distinguish a healthy server, an overloaded one, a misconfigured one, and a server that isn’t answering at all.
Reading the server status code
The status code is the server’s own summary of what happened. 200–299 means success; 300–399 is a redirect; 400–499 is a client error such as 404 (not found) or 403 (forbidden); and 500–599 is a server error like 500 (internal error), 502 (bad gateway), or 503 (service unavailable). Crucially, any of these means the server is up and answering — even a 500. A server is only truly "down" when it doesn’t respond at all and the request times out.
Up, degraded, or down
Response time is the other half of the picture. A fast 200 is a healthy server. A slow response or an intermittent 502/503 usually signals a server that’s overloaded or mid-deploy — degraded rather than dead. A connection refused or a timeout with no status code at all is a server that’s down or unreachable. Our checker reports both the code and the timing so you can tell these apart.
Server status vs. the website being “broken”
A server can be perfectly up while the website feels broken, because one server often fronts many features. Login, search, or checkout can fail while the homepage returns a healthy 200. A server status checker confirms the front door is answering; for a specific service’s deeper health, our per-service pages track a live check and 24‑hour history.
Frequently Asked Questions
What does a server status checker tell me?
Whether a server is responding, the HTTP status code it returned, and how long the response took. Together these tell you if the server is up, degraded, or down, and give a first clue as to why.
Does a 500 or 503 error mean the server is down?
No — a 500 or 503 is an HTTP response, which means the server is up and answering, just reporting an error (often overload or maintenance for 503). A server is only "down" when it doesn’t respond at all and the request times out.
Why is a server slow but not down?
High response times usually mean the server is overloaded, under-resourced, or handling a traffic spike. It’s still up and returning valid responses, just degraded. Sustained slowness often precedes or follows an outage.