Reliability in ITIL® 5 Explained

What Is Reliability in ITIL®?

Reliability is the measure of how long a service, component, or configuration item can perform its agreed function without interruption. It answers a narrow, specific question: once something is working, how long does it keep working before something goes wrong? That's distinct from asking how available a service is overall, or how quickly it recovers when it fails.

Reliability, Maintainability, and Serviceability

Availability, as a warranty factor in ITIL®, is shaped by three connected aspects. Reliability measures how long something runs without interruption. Maintainability measures how quickly and effectively a failed service or component can be restored to normal working after a failure. Serviceability measures how effectively third-party suppliers deliver the services or components they're responsible for. Together, these three aspects feed into the broader practice of Availability Management, which is concerned with ensuring services are available when the business needs them.

Reliability vs Availability

It's worth being precise about the difference between reliability and availability, since they're closely related but not the same thing. Availability is the overall outcome — is the service accessible and usable when required. Reliability is one of the specific factors that feeds into that outcome, focused narrowly on freedom from interruption. A service could technically have high uptime numbers overall while still suffering from frequent, brief interruptions that hurt its reliability specifically.

Real-World Example

An online banking platform stays technically "up" almost all the time, but experiences frequent brief outages of a minute or two, several times a week, due to an unstable component. Its overall availability percentage might still look reasonably strong, but its reliability is poor — the service keeps interrupting itself even though it's rarely down for long stretches. Availability Management would flag reliability specifically as the area needing attention, separate from asking whether the platform is generally accessible.

Why This Matters

Understanding reliability as a distinct concept matters because:

• The exam tests recognition of reliability, maintainability, and serviceability as separate, specific aspects of availability
• "Available" and "reliable" aren't interchangeable words for the same idea
• It connects directly to Availability Management, a core, frequently tested ITIL® practice

Common Exam Mistakes

The most common mistake is using "reliability" and "availability" interchangeably. Availability is the overall outcome; reliability is one specific contributing factor focused on freedom from interruption.

A second mistake is confusing reliability with maintainability. Reliability is about how long something runs before failing; maintainability is about how quickly it's restored once it does fail. They measure different points in the same failure cycle.

Memory Trick

Think:

Reliability — how long before it breaks.

Maintainability — how fast it's fixed once it does.

Serviceability — how well suppliers hold up their end.

All three feed into availability, but none of them is availability itself.

Key Takeaways

• Reliability is the measure of how long a service or component performs without interruption.
• It's one of three aspects — alongside maintainability and serviceability — that determine overall availability.
• Reliability is distinct from availability itself, which is the broader outcome of whether a service is accessible when needed.
• Maintainability measures recovery speed after failure; reliability measures freedom from interruption before failure.
• Reliability is a component of Availability Management, a frequently tested ITIL® practice.

One Practice Question