IT Incident Cost Calculator
Calculate the true cost of IT incidents including revenue loss, labor, reputation damage, and customer churn. Get direct cost, indirect cost, and annualized risk exposure in seconds.
IT Incident Cost Calculator
Calculate direct and indirect costs for a single incident and your annualized risk exposure.
Determines revenue impact multiplier
Detection to resolution (MTTD + MTTR)
Used for churn cost estimation
Annual revenue / 8,760 as starting point
Engineers, analysts, managers on bridge
How often this severity occurs annually
Industry Incident Cost Benchmarks
P1 incident cost per hour and response metrics by industry. Use as a sanity check for your revenue-per-hour inputs.
| Industry | P1 Cost / Hour | Typical MTTR | P1s per Year |
|---|---|---|---|
| E-commerce | $220,000 - $500,000 | 2.5 hours | 4-8 |
| Financial Services | $350,000 - $900,000 | 1.8 hours | 2-5 |
| Healthcare | $180,000 - $400,000 | 3.2 hours | 3-7 |
| SaaS / B2B | $80,000 - $250,000 | 3.8 hours | 6-12 |
| Media / Streaming | $150,000 - $400,000 | 2.1 hours | 4-10 |
| Retail | $90,000 - $220,000 | 4.5 hours | 5-15 |
Sources: Gartner IT downtime research, PagerDuty State of Digital Operations, IBM Cost of Downtime Report 2025. Ranges reflect 25th-75th percentile for organizations with $50M - $1B annual revenue.
Incident Cost FAQ
How much does the average IT incident cost?
The average cost of a major IT incident (P1/P2) ranges from $500,000 to $5 million when direct and indirect costs are included, according to industry research from Gartner, IBM, and PagerDuty. The cost varies enormously by industry, revenue size, and duration. A one-hour P1 outage at a large e-commerce company might cost $500,000, while the same duration at a small SaaS company might cost $50,000. The annualized cost is often the more useful metric for risk planning.
What are the direct costs of an IT incident?
Direct costs are the immediate, quantifiable costs: revenue loss during the outage (calculated as revenue-per-hour times duration times severity impact), and labor cost for the response team (engineers, managers, analysts on the incident bridge, often working overtime during extended incidents). Direct costs are typically 40-60% of total incident cost, with indirect costs making up the remainder.
What are indirect incident costs?
Indirect costs accrue after the incident is resolved and include: customer churn from dissatisfied users (typically 2-8% of affected customers depending on severity), brand and reputation damage (typically 10-25% of direct costs for P1 incidents), regulatory and compliance costs (potential fines, mandatory disclosures, audit costs), and productivity loss from post-incident work (postmortems, remediation, documentation). Indirect costs are harder to measure but are real and significant.
How do I calculate revenue loss from an outage?
The simplest approach: (Annual Revenue / 8,760 hours) x Outage Duration in Hours x Impact Percentage. Impact percentage varies by severity: P1 (complete outage) = 100%, P2 (major degradation) = 50-70%, P3 (partial impact) = 20-30%, P4 (minor issue) = 5-10%. For e-commerce, transaction-level data provides more accurate estimates. For SaaS, monthly recurring revenue divided by hours is a common baseline.
What is MTTR and how does it affect incident cost?
Mean Time to Recovery (MTTR) measures the average duration from incident detection to resolution. Every additional hour of MTTR multiplies cost linearly for revenue loss and roughly 1.5x for labor (overtime and fatigue premium). Reducing MTTR from 4 hours to 2 hours does not just halve costs - it eliminates the overtime premium, reduces reputation damage window, and limits the churn exposure. Organizations that invest in observability and runbooks typically achieve MTTR 40-60% lower than those without.
How do I reduce the cost of IT incidents?
The highest ROI investments: (1) Observability and monitoring - faster detection directly reduces MTTR and total cost; (2) Incident runbooks and playbooks - pre-documented response steps reduce cognitive load during incidents and cut resolution time 30-50%; (3) Chaos engineering and game days - pre-finding failure modes prevents costly production incidents; (4) On-call rotation and escalation automation - ensures the right people are engaged immediately; (5) Post-incident review culture - systematic learning prevents recurrence. See the Reduce Costs page for detailed strategies.