Average your incident resolution times and see how your team compares to common rapid-response targets.
One incident resolution time per line (or comma-separated), in minutes.
Mean Time to Respond
1.65 hr
Mean Time to Respond — Calculated outcome hr. Derived from your inputs via the displayed formula; use to plan.
Mean Time to Respond
99.00 min
Mean Time to Respond — Calculated outcome min. Derived from your inputs via the displayed formula; use to plan.
Incidents Analyzed
5
Incidents Analyzed — Calculated outcome. Derived from your inputs via the displayed formula; use to plan.
Response Health
Healthy — within common rapid-response targets
Response Health — Calculated outcome. Derived from your inputs via the displayed formula; use to plan.
What this means
Collect one resolution duration per incident, sum them, and divide by the count. The result is your average minutes-to-respond, also shown in hours. Shorter is generally better, but the right target depends on severity tiers and your documented SLA commitments.
Mean Time to Respond (MTTR) is the average time between an incident starting and the team resolving it. It is one of the core SecOps metrics, alongside MTBF and MTTA, and is used in SLA reporting and audit evidence.
Formula
MTTR = Σ(resolution times) ÷ number of incidents
Worked examples
FAQ
MTTR vs MTBF — what is the difference?
MTBF (mean time between failures) measures uptime between incidents; MTTR measures how long it takes to recover from each one. Both are typically part of the same reliability review.
Should MTTR include detection time?
Strictly it is time-to-respond, but many teams track MTTA (time to acknowledge) and detection time separately and review them as a chain.