Estimated Financial Impact
This estimator helps you put a dollar value on website downtime. Use it to see how much lost availability costs your business over a day, month, or year. The math is simple and transparent.
What you need
- Uptime percentage (for example 99.9)
- Analysis period (days — e.g., 1, 30, 365)
- Estimated revenue loss per minute of downtime
- Number of incidents in the period (optional)
- Cost per incident for staff time and recovery (optional)
- Any fixed losses or SLA penalties (optional)
Key formulas
- Total minutes in period = days × 24 × 60
- Downtime fraction = 1 − (uptime ÷ 100)
- Downtime minutes = Total minutes × Downtime fraction
- Revenue loss = Downtime minutes × Revenue loss per minute
- Incident cost = Number of incidents × Cost per incident
- Total estimated cost = Revenue loss + Incident cost + Other fixed losses + SLA penalties
Worked example
Inputs
- Uptime = 99.9%
- Period = 30 days
- Revenue loss per minute = $50
- Number of incidents = 2
- Cost per incident = $300
- Other fixed losses = $0
Calculation
- Total minutes = 30 × 24 × 60 = 43,200 minutes
- Downtime fraction = 1 − 0.999 = 0.001
- Downtime minutes = 43,200 × 0.001 = 43.2 minutes
- Revenue loss = 43.2 × $50 = $2,160
- Incident cost = 2 × $300 = $600
- Total estimated cost = $2,160 + $600 + $0 = $2,760
Practical notes
- Use a conservative revenue loss per minute. Include lost sales, lost conversions, and reputational effects if you can estimate them.
- Incident cost covers staff time, overtime, support refunds, and urgent third-party costs.
- SLA penalties are often negotiated and should be included as a fixed or percentage cost if they apply.
- Round results and present ranges. Estimates are useful for planning, not exact auditing.
How to reduce uptime cost
- Improve monitoring and alerting to reduce incident length.
- Add redundancy (CDN, multi-region hosting, failover) to reduce downtime probability.
- Run disaster recovery drills to shorten mean time to repair.
- Negotiate SLAs and careful vendor selection to reduce penalties.
- Invest in caching and graceful degradation to limit user-facing impact.
Frequently Asked Questions
What uptime percentage should I aim for?
It depends on your business. E-commerce and finance sites often target 99.9% or higher. Mission critical services aim for 99.99% or 99.999% where possible.
Why is a small uptime drop expensive?
Even a 0.1% drop over a month can add up to dozens of minutes of downtime. If each minute costs a lot, small differences matter.
How do I estimate revenue loss per minute?
Start with average revenue per minute = monthly online revenue ÷ minutes in month. Adjust for conversion impact and brand damage if needed.
Should I include indirect costs like brand damage?
Yes if you can estimate them. They are harder to measure but can be large for repeated outages.
Can I use this for mobile app downtime or APIs?
Yes. Use the same approach and pick a revenue or cost number that reflects lost transactions and engineering response costs for that product.