How to Calculate the Cost of Website Downtime
The cost of website downtime should be estimated from contribution margin and additional incident expense for the affected period, not simply average daily revenue. Include permanently lost orders or leads, acquisition spend sent to a broken journey, response and recovery work, compensation, manual reconciliation, and measurable downstream effects.
Distinguish a total outage from a broken checkout, one failed payment method, regional access, or degraded conversion. A site can return HTTP 200 while the business cannot sell.
At a glance
Use this first-pass equation:
Lost contribution = normal retained orders per minute × contribution per order × affected minutes × permanently lost share.
Then add:
- wasted acquisition spend;
- incident response and recovery cost;
- compensation and operational rework;
- downstream effects supported by cohort or customer data.
Present a low, working, and high scenario. False precision is less useful than an explicit range with evidence.
Define the failure mode
| Scenario | Customer experience | Likely business effect |
|---|---|---|
| Full outage | Store cannot be reached | Most online activity stops |
| Checkout outage | Browsing works; order cannot complete | New orders are lost or delayed |
| One payment method fails | A segment receives declines | Loss depends on method share and alternatives |
| Lead delivery fails | Success message appears | Hidden lead loss and slow response |
| Inventory or price is stale | Order uses wrong availability or price | Cancellation, support, and margin risk |
| Severe latency | Some users abandon | Conversion degrades rather than reaches zero |
| Analytics fails | Sales continue | Decisions and attribution become unreliable |
The calculation must follow the affected business journey.
Step 1: build a normal baseline
Compare the incident with genuinely similar periods:
- same day of week and local time;
- similar campaign and traffic mix;
- comparable promotion and inventory state;
- several historical periods rather than one;
- segmentation by device or region when relevant.
Capture sessions, checkout starts, orders created, payments succeeded, orders retained, net revenue, contribution, and acquisition spend in 15-minute or appropriate intervals.
Step 2: use contribution, not gross revenue
A sale that never occurred does not consume all of its variable product and fulfilment costs. Use the contribution framework in Ecommerce Unit Economics.
Gross revenue may still be useful for communicating scale, but label it separately from estimated economic loss.
Step 3: separate lost, delayed, and shifted demand
Customers may:
- abandon permanently;
- return after recovery;
- buy through an app, marketplace, store, or sales team;
- submit a support-assisted order;
- create a duplicate attempt.
Calculate the gross shortfall against baseline, then subtract verified late or channel-shifted orders. If the recovery share is unknown, show a range.
Step 4: add incident costs
| Cost | Evidence |
|---|---|
| Wasted acquisition | Spend directed at the affected journey |
| Engineering and operations | Actual hours and agreed internal rate |
| Customer support | Incremental contacts and handling time |
| Compensation | Credits, refunds, expedited delivery |
| Manual recovery | Order recreation, payment and inventory reconciliation |
| External services | Forensics, emergency vendors, temporary capacity |
| Transaction costs | Duplicate operations and unrecovered fees |
Do not invent a large reputational number. Measure observable effects such as cancellations, repeat purchase changes in the affected cohort, complaints, or review volume.
Step 5: produce a range
Low case
- verified contribution shortfall only;
- documented additional costs;
- recovered and shifted demand removed.
Working case
- baseline-adjusted contribution shortfall;
- evidence-based lost share;
- acquisition, response, and compensation costs.
High case
- plausible peak-period shortfall;
- lower customer return rate;
- extended recovery work;
- uncertain downstream effects shown separately.
Worked example
A store normally retains 18 orders per hour in the affected window. Contribution per order is $34. Checkout fails for 40 minutes. Order IDs and later behaviour suggest that 45–65% of the missing demand did not return.
Estimated lost contribution:
- low: 18 × 0.667 × $34 × 0.45 = approximately $184;
- high: 18 × 0.667 × $34 × 0.65 = approximately $265.
Add $400 of acquisition spend and $1,200 of response and recovery work. The direct working range is approximately $1,784–$1,865.
These are illustrative values, not an industry benchmark.
Copyable impact card
| Field | Value |
|---|---|
| Incident | |
| Affected journey | |
| Start and end in UTC | |
| Comparison periods | |
| Normal retained orders/leads per minute | |
| Actual orders/leads | |
| Contribution per unit | |
| Verified late or shifted operations | |
| Low estimate | |
| Working estimate | |
| High estimate | |
| Acquisition spend | |
| Response and recovery | |
| Compensation | |
| Evidence links | |
| Confidence | High / medium / low |
Use cost to prioritise reliability
Estimate annual exposure:
Expected annual risk = incident probability × typical financial impact.
A hidden form failure that lasts a day several times a year may deserve more investment than a rare five-minute homepage outage. Use the calculation to set journey-monitoring frequency, severity, failover priorities, ad-pausing rules, and load-test budget.
Common mistakes
- multiplying daily gross revenue by outage hours;
- assuming every missing order is permanently lost;
- ignoring partial or regional failures;
- inventing an unsupported reputation cost;
- comparing a campaign peak with an ordinary day;
- including duplicate or test orders;
- forgetting acquisition and reconciliation work;
- drawing a precise conclusion from broken analytics.
FAQ
What if analytics failed during the outage?
Use OMS orders, payment attempts, CRM leads, server logs, ad spend, support records, and comparable periods. Widen the range and lower the confidence rating.
Should future customer lifetime value be included?
Only as a separate scenario supported by a credible cohort model and an identifiable affected group. Do not mix speculative lifetime value with verified direct loss.
How do I value downtime for a non-commerce site?
Choose a business unit such as a qualified lead, booking, document submission, activated user, or completed workflow. Estimate its contribution and how much demand can be recovered later.
Sources and further reading
- Google SRE: Service Level Objectives
- Google SRE: Monitoring Distributed Systems
- Stripe: business impact of failed payments
Reviewed: 10 August 2026.
Next: build an ecommerce operations dashboard and define incident severity.
Pingvera provides independent incident timing, affected-journey evidence, and recovery confirmation for a defensible business-impact estimate.
Know about problems before your customers do
Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.
Start freeRead next: Pingvera Webhook to Help Desk Integration · Ecommerce Operations Dashboard: KPI Template.