Uptime & SLA Calculator
Turn an SLA percentage into the downtime it allows, work out uptime from real downtime, combine services in series and in parallel, and set alerts on how fast an error budget burns.
Free · No signupWorked out in your browser
The availability the SLA or SLO promises.
Match your contract: many bill by the calendar month, which runs 28 to 31 days.
Allowed downtime for
99.9%
three nines
| Per | Allowed downtime | Period |
|---|---|---|
| Day | 1m 26.4s | 1 day |
| Week | 10m 4.8s | 7 days |
| Month | 43m 12s | 30 days |
| Quarter | 2h 11m 24s | 91.25 days |
| Year | 8h 45m 36s | 365 days |
That is your error budget. A 5-minute outage spends 11.6% of the month's, and one deploy with 30 seconds of errors spends 1.16%.
Worked out in this tab as you type. Nothing you enter leaves this page.
Budgets are theory: know your real numbers
Watch each server’s health, live.
CtrlOps gives you real-time CPU, memory and disk for each server you open, and alerts such as Website down, so you know how much of your error budget you are actually spending. Local-first, credentials never leave your machine.
The nines
Allowed downtime,
by SLA.
With a 365-day year and a 30-day month. Each extra nine is ten times less room.
| SLA | Nines | Per year | Per month | Per week | Per day |
|---|---|---|---|---|---|
99% | Two | 3d 15h 36m | 7h 12m | 1h 40m 48s | 14m 24s |
99.5% | Two and a half | 1d 19h 48m | 3h 36m | 50m 24s | 7m 12s |
99.9% | Three | 8h 45m 36s | 43m 12s | 10m 4.8s | 1m 26.4s |
99.95% | Three and a half | 4h 22m 48s | 21m 36s | 5m 2.4s | 43.2s |
99.99% | Four | 52m 33.6s | 4m 19.2s | 1m 0.5s | 8.64s |
99.999% | Five | 5m 15.4s | 25.9s | 6.05s | 0.864s |
How uptime is counted
A percentage.
A number of minutes.
What uptime, SLA, and the nines mean
Uptime is the share of time a service is available. An SLA, a service level agreement, promises a minimum, usually as a percentage like 99.9%. People count the leading nines: 99.9% is three nines, 99.999% is five. Each extra nine cuts the allowed downtime by ten.
How allowed downtime is calculated
It is the length of the period times the share you are not promising: downtime = period × (1 − SLA / 100). For 99.9% over a 30-day month that is 2,592,000 s × 0.001 = 2,592 s, or 43m 12s. The window matters, which is why the calculator lets you set how long a month and a year are.
Error budgets and burn rate
Site reliability teams turn the SLA around: the allowed downtime is an error budget to spend on incidents, risky deploys and maintenance. The burn rate is how fast it is going: at 1×, a 30-day budget lasts exactly 30 days; at 14.4×, it is gone in two days, and an hour of that spends 2% of the month. That is the threshold Google's SRE workbook pages on, checked over a long and a short window so a blip does not wake anyone.
Several services: series and redundancy
A request that needs every one of several services is up only when all of them are, so availabilities multiply: three at 99.9% give about 99.7%. Redundant copies work the other way: two copies at 99.9% are both down only 0.0001% of the time, if they fail independently. Shared power, a shared network or the same bad deploy breaks that assumption, so treat the result as a ceiling.
SLA, SLO and SLI
- The SLI is what you measure, such as the share of requests that succeed.
- The SLO is your own target for it, such as 99.95%.
- The SLA is the promise to customers, usually looser than the SLO and often with penalties.
Gotchas
- Monthly and yearly SLAs allow very different downtime; check which your provider uses.
- Many SLAs leave planned maintenance out of the count.
- Partial outages, raised error rates and slow responses may or may not count: the SLI decides.
Uptime & SLA FAQ
Uptime and SLAs,
explained.
About 8 hours 45 minutes per year, 43 minutes 12 seconds per 30-day month, or 1 minute 26 seconds per day. Each additional nine reduces the allowed downtime by roughly a factor of ten.
They are three, four, and five nines. Per year that is roughly 8h 46m (99.9%), 52m 34s (99.99%), and 5m 15s (99.999%). Each extra nine is about ten times less allowed downtime - and usually far more expensive to achieve.
It is the allowed downtime restated as something you can spend. A 99.9% monthly SLA gives roughly 43 minutes of error budget per month for incidents, deployments, and maintenance. SRE teams use it to balance shipping speed against reliability.
For services in series (a request needs all of them), multiply their availabilities: three components at 99.9% give 0.999^3 ≈ 99.7%. Redundancy works the opposite way - parallel copies raise availability. Use the Composite mode in this calculator.
It is shorthand for 99.9% availability - three leading nines. Two nines is 99%, four nines is 99.99%, five nines is 99.999%. "Three and a half nines" usually means 99.95%.
It depends on the agreement, and it matters a lot: 99.9% over a month allows ~43 minutes, but the same percentage over a year allows ~8.7 hours in a single stretch. Always confirm the measurement window, and set the month/year basis in this tool to match.
Keep reading
Tools and guides for your next step.