TOOLTIKI Lovable tool, really free
Network Availability

Uptime percentage calculator

Uptime target
%
Downtime a year 8h 45m
period × (1 − uptime)
Allowed downtime
Hours a year 8.76
Per 30-day month 43m 12s
Per week 10m 5s
Per day 1m 26s
Commonly called three nines
Note An SLA usually excludes scheduled maintenance, so the contractual figure and the figure your users experience are different numbers.
Local · monthly is the number that usually binds

Three nines (99.9%) allows 8 hours 46 minutes of downtime a year. Four nines allows 52 minutes. Five nines allows 5 minutes 15 seconds — less than a single reboot, which is why five nines requires redundancy rather than reliability.

Advertisement
320 × 100

Converts an uptime percentage into the downtime it allows across a year, month, week and day — the numbers behind an SLA.

How to use the uptime percentage calculator

1 Enter the uptime percentage.
2 Read the downtime it allows per year, month, week and day.

The nines are worth knowing by heart because each one costs roughly ten times the last. Three nines allows 8 hours 46 minutes a year and is achievable with careful operations on a single system. Four nines allows 52 minutes and needs redundancy — that is less than one unplanned reboot. Five nines allows 5 minutes 15 seconds across a whole year, which is less than most systems take to restart, so it can only be reached by never having a single point of failure at all.

The monthly figure matters more than the annual one, because most SLAs are measured and credited monthly. Three nines monthly is 43 minutes, and one bad afternoon breaches it even though the annual figure still looks fine. An SLA that is measured monthly and quoted annually is measuring the stricter thing.

Read what the SLA excludes, because it is usually where the number comes from. Scheduled maintenance is almost always excluded, and sometimes so are provider-network problems, DDoS and anything the customer’s own configuration caused. That is why a provider can report 99.99% for a month in which you were down for two hours — the contractual figure and the figure your users experienced are genuinely different numbers, and only one of them shows up in a credit.

One compounding trap: dependencies multiply. A service at 99.9% that depends on three other services each at 99.9% has a realistic ceiling near 99.6%, because any one of them failing takes you down.

Questions

8 hours 46 minutes a year, or 43 minutes a month.

ITIL — service level managementGoogle SRE Book — service level objectives
Advertisement
300 × 250
Was this tool any good?
INTERNAL SIGNAL ONLY · WE USE IT TO FIND TOOLS WORTH REBUILDING