Skip to content
Built in Lahore, PakistanHow we check the math
mathbehind

Uptime and SLA Downtime Calculator

Turn an uptime percentage like 99.9% into the downtime it allows per year, month, week and day.

By Muhammad Ahmad, Software EngineerLinkedIn· figures checked

Your numbers

%

For example 99.9 (three nines) or 99.99 (four nines).

Allowed downtime per year

8h 45m 36s

Per month
43m 48s
Per week
10m 5s
Per day
1m 26s
Minutes per year
525.6
The math behind it
  1. Allowed downtime share

    100% − 99.9%equals0.1%

  2. Per year

    0.1% × 365 d × 24 hequals8h 45m 36s

  3. Per day

    0.1% × 24 hequals1m 26s

Uptime targets are written as percentages, but what you actually need to know is how much downtime they allow. The difference between 99.9% and 99.99% sounds tiny, yet it is the difference between about 8 hours and about 53 minutes of downtime a year.

Figures checked by Muhammad Ahmad against AWS: Service Level Agreements, Google Cloud: SLAs and Azure: SLA for services. Prices and rules change, so confirm with the official source before relying on them. How we check the math

How it works

Subtract the uptime percentage from 100% to get the share of time you are allowed to be down. Multiply that by the length of the period.

The year is 365 days. A month is one twelfth of a year, about 30.4 days, and a week is 7 days. Some SLAs define a month as the actual calendar month, so check your contract if the exact minutes matter.

Each extra nine cuts allowed downtime by a factor of ten. 99% allows about 3.65 days a year, 99.9% about 8.8 hours, 99.99% about 53 minutes, and 99.999% about 5 minutes.

A worked example

A 99.9% uptime target allows 0.1% downtime: 8h 45m 36s over a year, 43m 48s in a month, 10m 5s in a week, or about 1m 26s a day.

More examples

99.99% uptime allows 52 minutes 34 seconds of downtime a year, 4 minutes 23 seconds a month and about 8.6 seconds a day.

The steps between common targets are bigger than they look. 99.5% allows 1 day 19 hours 48 minutes of downtime a year, about 3 hours 39 minutes a month. 99.95% allows 4 hours 22 minutes 48 seconds a year, about 21 minutes 54 seconds a month.

At five nines, 99.999%, the allowance is 5 minutes 15 seconds a year, under a second a day. A single slow deployment or restart can use a whole year's budget, which is why five-nines systems rely on automatic failover rather than people responding to alerts.

Common mistakes

  • Promising the same uptime as your providers while depending on several of them.
  • Ignoring maintenance exclusions in the SLA.
  • Measuring per year when the agreement measures per calendar month.
  • Treating an SLA credit as insurance for lost revenue.
  • Choosing a target without checking what your own on-call process can respond to: at 99.99%, a monthly budget of about 4 minutes is shorter than most people take to acknowledge an alert.

Questions people ask

Does planned maintenance count as downtime?

It depends on the agreement. Many SLAs exclude scheduled maintenance announced in advance, which is why the fine print matters as much as the percentage.

How do dependencies affect my uptime?

If your service needs two systems that each have 99.9% uptime, and either one failing takes you down, your combined uptime is about 99.8% (0.999 × 0.999). Every hard dependency lowers the uptime you can realistically promise.

What is the difference between an SLA, SLO and SLI?

An SLI is the measurement, such as the share of successful requests. An SLO is your internal target for it. An SLA is the promise in a contract, usually with refunds or credits if you miss it, and is normally set a little looser than the SLO.

How much downtime is 99.9% uptime?

About 8.76 hours a year, 43.8 minutes a month or 10.1 minutes a week. Each extra nine divides the allowed downtime by ten.

What does five nines mean?

99.999% uptime, which allows about 5.26 minutes of downtime a year. It's expensive to achieve and usually needs redundancy across regions.