MTTR is the average time between the start of an incident and service being restored, calculated across a set of incidents. The "R" stands for different things in different teams: recovery, repair, respond or resolve. These measure different intervals, so state which one you use.
Why it matters
MTTR is one of the clearest measures of how well you detect, diagnose and fix problems. Lowering it often delivers more availability than preventing every failure. It is made up of detection time, diagnosis time and repair time, and faster alerting shrinks the first part.
Example
Three incidents in a quarter lasted 8, 25 and 47 minutes:
MTTR = (8 + 25 + 47) / 3 = 26.7 minutesBecause a single long incident skews the mean, many teams also track the median, or the 90th percentile.
Common mistakes
- Starting the clock when someone notices rather than when the failure began. Use monitor data for the start time.
- Mixing "time to acknowledge" with "time to restore" in one number.
- Reporting the mean of very few incidents, which says little.
- Optimizing the number by closing incidents early or splitting one outage into several.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.