Uptime / SLA Calculator

An availability target like "99.9%" is easy to say and hard to picture. Enter one below to see exactly how much downtime it allows over a day, a week, a month and a year.

ad placeholder — remove this div, insert an ad unit after AdSense approval

Availability target

Enter your uptime percentage
%

The share of time the service is promised to be available. Common values: 99, 99.5, 99.9, 99.95, 99.99, 99.999. You can type any number.

Downtime it allows

Per month

Total time the service may be down in a 30-day month and still meet the target.

Per day

Allowed downtime in a single 24-hour day.

Per week

Allowed downtime over 7 days.

Per quarter

Allowed downtime over 90 days.

Per year

Allowed downtime over 365 days.

Periods are fixed at 30, 90 and 365 days, the usual convention in SLA documents. Scheduled maintenance may be excluded depending on the contract.

Work it backwards

Measured some downtime and want the uptime percentage it produced?

Measured downtime

How much was it down, and over what period

How long the service was unavailable, in the unit you pick next.

The unit your downtime figure is in.

The length of time you were measuring over.

Uptime achieved

Uptime percentage

The availability this downtime works out to over the period you chose.

In "nines"

A rough label for how many leading nines the percentage has.

The "nines" at a glance

UptimeNameDowntime / monthDowntime / year
99%two nines7h 12m3d 15h 36m
99.5%3h 36m1d 19h 48m
99.9%three nines43m 12s8h 45m 36s
99.95%21m 36s4h 22m 48s
99.99%four nines4m 19s52m 34s
99.999%five nines26s5m 15s

Why each extra nine is so expensive

Every additional nine cuts your downtime budget by about 90%. Going from 99.9% to 99.99% means the same yearly outage allowance drops from nearly nine hours to under an hour. In practice that requires redundancy across failure domains, automated failover, tighter deploy processes, on-call coverage and constant testing — each of which adds cost and complexity. Most products do not need more than three nines; picking a target higher than your users require mostly buys you stress.

SLA, SLO and actual uptime

  • SLA — the promise in the contract, often with refunds or credits if missed.
  • SLO — the internal goal the team works to, usually set stricter than the SLA to keep a buffer.
  • Actual uptime — what you measured. The gap between this and your SLO is your early-warning signal.

Frequently asked questions

How much downtime does 99.9% uptime allow?

About 8 hours 45 minutes per year, or roughly 43 minutes 12 seconds per 30-day month. "Three nines" sounds strict but still leaves close to a full working day of outage over a year.

What is the difference between 99.9%, 99.99% and 99.999%?

Each extra nine cuts allowed downtime by about 10×. 99.9% allows ~8.8 hours a year, 99.99% ("four nines") about 52 minutes, and 99.999% ("five nines") about 5 minutes 15 seconds. The cost of infrastructure and process to reach each nine also rises sharply.

Does scheduled maintenance count against an SLA?

It depends on the contract. Many SLAs exclude announced maintenance windows from the downtime calculation, so read the definition of "downtime" and "excluded events" carefully. This calculator shows raw allowed downtime; adjust for exclusions your agreement allows.

What month length does this calculator use?

It uses fixed periods: 30 days for a month, 90 days for a quarter and 365 days for a year, which is the common convention in SLA documents. A calendar month with 31 days would allow slightly more downtime.

What is the difference between an SLA, an SLO and actual uptime?

The SLA is the contractual promise (often with penalties). The SLO is the internal target a team aims for, usually stricter than the SLA. Actual uptime is what you measured. Teams typically set the SLO tighter than the SLA so they have a safety margin.

ad placeholder — in-content unit goes here after approval