Website Uptime Checker
"Is it down for everyone, or just me?" — check any website's live status, response code and speed from an independent server.
How to read an uptime result
2xx means the page served normally. 3xx is a redirect — fine if it lands where you expect, suspicious if your homepage suddenly redirects somewhere you do not recognise. 4xx means the server is alive but refuses or cannot find the page (a 403 after a migration usually means permissions or a firewall rule; a 404 on the homepage usually means a moved document root). 5xx is a server-side failure — the application, PHP, or the database is down even though the machine is up. And no response at all points lower in the stack: DNS, network, or a dead server, in that order of likelihood.
Response time matters almost as much as up or down. A homepage answering in 4 seconds is technically "up" and practically losing customers — studies keep landing on the same conclusion, that most mobile visitors abandon pages slower than about 3 seconds. Watch for a site that is up but drifting slower week by week; that is usually a database or disk problem announcing itself early.
The limit of a one-off check
This tool answers "now". It cannot tell you the site was down from 02:10 to 02:40 last night, which is when most unattended outages happen and when they are cheapest to miss and most expensive to discover from an angry customer. That gap — between checking and watching — is the whole reason UptimeVitals exists: checks every minute, from more than one place, with an alert the moment something changes.
Uptime Checker — frequently asked questions
The checker says up, but I cannot open the site. Who is right?
Both can be. Our server reaches it; your connection may be blocked by local DNS, your ISP, a firewall rule, or your own IP being rate-limited by the server. Try your phone on mobile data — if it loads there, the problem is between you and the server, not the server.
Why does my site show a redirect?
Usually HTTP→HTTPS or non-www→www, both healthy. It becomes a problem when the destination is unexpected or loops — browsers report loops as an error long before they report slowness.
What response time should I aim for?
Under 1 second from your main audience's region is good; under 2.5 seconds is acceptable; consistently over 3 seconds costs traffic and rankings.
Does this check subpages too?
Yes — paste any full URL, not just the homepage. Checking the checkout or login page specifically is a good habit; homepages are often cached and healthy while dynamic pages fail.