How many nines does your service need?

Availability targets are often copied from the last project or set to whatever sounds safest. Both are expensive mistakes. Here is how we work out the right number.

Start with the numbers in plain terms

An availability target is a promise about downtime. It helps to state it that way, because "four nines" means little to the person who has to fund it.

TargetDowntime a yearDowntime a month
99.9%8.8 hours44 minutes
99.95%4.4 hours22 minutes
99.99%53 minutes4 minutes
99.999%5.3 minutes26 seconds

Each step down the table usually means a step up in architecture: more zones, then more regions, then automated failover that has to be tested regularly. Cost and complexity rise much faster than the number does.

Ask what an outage costs, and when

The useful question is what happens to users if the service is down for an hour. For a service used in office hours to book an appointment, the answer is often that people come back later. For one that supports emergency response, it is very different.

Timing matters as much as duration. Twenty minutes at three in the morning and twenty minutes on deadline day are not the same event. If the service has peaks, set the target around them and plan maintenance outside them.

Check what you depend on

A service is rarely more available than the things it needs to work: an identity provider, a payment service, a legacy system behind an API. If a critical dependency offers 99.9%, promising 99.99% on top of it is a promise you can't keep unless you design a way to keep working without it.

Set recovery targets alongside it

Availability says how often you can be down. It says nothing about how much data you can lose or how long recovery takes. Agree a recovery time objective and a recovery point objective at the same time, and make sure backups and restores are tested against them. An untested restore is a hope, not a plan.

Write the decision down

Record the target, the options you considered, what each would have cost and why you chose as you did. When someone asks in two years why the service runs in one region, the answer will be on a page. When circumstances change, you will know which assumption to revisit.

Then measure it

A target nobody measures is decoration. Define how availability is calculated, from the user's point of view where you can, and report it. If you consistently beat the target by a wide margin, you may be paying for more than you need.

Facing this on your programme?

We're happy to talk it through, with no obligation.