What Website Downtime Actually Costs You
Everyone knows downtime is bad. But most small businesses and indie developers haven't calculated what it actually costs them. It's usually more than they expect.
The Direct Cost: Lost Revenue
If your site takes payments, every minute of downtime is a direct revenue loss. A rough formula:
Hourly revenue × downtime hours = lost revenue
If your site generates $5,000/month, that's roughly $7/hour. An hour of downtime during business hours costs you $7. A weekend outage that runs 8 hours costs $56 before you even start counting indirect costs.
For higher-traffic or higher-AOV sites, the numbers scale fast. An e-commerce store doing $50k/month loses $70 per hour. A SaaS app with annual contracts loses credibility that's hard to price.
The Indirect Cost: SEO
Google crawls your site regularly. If Googlebot hits a 500 error or times out repeatedly, it affects how your pages are indexed. Persistent downtime can cause pages to drop from search results — and recovering lost rankings takes weeks or months.
One hour of downtime won't tank your SEO. A pattern of unreliability will.
The Trust Cost: Customers Who Don't Come Back
This one is hardest to measure. When a visitor hits a down site, they leave and often don't return. If they were a first-time visitor from an ad campaign or organic search, that's a wasted acquisition cost on top of the lost conversion.
For existing customers, downtime erodes trust. Support tickets start with "I tried to access my account and couldn't." Churn correlates with reliability.
How Long Before You Know Your Site Is Down?
For most small businesses and indie developers: too long. The typical discovery path is:
- A customer emails or tweets about it
- You check and confirm
- You start debugging
By the time you're aware, the site may have been down for an hour or more. If it happens overnight or on a weekend, potentially much longer.
The fix is simple: be the first to know, not the last. Automated monitoring that checks your site every few minutes and alerts you immediately cuts that gap from hours to minutes.
Common Causes of Unexpected Downtime
- Deployment gone wrong — a bad commit takes down production
- Database connection pool exhausted — traffic spike the server wasn't sized for
- Third-party service outage — payment processor, CDN, or auth provider goes down and cascades
- SSL certificate expiry — not technically "downtime" but has the same user-facing effect
- Domain/DNS misconfiguration — nameserver change doesn't propagate correctly
- Hosting provider issues — shared hosting especially is prone to resource contention
What Good Monitoring Catches
A solid website monitoring tool checks:
- Uptime — is the server responding?
- SSL validity — is the cert valid and not expiring soon?
- Broken links — are internal and external links returning errors?
- Console errors — is JavaScript throwing errors that break functionality?
- Page load performance — is the site loading slowly enough that users are abandoning?
Page Canary checks for broken pages and links, JavaScript errors and SSL problems every day and emails you when something breaks, so you can fix it before your customers notice.
Run a free scan of your site to see your current health status.