Measure delays across alerts, diagnosis, fixes, and validation. Track MTTR, outage cost, and phase balance. Act faster with data-driven reliability decisions every release cycle.
Enter average minutes for one incident. The incidents count is used for period estimates.
These examples show how different incident profiles can affect recovery time and downtime cost.
| Incident Type | Detection | Diagnosis | Fix | Verification | Deployment | Total Recovery | Cost / Min | Total Cost |
|---|---|---|---|---|---|---|---|---|
| API outage | 6 min | 15 min | 28 min | 12 min | 10 min | 92 min | $180 | $16,560 |
| Database failover | 4 min | 12 min | 20 min | 10 min | 7 min | 70 min | $150 | $10,500 |
| Rollback after release | 3 min | 10 min | 18 min | 9 min | 6 min | 60 min | $220 | $13,200 |
It measures how long a software service takes to recover after a failure begins. This includes detection, response, diagnosis, repair, validation, deployment, and stabilization time.
Yes, in many engineering teams this calculator estimates MTTR, or mean time to recovery. It builds that estimate from the detailed phases that make up an outage response.
A single total hides bottlenecks. Phase timing shows whether delays come from alerting, diagnosis, implementation, deployment, or stabilization, which makes improvement work more targeted.
Use lost revenue, support load, engineering time, penalties, and productivity loss. Many teams start with a conservative value, then refine it using incident review data.
These are the minutes that could be reduced through scripts, runbooks, auto-remediation, rollback pipelines, failover orchestration, or better monitoring workflows.
It shows the share of total time spent on direct restoration work: fixing, verifying, and deploying. A low value often suggests waiting, coordination, or slow diagnosis.
Yes. That is often the best approach. Pull average phase times from postmortems or incident reviews to create a realistic baseline for forecasting and improvement planning.
It helps prioritize the phases that create the biggest delay and cost. Teams can then invest in faster alerting, clearer runbooks, automation, testing, and deployment safety.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.