How an uptime monitor checks your site from outside
An uptime monitor is a service that keeps asking your site a simple question: are you there? It does this from its own computers, on a timer, and it tells you when the answer changes.
What one check looks like
For most small sites, the check is a web request. The monitor asks for your page the way a browser would, then looks at what comes back. UptimeRobot describes website monitoring as checking whether a page returns a successful HTTP response.1
If the page loads and the reply says everything's fine, the check passes. If the reply is an error, or nothing comes back before the monitor gives up, the check fails.
Where the checks come from
The monitor sits outside your site on purpose. Wikipedia notes that the monitoring is often conducted from several locations around the world.2 That matters because you can't always see a problem from your own desk. Your laptop may have the page saved, or your own network may have a quirk that visitors don't share.
Checking from the outside is closer to what a visitor sees. It also means the monitor keeps working when your own computer is switched off.
How often it checks
Wikipedia says monitoring frequency runs from once every four hours to every 15 seconds.2 Most providers offer a free plan with low-frequency monitoring. StatusCake's free plan, for example, lists test intervals of five minutes (checked 16 November 2026).3
Why does this matter? A check every five minutes can't notice a problem that starts and ends in the gap between two checks, so a short blip may never reach your report. Tight gaps catch more.
Is it really "pinging"?
People say "ping" for any check, but the word has a narrow meaning. Ping sends an ICMP echo request to a computer and waits for an echo reply.4 It asks whether the machine answers at all. It says nothing about whether your web pages work.
That's why the web request is the usual choice for a website. The difference between the two is the subject of HTTP, ping and keyword checks compared.
Why a "successful" reply can still hide a problem
A page can still return a 200 OK status while showing an error message, as UptimeRobot points out.1 The server said yes, but the visitor sees something broken. A basic check would call that a pass.
A second check that looks for a word on the page can catch that quiet kind of failure. If you're stuck on what went wrong, see what to do when the site is down.
What happens after a failure
When a check fails, the monitor doesn't just record it. Wikipedia says monitoring services send out alerts via email, SMS or phone.2 You pick which channels to use. How to keep those alerts useful, rather than noisy, is covered in setting alerts without drowning in false alarms.
A monitor can only report what it sees from outside. It can tell you the site isn't answering, but it can't tell you why. That job falls to you or your host. Nothing more.
Notes and sources
- Keyword monitoring and website monitoring, UptimeRobot
- Website monitoring, Wikipedia
- Pricing, StatusCake
- Ping (networking utility), Wikipedia