Website downtime cost is the sum of lost business value, incident labor, customer remediation, and longer-term loss attributable to the outage. Revenue per hour alone is not enough, and a generic industry multiplier is not defensible. This guide combines the formula, a fill-in worksheet, worked examples, and low/expected/high estimates on one page.
The Simple Downtime Cost Formula
At its core, calculating downtime cost is straightforward:
Downtime Cost = (Revenue per hour) × (Hours of downtime) × (Impact percentage)
Let's break that down:
Revenue per hour
Take your annual online revenue and divide by 8,760 (hours in a year):
| Annual Revenue | Revenue per Hour |
|---|---|
| $100,000 | $11.42 |
| $500,000 | $57.08 |
| $1,000,000 | $114.16 |
| $5,000,000 | $570.78 |
| $10,000,000 | $1,141.55 |
Hours of business impact
Use the incident timeline for the affected journey, not a generic annual average. A checkout failure can start later and recover earlier than the overall incident; a queue backlog can keep causing business impact after the website is technically reachable.
Impact percentage
Not all downtime affects 100% of revenue. Consider:
- Full outage: 100% impact
- Degraded performance: 30-70% impact
- Regional outage: Impact based on regional traffic
- Specific feature down: Impact based on feature usage
Add the costs revenue alone misses
Use the complete worksheet when the outage caused response work or customer impact:
Downtime cost =
((hourly revenue or hourly conversion value) × outage duration × impact percentage)
+ (engineer hourly cost × engineer hours)
+ support and communication labor
+ refunds or SLA credits
+ wasted campaign spend
+ probability-weighted churn or lost deals
For uncertain items, calculate three cases. The low case should include only observed costs, the expected case should use the most defensible assumptions, and the high case should show plausible exposure without presenting it as fact.
The Hidden Costs Most Calculators Miss
The formula above only captures direct revenue loss. The real cost is much higher.
1. Incident and productivity labor
When your site goes down, your team scrambles:
- Engineers drop everything to investigate
- Support staff handle angry tickets
- Sales can't demo the product
- Marketing campaigns get paused
Calculate loaded hourly cost multiplied by the time each responder, support agent, and stakeholder actually spent. Keep displaced roadmap work as a separate line if you can estimate it.
2. Customer acquisition cost wasted
You paid to get visitors to your site — through ads, SEO, content marketing. When they arrive and your site is down:
- Paid ads: You're still paying for clicks that bounce
- SEO traffic: Visitors won't come back tomorrow
- Referral traffic: The person who referred them looks bad
If your customer acquisition cost is $50, and 100 visitors hit a down site, that's $5,000 wasted.
3. Customer lifetime value at risk
An existing customer who can't access your service doesn't just miss one transaction. They start questioning their choice. They look at competitors. They might not come back.
Do not attach a generic churn percentage to every affected customer. Estimate the number of at-risk accounts, multiply by their expected contribution margin or customer lifetime value, and apply a probability range your customer-success data can support.
4. SEO damage
Google monitors site availability. Extended or frequent outages can:
- Drop your search rankings
- Get your site temporarily de-indexed
- Reduce crawl frequency
- Lower your domain authority over time
The SEO impact can cost you traffic for months after the outage is resolved.
5. Brand reputation damage
Some costs can't be calculated:
- Negative social media posts
- Bad reviews mentioning reliability
- Lost trust with enterprise prospects
- Competitor screenshots of your error page
Real-World Downtime Cost Examples
Let's look at what downtime costs different types of businesses:
Small e-commerce store
| Metric | Value |
|---|---|
| Annual revenue | $500,000 |
| Revenue per hour | $57 |
| Downtime (2 hours) | $114 |
| Incident labor and support | $342 |
| Observed cost | $456 |
Growing SaaS company
| Metric | Value |
|---|---|
| Monthly recurring revenue | $100,000 |
| Revenue per hour | $137 |
| Downtime (2 hours) | $274 |
| Churn risk (1% of MRR) | $1,000 |
| Engineering time (4 hours × $150) | $600 |
| Total cost | $1,874 |
Enterprise e-commerce
| Metric | Value |
|---|---|
| Annual revenue | $10,000,000 |
| Revenue per hour | $1,142 |
| Downtime (1 hour) | $1,142 |
| Incident labor, support, refunds, and campaign waste | $4,568 |
| Emergency response | $2,000 |
| Total cost | $7,710 |
Lead-generation site
Assume a paid campaign spends $150/hour, the site is down for 3 hours, two qualified leads worth $1,000 each are missed, and one engineer spends 2 hours at $75/hour:
Wasted campaign spend: $150 × 3 = $450
Missed lead value: 2 × $1,000 = $2,000
Engineering time: $75 × 2 = $150
Estimated total: $2,600
The lead value is an assumption, so record the observed campaign waste and labor separately from probability-weighted pipeline loss.
The Compounding Cost of Slow Detection
Here's what most people miss: the cost of downtime is directly related to how fast you detect it.
Consider a 1-hour outage:
| Detection Method | Time to Detect | Total Downtime | Cost Multiple |
|---|---|---|---|
| Customer complaint | 45 minutes | 1 hour 15 min | 1.25x |
| Checking manually | 30 minutes | 1 hour | 1.0x |
| 5-minute monitoring | 5 minutes | 35 minutes | 0.58x |
| 1-minute monitoring | 1 minute | 31 minutes | 0.52x |
With 1-minute monitoring, you cut your downtime (and costs) nearly in half compared to waiting for customer complaints.
How to Calculate Your Specific Downtime Cost
Use this worksheet to calculate your numbers:
Step 1: Direct revenue impact
Annual online revenue: $________
÷ 8,760 hours = Revenue per hour: $________
× Average outage duration: ________ hours
= Direct revenue loss: $________
Step 2: Add costs you can trace
Incident response labor: $________
Support and communication: $________
Refunds / SLA credits: $________
Wasted campaign spend: $________
Expected churn or lost deals: $________
For uncertain items, record low, expected, and high estimates instead of hiding uncertainty inside a multiplier.
Step 3: Annual exposure
Total downtime cost: $________
× Expected incidents per year: ________
= Annual downtime exposure: $________
The ROI of Uptime Monitoring
Now let's flip the equation. What does monitoring cost versus what it saves?
Without monitoring
- Average detection time: 30-60 minutes
- Average incidents discovered: 4-6 per year (many go unnoticed)
- No historical data for prevention
- Reactive, stressful incident response
With monitoring
- Detection time: 1-5 minutes
- All incidents captured, even brief ones
- Historical data helps prevent future issues
- Proactive, calm incident response
The math
For a business with $1,000,000 annual online revenue:
| Scenario | Annual Cost |
|---|---|
| Without faster detection (3 incidents × 2 hours × $114/hour) | $684 direct revenue exposure |
| With 5-minute detection (3 incidents × 35 min × $114/hour) | $200 direct revenue exposure |
| Direct revenue exposure avoided | $484 |
The table isolates direct revenue exposure; labor and customer costs must be added from your own records. Monitoring ROI is positive only when the expected loss avoided exceeds monitoring and response costs.
Beyond Cost: The Peace of Mind Factor
Some benefits don't show up in a spreadsheet:
- Sleep better knowing you'll be alerted instantly
- Vacation confidently with monitoring watching 24/7
- Build trust with customers through transparency
- Make better decisions with uptime data
- Prove reliability to enterprise prospects
What to Monitor for Maximum Protection
To minimize downtime costs, monitor:
Critical paths
- Homepage and landing pages — First impression for visitors
- Login and authentication — Users can't access their accounts
- Checkout/payment flow — Direct revenue impact
- Core API endpoints — Everything depends on these
- Database connectivity — Often the first thing to fail
Supporting infrastructure
- SSL certificates — Expiration causes instant "unsafe" warnings
- DNS resolution — No DNS = no website
- CDN and assets — Broken images and slow loads
- Third-party services — Payment processors, APIs, etc.
- Background jobs — Cron jobs and scheduled tasks
How Webalert Minimizes Your Downtime Costs
Webalert is built to detect issues fast and alert you instantly:
- 1-minute checks — Catch issues before customers notice
- Multi-channel alerts — Email, SMS, Slack, Discord, webhooks
- SSL monitoring — Never let a certificate expire
- Response time tracking — Catch slowdowns before they become outages
- Status pages — Keep customers informed automatically
- Incident history — Data to prevent future issues
The free plan monitors up to 3 endpoints with 10-minute checks. Paid plans offer 1-minute checks for faster detection.
See features and pricing for details.
Final Thoughts
Every minute of downtime costs money. The question isn't whether you can afford monitoring — it's whether you can afford not to have it.
Calculate your downtime costs. Compare them to the cost of monitoring. The ROI is almost always overwhelmingly positive.
Don't wait for your next outage to do the math.
Stop losing money to undetected downtime
Start monitoring for free with Webalert →
Explore features or see pricing.
Free forever. 1-minute detection. ROI from day one.