Rex says
Everyday utility math — the kind you'd otherwise pull up four browser tabs for. I keep it to one clean answer.
Try a scenario
Click to load — tweak from there.Inputs
Result
Annual savings from MTTR reduction
$1,512,000
MTTR reduction
63.6%
Current annual incident cost
$2,376,000
Projected annual incident cost
$864,000
Psst — share this and help Rex grow
One click, a permanent link with your numbers baked in.
How to use this
- 1Enter incidents per year.
- 2Enter current mttr (minutes).
- 3Enter target mttr (minutes).
- 4Enter cost per minute of downtime ($).
- 5Read your annual savings from mttr reduction on the right — it updates as you type.
- 6Hit Share to keep the scenario or send it to someone.
About this calculator
Mean time to recovery (MTTR) is the average time from an incident starting to service being fully restored, and it's one of the four DORA metrics correlated with high-performing engineering teams. This calculator takes your current MTTR and incident frequency, applies your incident cost per minute, and computes both current annual incident cost and the savings from a target MTTR reduction, so investment in observability, runbooks, or automated rollback tooling can be justified with a real number instead of a vague 'faster is better' argument. It splits MTTR conceptually into detection time (how long until you know something's wrong) and repair time (how long to actually fix it once known) because they respond to different investments — better monitoring and alerting cuts detection time, while better runbooks, feature flags, and automated rollback cut repair time, and most teams have far more slack in detection time than they realize.
Worked example
Using the values the calculator loads with:
Inputs
- Incidents per year: 24
- Current MTTR: 55 minutes
- Target MTTR: 20 minutes
- Cost per minute of downtime: 1800 $
Results
- Annual savings from MTTR reduction: $1,512,000
- MTTR reduction: 63.6%
- Current annual incident cost: $2,376,000
- Projected annual incident cost: $864,000
What each field means
Inputs
- Incidents per year
- The incidents per year used in the calculation. Starts at 24 so you have a working example on load.
- Current MTTR (minutes)
- The current mttr used in the calculation, measured in minutes. Starts at 55 minutes so you have a working example on load.
- Target MTTR (minutes)
- The target mttr used in the calculation, measured in minutes. Starts at 20 minutes so you have a working example on load.
- Cost per minute of downtime ($)
- The cost per minute of downtime used in the calculation, measured in $. Starts at 1800 $ so you have a working example on load.
Results
- Annual savings from MTTR reduction
- Returned as a money amount in US dollars and shown as the headline result. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- MTTR reduction
- Returned as a percentage. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Current annual incident cost
- Returned as a money amount in US dollars. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Projected annual incident cost
- Returned as a money amount in US dollars. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
FAQ
What counts as good MTTR for the industry?
DORA's State of DevOps research bands elite performers at under 1 hour MTTR, high performers under 1 day, medium performers under 1 week, and low performers over 1 week or even 1 month. The bands matter more than the exact minute count — moving from 'medium' to 'high' typically has a bigger business impact than shaving a few minutes off an already-fast MTTR.
Where should I invest first: detection or repair time?
Time your last 10-15 incidents from actual failure onset to first alert versus first alert to resolution — most teams find detection eats 30-50% of MTTR and is cheaper to fix (better alerting thresholds, synthetic monitoring) than repair time, which often requires structural changes like feature flags or one-click rollback pipelines. Fix whichever phase is the larger share first.
Does incident count go down as MTTR goes down?
Not directly — MTTR and incident frequency are different metrics driven by different causes (MTTR by response tooling and process, frequency by code quality and change failure rate). But teams that invest in fast, safe rollback mechanisms to cut MTTR often see frequency drop too, because the same tooling that speeds recovery also makes it cheaper to catch and revert bad changes before they escalate.
Accuracy and limitations
- Estimates assume standard, average conditions — local rules, pricing, and materials vary.
- Results are rounded for readability; add a buffer before ordering, booking, or committing.
- Double-check anything with a real cost attached against a local quote.
Related tools
Cite this calculator
Writing about this topic? Grab a citation — every link helps keep these tools free.
RevenueLab. (2026). MTTR Impact Calculator. Retrieved from https://www.revenuelab.fyi/toolbox/mttr-impact-calculator
<p>Source: <a href="https://www.revenuelab.fyi/toolbox/mttr-impact-calculator" target="_blank" rel="noopener">MTTR Impact Calculator — RevenueLab</a> (2026).</p>
Source: [MTTR Impact Calculator — RevenueLab](https://www.revenuelab.fyi/toolbox/mttr-impact-calculator) (2026).