Course contentsShow
← System Design
Lesson 1324 of 1,91933. Reliability Engineering FoundationsFree lesson

Mean Time To Repair (MTTR)

Understand MTTR as a measure of recovery speed and its critical impact on overall system availability.

Mean Time To Repair (MTTR)

What you'll learn: How MTTR measures your system's recovery speed and why minimizing it is crucial for overall availability.

The Core Idea

Mean Time To Repair (MTTR) is the average time it takes to restore a service or component to full operation after a failure occurs. While MTBF (which you just learned) tells you how often things break, MTTR tells you how quickly you bounce back when they do.

Think of it like this: MTBF is how long your car runs between breakdowns. MTTR is how long you're stranded on the roadside waiting for repairs. Both matter, but if you can get back on the road in 5 minutes versus 5 hours, your overall travel reliability changes dramatically.

Why MTTR Is Critical

MTTR directly impacts your system's availability. Remember the availability formula:

Availability = MTBF / (MTBF + MTTR)

Notice that reducing MTTR improves availability just as effectively as increasing MTBF. Sometimes fixing things faster is more practical than preventing failures entirely—especially when you embrace that 100% availability is unrealistic.

What MTTR Includes

MTTR encompasses the entire recovery timeline:

  • Detection time: How long until you notice the failure
  • Diagnosis time: Identifying the root cause
  • Repair time: Implementing the fix (rollback, restart, patch)
  • Verification time: Confirming the system is healthy again

This is why good monitoring, clear runbooks, automated rollbacks, and practiced incident response are SRE fundamentals—they all slash MTTR.

Real Impact

A system with 99.9% availability allows ~43 minutes of downtime per month. If your MTTR is 60 minutes, a single incident blows your entire error budget. Reducing MTTR to 10 minutes gives you breathing room for multiple incidents.

Key Takeaway: MTTR measures how fast you recover from failures; minimizing it through automation, monitoring, and practiced incident response is essential for meeting availability targets and preserving your error budget.