Uptime Monitor
Check website availability and uptime status from multiple locations.
This tool performs an instant availability check to determine if a website is online and responding.
It measures response time and Time to First Byte (TTFB) to assess server performance.
Note: This is a single check, not continuous monitoring.
Down at 3am: verifying an outage from outside your network
When a user reports your site is down, the first question is: is it down for everyone or just them? An independent uptime check answers that in seconds.
A site can appear down for three different reasons: the server is genuinely unreachable, the user's ISP has a routing issue, or the user's DNS is stale. Running an uptime check from our infrastructure tells you definitively whether the server is responding to HTTP requests from the outside world — independently of the user's network, browser, or cache. If we see HTTP 200, the site is up. If we see a timeout or 5xx, the outage is real.
HTTP 200, 301, 403, 503: what each status code tells you
Not all 'up' responses are equal. A 301 redirect, a 403 Forbidden, and a 200 OK all indicate different things about your site's actual health.
HTTP 200 means the server returned content successfully. 301/302 means the URL redirects — useful for knowing if redirects are in place but a chain of 3+ redirects adds measurable latency. 403 Forbidden usually means authentication or IP blocking is working — your site is up but access is restricted. 503 Service Unavailable means the server is reachable but overloaded or in maintenance mode. 504 Gateway Timeout means the upstream server didn't respond — often a sign of backend overload.
Response time vs. uptime: both matter, differently
A site can be 'up' but respond in 4 seconds — which is functionally down for most users. Response time is uptime's silent partner.
Traditional uptime monitoring checks if a server responds at all. Response time monitoring checks how long it takes. A 4-second response time means your server answered, but the user experience is degraded to the point of abandonment. For SLA reporting, pure uptime (% of time the server responds) is the metric. For actual user experience, response time under 1.5s is the goal. This check gives you both.
Before calling your hosting provider: verify with an independent check first
Hosting support will ask if you've verified from outside your network. Run this check first — it tells you whether the issue is on their side or yours.
When you report an outage to your host, the first thing they'll do is ping your server from their infrastructure. If it responds, they'll tell you the server is fine — and the conversation stalls. Running an independent check before you call gives you the same data they'd collect: HTTP response code, response time, and whether the server is reachable from an external network. If this check shows the site is down, your outage report is immediately credible.