Skip to content
BENIBIX Learn

MTBF vs MTTR

People read the two numbers as one score for reliability, and they measure different things. MTBF is how long a system runs, on average, before it breaks. MTTR is how long it takes to bring it back. A service can break often but recover in seconds, or break rarely and stay down for a day.

Infrastructure📟 Reliability

Mean Time Between Failures (MTBF)

How long a system runs before it breaks again. It is the mean of many.

Mean time between failures is the average time a system runs before it breaks again. You add up the running time and divide it by the number of failures. A higher number means failures come less often. Together with mean time to recovery, it shows how reliable a system is. One says how often it breaks, and the other says how fast it comes back.

Example
Jack's service failed 4 times in 2,000 hours of running. Its mean time between failures is 500 hours.
Why it matters
It tells you how often to expect trouble. Fewer breaks mean fewer pages and fewer unhappy users.
Full entry
Infrastructure📟 Reliability

Mean Time to Recovery (MTTR)

The average time it takes to fix a service that broke. Lower is better.

Mean time to recovery is the average time from when a service breaks to when it works again. You add up how long each incident lasted. Then you divide by the number of incidents. The R can mean recovery, repair or restore, so say which you mean. A falling MTTR shows a team is getting faster at fixing things.

Example
Jack's team had three incidents this quarter. They lasted 20, 40 and 60 minutes, so the MTTR is 40 minutes.
Formula
MTTR = total time down ÷ number of incidents
Why it matters
Failures will happen. How fast you recover is often easier to improve than how often you fail.
Full entry

In one line

Mean Time Between Failures (MTBF)
How long a system runs before it breaks again. It is the mean of many.
Mean Time to Recovery (MTTR)
The average time it takes to fix a service that broke. Lower is better.