To check website uptime, use a monitoring tool that pings your site every few minutes from several locations and alerts you the moment it stops responding. A one-off manual check only tells you your site is up right now; continuous monitoring tells you when it went down, for how long, and whether visitors were affected.
I learned this second-hand, the expensive way. A small bakery I helped discovered on a Monday morning that its site had been down since Friday night. Weekend customers looking for opening hours and the cake-order form found an error page instead. Routine host maintenance had failed to restart, and three days of weekend traffic quietly evaporated. One free uptime monitor, set up in ten minutes, would have sent an alert on Friday night and turned a three-day outage into a ten-minute fix. That is the whole case for checking website uptime properly: you cannot fix a problem you do not know about.
What does website uptime actually mean?
Website uptime is the percentage of time your site is available and responding to visitors. Small percentages hide large amounts of time. For a 30-day month:
– 99 percent uptime allows about 7 hours and 12 minutes of downtime.
– 99.9 percent uptime allows about 43 minutes.
– 99.99 percent uptime allows about 4 minutes.
So a host advertising “99.9% uptime” still allows roughly three quarters of an hour down per month — enough to lose real visitors if the outage lands at your busiest hour. Uptime is also different from speed: a site can be technically “up” while loading so slowly that visitors leave.
How do you check website uptime right now?
If you want an answer this minute, work through these checks in order:
1. Open the site in a private window. Incognito mode skips your cached copy and shows what a new visitor sees.
2. Rule out your own connection. Open the site on your phone with Wi-Fi off, over mobile data. If it works there but not on your office network, the problem is your network, not your site.
3. Ask a third-party checker. Free “is it down” tools load your site from their own servers and report whether it responds — a quick second opinion, but only for one moment in time.
4. Check your host’s status page. If your host reports an incident, your site is probably one of many affected — wait for their fix rather than changing your own settings in a panic.
5. Check the quiet killers: domain and SSL expiry. A site showing a security warning or a registrar parking page has usually not been hacked — its certificate or domain renewal has lapsed. Check both before assuming the server is at fault.
These checks answer “is it down right now?” They cannot answer “was it down at 3 a.m.?” For that, you need monitoring.
How do you set up uptime monitoring that alerts you?
Most tools offer a free tier that covers a small site comfortably. Here is the setup I use:
Step 1: Pick a monitor with a free plan. UptimeRobot, Better Stack, and similar tools monitor a handful of sites free — no paid plan needed for the core benefit: an alert when your site stops answering.
Step 2: Add your homepage — and one key inner page. The homepage proves the server is alive; an inner page, like your contact page, proves the site actually works. A database failure can leave the homepage up while every other page errors.
Step 3: Set a short check interval. Five minutes is the usual free-tier interval and is fine for most small sites; one-minute checks catch shorter outages but generate more noise.
Step 4: Monitor from more than one location. A single-location monitor can cry wolf when its own data centre has a network problem. Two or three locations, alerting only when several agree, cuts false alarms sharply.
Step 5: Choose alert channels you will actually see. Email alerts are easy to miss at 2 a.m., so add push notification or SMS for your main site. An alert you sleep through is no better than no alert.
Step 6: Test the alert before you trust it. Point a monitor at a test page you control, take that page down briefly, and confirm the alert arrives. I once discovered months too late that a client’s alerts were landing in a spam folder.
What should you do the moment you get a downtime alert?
Do not start changing settings at random. First, verify it from a second source: open the site on mobile data or run a quick third-party check. If only the monitor says down, wait for its next check — single-location blips happen.
Second, check your host’s status page. If the host reports an incident, note the time and wait — changing your own DNS or plugin settings during a host outage only adds a second problem.
Third, think about what changed recently. Most small-site outages follow a change: a plugin update, a theme edit, a DNS change, a certificate renewal. If you updated something hours before the outage, rolling it back is often faster than diagnosing it.
Fourth, contact your host with facts, not feelings. “My site has returned a 500 error since 02:14, confirmed from two locations, and your status page shows no incident” gets a faster, better answer than “my site is down, fix it.”
Finally, check the site properly once it returns. An outage can mask a second problem — a half-applied update, a broken form, a page that loads but looks wrong. Open your key pages and confirm they work, not just that they load. A quick pass with our responsive preview tool also shows your site at phone, tablet, and desktop widths side by side, so a fix that broke the layout does not slip past you.
What is a good uptime target — and what usually takes sites down?
For a small business or personal site, 99.9 percent uptime per month is a realistic, healthy target — roughly 43 minutes of downtime, ideally none of it during your busy hours. What matters more than the third decimal place is hearing about outages within minutes, not days.
The usual culprits are unglamorous: maintenance that fails to restart cleanly, an expired domain or SSL certificate, a plugin update that conflicts with the theme, a traffic spike overwhelming a small hosting plan, and DNS changes that propagate badly. Auto-renewals, updates tested on staging first, and a monitor that tells you within minutes cover almost all of them.
A mini-test on my own small site makes the point. A free monitor checking every five minutes caught a 25-minute outage at 2 a.m. caused by host maintenance. I was asleep, but the alert was waiting when I woke up, with exact start and end times. I confirmed the maintenance window matched and checked the key pages — no visitor had complained, because the outage was short and I knew about it before they did. Without the monitor I would never have known it happened.
FAQ
What does it mean to check website uptime?
To check website uptime means to verify that your site is available and responding to visitors, either at one moment or continuously over days and weeks. A one-off check answers “is it up now?”; a monitor answers “was it up all week?”
How often should an uptime monitor check my site?
Every five minutes is enough for most small sites and is the standard free-tier interval. One-minute checks catch shorter outages but generate more noise. Monitor from at least two locations so a single network blip does not wake you up.
What is a good uptime percentage for a small website?
Aim for 99.9 percent uptime per month, about 43 minutes of downtime. More important is how fast you find out: an alert within five minutes turns most outages into minor incidents.
Why is my website down but my hosting account looks fine?
The most common reasons are an expired domain or SSL certificate, a failed plugin or theme update, a DNS change that has not propagated, or a host-side incident not yet on the status page. Check domain and certificate expiry first, then the host’s status page, then what changed on the site most recently.