Most website owners find out their site is down the same way: a customer tells them. Sometimes it is an email, sometimes a missed order, sometimes a message from a friend who “couldn’t get the page to load”. By then the site may have been down for an hour, or for the whole night.
Monitoring exists to close that gap. A monitor asks your site, over and over, whether it is working, and tells you the moment the answer is no.
Websites fail quietly
When a shop closes, the door is shut and everyone can see it. A website that stops working looks perfectly fine from the inside. You are logged in, your browser has the page cached, and nothing on your screen has changed. Meanwhile every new visitor is getting an error, a blank page or a spinner that never stops.
The causes are rarely dramatic:
- A hosting provider has a problem, or restarts the server you are on.
- A deployment goes out with a bug that only shows on the live site.
- The database fills up, runs out of connections or stops responding.
- An SSL certificate expires, and browsers show visitors a full-page security warning.
- A domain renewal is missed, or a DNS change goes wrong, and the address stops resolving.
- A traffic spike, a bot or a slow query makes the site too slow to use.
None of these tells you about itself. They are only noticed when somebody looks.
What an outage actually costs
The direct cost is the sales, sign-ups and enquiries you could not take while the site was down. For a business that takes orders online, that is easy to put a number on, and the number grows with every minute you do not know about the problem.
The indirect costs are harder to see and often larger:
- Trust. A visitor who meets an error page may not come back. They rarely tell you; they just go elsewhere.
- Search visibility. If search engines repeatedly find your site unavailable, pages can drop in the results. A short outage is usually forgiven; a long or repeated one is not.
- Your own time. Finding a problem late means diagnosing it under pressure, with customers already waiting.
The cost is mostly in the delay. Fixing an outage often takes minutes. What takes hours is noticing it. Monitoring shrinks the part you can do something about.
What a heartbeat check does
A website heartbeat check is a small, regular request to your site. Every few minutes a monitor asks for a page, and if it gets a healthy response, it is satisfied. If it gets an error, a timeout or no answer at all, it tries once more to rule out a one-off glitch, and then raises the alarm.
That alarm is the point. It reaches you by email, a chat message or a webhook, wherever you will see it fastest, and a second message tells you when the site has recovered. You find out in minutes, from a machine, instead of hours later from a customer.
A record, as well as an alarm
Good monitoring also keeps history. Each outage is logged with when it started and when it ended, so you can answer questions that are otherwise guesswork. How often does the site go down? How long does it take to recover? Is it getting slower over time? That record is what lets you spot a failing host before it fails badly, and it gives you something concrete to show a hosting provider when you ask for a refund or a fix.
The website monitoring metrics guide goes through the numbers worth tracking.
Who needs it
Anyone whose website matters to the work they do. A shop, a booking page, a portfolio that brings in clients, a client’s site you look after, an API that other software relies on. If the site being down for a day would cost you money or reputation, it is worth five minutes to set up a monitor.
It is especially valuable when you look after sites for other people. Being the first to know, and already working on the fix when the client notices, is a very different conversation from finding out from them.
Getting started
- Pick the address to watch. Your homepage works, but a dedicated health page is lighter and clearer. Pingvella provides a ready-made one you can upload in a minute.
- Choose where alerts should go, and make sure it is somewhere you will actually see them.
- Test it. Pause the check, or point it at an address that does not exist, and confirm you receive the alert.
Pingvella checks every website every 5 minutes, and every account can have five website checks, including the free one. This guide explains how it works from the first request to the recovery notice.