What Uptime Monitoring Actually Checks

An uptime check makes one request, right now, and reports whether it succeeded. That is genuinely useful for confirming a site is up at this exact moment, but it says nothing about ten minutes ago or ten minutes from now. Real uptime monitoring, the kind that pages someone at 3am, works by repeating this same check on a schedule and alerting when a result changes.

Down is not just a connection failure. A server that responds but returns a 500 error, or a database-backed site that loads a page shell with none of the actual content, can be just as broken from a visitor's point of view as a server that does not respond at all. A meaningful uptime check should treat a server error as a failure, not just a total lack of response.

A single failed check could mean the site is genuinely down, or it could mean one request happened to hit a brief hiccup, a momentary network blip, or a server that was mid-restart. Real monitoring tools usually wait for two or three consecutive failures before alerting anyone, specifically to avoid false alarms from a single unlucky request.

Continuous uptime monitoring needs somewhere to store history and someone to notify when something changes, which means accounts. Since the free tools on Frabs deliberately have none, Uptime Checker is a genuine one-off: run it whenever you want a current answer, rather than something watching in the background on your behalf.

Uptime Checker reports whether a site is online right now, its HTTP status code, and how long it took to respond. For a fuller picture in one pass, including SSL, DNS and performance rather than just an up or down answer, the full Health Check covers all of it in a single report.