Uptime Math

SLA Uptime Calculator

How Much Downtime Does 99.9%, 99.99%, 99.999% Allow?

Updated April 2026

Calculator Inputs

$

Downtime Allowances at 99.900% Uptime

Per Day

1.44 min

Per Week

10.08 min

Per Month

43.80 min

Per Quarter

2.19 hr

Per Year

8.76 hr

Annual Exposure at This SLA Tier

$2,628,000

If you have 526 minutes of downtime per year and each hour costs you $300,000

Complete SLA Downtime Allowance Table

Uptime %NinesPer YearPer MonthPer WeekPer Day
90%1 nine52,560 min (36.5 days)4,380 min1,008 min144 min
95%1.3 nines26,280 min (18.25 days)2,190 min504 min72 min
99%2 nines5,256 min (3.65 days)438 min100.8 min14.4 min
99.5%2.3 nines2,628 min (1.82 days)219 min50.4 min7.2 min
99.9%3 nines525.6 min (8h 46m)43.8 min10.08 min1.44 min
99.95%3.3 nines262.8 min (4h 23m)21.9 min5.04 min0.72 min
99.99%4 nines52.56 min4.38 min1.01 min8.64 sec
99.999%5 nines5.26 min26.3 sec6.05 sec0.86 sec
99.9999%6 nines31.5 sec2.63 sec0.60 sec0.086 sec

How to Calculate Downtime From an Uptime Percentage

An SLA percentage is a promise about uptime. The allowed downtime is simply the remaining fraction multiplied by the length of the period:

Allowed downtime = (1 - uptime %) × period length

The only constants you need are the minutes in each period: a year is 525,600 minutes (365 × 24 × 60) and a day is 1,440 minutes.

Worked example: 99.9% uptime

  • Downtime fraction: 1 − 0.999 = 0.001 (0.1%)
  • Per year: 0.001 × 525,600 = 525.6 minutes (about 8 hours 46 minutes)
  • Per day: 0.001 × 1,440 = 1.44 minutes

Add a nine and the allowance shrinks by 10×: 99.99% is 0.0001 × 525,600 = 52.56 minutes per year, and 99.999% is 5.26 minutes per year. The table above applies this same formula across every tier from 99.5% to 99.9999%, per year, month, week, and day.

What Each Tier Means in Practice

99.9% (Three Nines)

About 8 hours 46 minutes of downtime per year. This sounds good until you realize that 8 hours could be one single Saturday afternoon outage. For most production systems, this means: single-region deployment with solid monitoring and manual escalation. Most shared hosting and basic cloud deployments fall into this tier naturally.

99.99% (Four Nines)

Only 52 minutes of downtime per year. That is less than one hour, spread across all incidents. This requires genuinely automated failover - you cannot manually respond to every incident in under 5 minutes reliably. Multi-AZ with database replication and load balancer health checks is the minimum architecture. This is the standard for most SaaS products with paying B2B customers.

99.999% (Five Nines)

5 minutes 16 seconds per year. Effectively zero planned maintenance is possible at this tier. Multi-region active-active architecture is required. This is what financial exchanges, telephone networks, and critical healthcare systems target. The cost delta from four nines to five nines is typically 10-20x in infrastructure spend.

SLA Tier to Architecture Map

SLA TierArchitecture RequiredAdditional Cost Est.
99.9%Single region, multi-AZ with monitoring~$5K-20K/yr extra
99.99%Multi-AZ with automated failover, DB replication, load balancing~$50K-200K/yr extra
99.999%Multi-region active-active, global load balancing, chaos engineering~$500K-2M/yr extra

Architecture costs are rough estimates for typical cloud deployments on AWS/Azure/GCP. Actual costs depend on scale, region count, and data volume.

Frequently Asked

What is 99.9% uptime in minutes per year?
99.9% uptime (three nines) allows 525.6 minutes of downtime per year - approximately 8 hours and 46 minutes. That is 43.8 minutes per month, 10.08 minutes per week, and 1.44 minutes per day.
What is 99.99% uptime in minutes per year?
99.99% uptime (four nines) allows 52.56 minutes of downtime per year - approximately 52 minutes and 34 seconds. That is 4.38 minutes per month, 1.01 minutes per week, and 8.64 seconds per day.
What is 99.999% uptime in minutes per year?
99.999% uptime (five nines) allows only 5.26 minutes of downtime per year. That is 26.3 seconds per month and under 6 seconds per week. Achieving five nines requires multi-region active-active architecture with automated failover and chaos engineering.
Why is the difference between 99.9% and 99.99% significant?
The difference between 99.9% and 99.99% is exactly 10x: going from 525 minutes/year of allowable downtime to 52 minutes/year. For a mid-size enterprise at $300,000/hr, that 10x improvement eliminates approximately $2.3M in annual downtime risk. The architecture upgrade typically costs $50K-$200K per year in additional infrastructure - a positive ROI for most organizations.
What architecture is needed to achieve 99.99% uptime?
99.99% (four nines) typically requires multi-AZ deployment with automated failover, load balancing with health checks, database replication across availability zones, and automated incident response. Single-region, single-AZ deployments typically achieve 99.9% at best. Multi-region active-active is needed for 99.999%.
How do you calculate downtime from an uptime percentage?
Multiply the downtime fraction (1 minus the uptime percentage) by the length of the period. A year is 525,600 minutes (365 x 24 x 60), so 99.9% uptime allows (1 - 0.999) x 525,600 = 525.6 minutes per year, and 99.99% allows (1 - 0.9999) x 525,600 = 52.56 minutes. A day is 1,440 minutes, so 99.9% allows 1.44 minutes per day. Each additional nine cuts the allowance by 10x.
What does a 99.5% SLA allow?
99.5% uptime allows 2,628 minutes of downtime per year - about 1.82 days. That works out to roughly 219 minutes per month, 50.4 minutes per week, and 7.2 minutes per day. It is a common tier for internal tools and lower-priority services rather than customer-facing production systems.

Updated 2026-04-27