sourcecodestack Team
Tools, guides & how-tos
Your website is down. Right now, somewhere in the world, a potential customer is trying to reach you, getting an error message, and clicking over to your competitor. How long has it been down? You have no idea — because no one told you.
This scenario plays out thousands of times every day for businesses, developers, and content creators who haven’t set up uptime monitoring. This guide explains what uptime monitoring is, why downtime is far more costly than most people realize, and how to implement a solid monitoring strategy.
Website uptime is the percentage of time a website is accessible and responding correctly to requests. It’s measured over a rolling time period — usually 30 days — and expressed as a percentage.
Downtime is everything else: the time when your site is slow, returning errors, or completely unreachable.
Uptime is typically measured by a monitoring service that sends requests to your website at regular intervals (every 1, 5, or 10 minutes) and records whether a valid response was received. If several consecutive checks fail, an alert is triggered.
Uptime percentages sound impressive until you convert them to actual downtime. A 99% uptime guarantee sounds nearly perfect — but it allows for over 87 hours of downtime per year.
| Uptime % | Downtime per Year | Downtime per Month | Downtime per Week |
|---|---|---|---|
| 90% | 36.5 days | ~73 hours | ~16.8 hours |
| 95% | 18.25 days | ~36 hours | ~8.4 hours |
| 99% | 3.65 days | ~7.3 hours | ~1.68 hours |
| 99.5% | 1.83 days | ~3.65 hours | ~50.4 minutes |
| 99.9% | 8.76 hours | ~43.8 minutes | ~10.1 minutes |
| 99.95% | 4.38 hours | ~21.9 minutes | ~5 minutes |
| 99.99% | 52.6 minutes | ~4.4 minutes | ~1 minute |
| 99.999% | 5.26 minutes | ~26 seconds | ~6 seconds |
When your hosting provider offers a 99.9% uptime SLA (Service Level Agreement), they’re contractually allowing your site to be down for nearly 9 hours per year. For an e-commerce store, that could be catastrophic.
Pro Tip: Uptime percentages in SLAs refer to scheduled and measured uptime — not your actual experience. Read the fine print to understand what maintenance windows, planned outages, and force majeure clauses exclude from the SLA calculation.
| Website Type | Minimum Acceptable Uptime | Target |
|---|---|---|
| Personal blog | 99% | 99.9% |
| Small business site | 99.5% | 99.9% |
| E-commerce store | 99.9% | 99.95% |
| SaaS application | 99.9% | 99.99% |
| Critical infrastructure | 99.99% | 99.999% |
Most website owners dramatically underestimate the cost of downtime. The impact is felt across multiple dimensions simultaneously.
For e-commerce sites, the math is straightforward: if your store generates $10,000 per day in revenue and goes down for 4 hours, that’s roughly $1,667 in lost sales — assuming you can recapture none of that demand (which you often cannot, because customers buy elsewhere).
Amazon famously loses an estimated $220,000 per minute of downtime. Even at a fraction of that scale, downtime is expensive.
This is the less obvious but potentially longer-lasting consequence. Googlebot crawls your site regularly. If it encounters:
Rankings built over months of content and link building can evaporate during a prolonged outage. Restoring rankings takes time — time during which your organic traffic and revenue remain suppressed.
81% of users who encounter a website error will leave and try a competitor. Of those, a significant portion won’t return. In the age of instant alternatives, a downed site is an invitation to churn.
For B2B companies, a website outage during a critical sales conversation or product demo can directly cost enterprise deals worth tens or hundreds of thousands of dollars.
Frequent downtime signals operational immaturity. Enterprise buyers and sophisticated consumers factor website reliability into their assessment of a vendor’s overall reliability. An unstable website suggests unstable operations.
Understanding HTTP status codes is essential for interpreting uptime monitoring results. When a monitoring service reports that your site is “down,” the specific status code tells you a great deal about what’s wrong.
| Code | Name | Meaning |
|---|---|---|
| 200 | OK | Normal successful response |
| 201 | Created | Resource successfully created (POST requests) |
| 204 | No Content | Success with no response body |
| Code | Name | Meaning |
|---|---|---|
| 301 | Moved Permanently | URL has changed permanently — update your links |
| 302 | Found | Temporary redirect |
| 304 | Not Modified | Cached version is still valid |
Pro Tip: Uptime monitors should follow redirects (301/302) and check the final destination. A broken redirect chain — where the final URL returns a 404 or 500 — means your site is effectively down even though the initial URL responds.
| Code | Name | Meaning |
|---|---|---|
| 400 | Bad Request | Malformed request syntax |
| 401 | Unauthorized | Authentication required |
| 403 | Forbidden | Access denied |
| 404 | Not Found | Page doesn’t exist — check for broken links |
| 429 | Too Many Requests | Rate limiting — often temporary |
| Code | Name | Meaning |
|---|---|---|
| 500 | Internal Server Error | Generic server-side failure |
| 502 | Bad Gateway | Upstream server sent invalid response |
| 503 | Service Unavailable | Server overloaded or in maintenance |
| 504 | Gateway Timeout | Upstream server took too long to respond |
For uptime monitoring purposes, any 5xx response is treated as downtime. 4xx responses are more nuanced — a 404 on a specific monitored page indicates a problem, but 404s on arbitrary URLs are not downtime.
Uptime monitoring services work by deploying agents in multiple geographic locations that periodically send HTTP requests to your website and record the results.
| Interval | Best For |
|---|---|
| 1 minute | Critical production applications, e-commerce |
| 5 minutes | Standard business websites |
| 10 minutes | Blogs, portfolio sites, low-traffic sites |
| 30 minutes | Development/staging environments |
A sophisticated monitoring setup checks from multiple geographic locations simultaneously. This is important because:
Multi-location monitoring distinguishes between “site is down globally” and “site is unreachable from East Asia” — very different problems requiring different responses.
| Feature | Free Tools | Paid Tools |
|---|---|---|
| Check interval | 5-30 minutes | 1 minute or less |
| Monitoring locations | 1-3 | 5-20+ |
| Alert methods | Email only | Email, SMS, Slack, PagerDuty, webhooks |
| Alert delay | Immediate to 15 min | Immediate |
| Response time history | 30-90 days | 1+ year |
| Status page | Basic or none | Branded public status page |
| SSL monitoring | Sometimes | Always |
| Domain expiry monitoring | No | Yes |
| API access | No | Yes |
| Multiple contacts | No | Yes |
| Escalation policies | No | Yes |
| Price | Free | $5-$50+/month |
Free tools are appropriate for: Personal blogs, hobby projects, low-stakes websites where 5-10 minute check intervals are acceptable.
Paid tools are appropriate for: E-commerce, SaaS, any site where downtime costs money or damages customer relationships.
Before assuming your site is globally down, it’s worth checking whether the issue is on your end. This is one of the most common troubleshooting scenarios: you can’t reach a site, but it’s actually fine everywhere else.
# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux
sudo systemctl restart systemd-resolvedHaving a documented incident response plan before you need it is the difference between a 10-minute outage and a 4-hour crisis.
Pro Tip: Keep a “runbook” — a document with step-by-step procedures for your most common failure scenarios. When you’re stressed during an outage at 2 AM, having a checklist prevents you from missing obvious steps.
Two related monitoring tasks often overlooked:
An expired SSL certificate causes browsers to show scary security warnings that prevent users from accessing your site. Many hosting providers now offer auto-renewal via Let’s Encrypt, but auto-renewal can fail silently.
Good uptime monitoring services alert you 30, 14, and 7 days before your SSL certificate expires.
Domain registrations must be renewed annually (or every 2-10 years). Forgetting to renew can result in:
Set reminders at least 60 days before domain expiry.
To check your website’s current status and set up basic monitoring, use our Website Uptime Checker. It provides:
For ongoing monitoring, configure alerts so you’re notified within minutes — not hours — when something goes wrong. The faster you know about downtime, the faster you can fix it, and the less revenue and reputation damage occurs.
Website uptime is not a technical vanity metric — it’s a direct measure of your reliability and a significant factor in revenue, SEO performance, and customer trust. For any website where downtime has real consequences, monitoring should be implemented before you need it, not after an incident reminds you.
Start with the basics: set up monitoring for your primary domain, configure email alerts, and know your hosting provider’s SLA. Then build up to SSL monitoring, multi-location checks, and a public status page as your site grows in importance. The time investment is small; the value during an actual outage is enormous.
sourcecodestack Team
We build free, privacy-first browser tools and write practical guides on how to use them. Everything runs on your device — no uploads, no sign-ups.
A site will not load. Before you clear your cache, reboot the router, or file an angry support ticket, answer …
You have two JSON payloads — maybe a staging API response and a production one, or a config file before and af…
API Client Guide: Test APIs Online Without Postman Testing an API should be fast and frictionless. You have an…