Humanfrog Lab

How much downtime does 99.9 % really allow, and what availability does your whole system actually reach?

A provider promises 99.9 % availability and the number sounds close to perfect. In practice it means up to 43 minutes of downtime in a 30-day month, or almost 9 hours a year, and only for what the SLA actually counts as downtime. Your service also depends on several components at once, so its availability is lower than that of any single component.

With this uptime and SLA calculator, convert an availability percentage into allowed downtime per day, week, month, quarter and year and back again, calculate the availability of your whole system from components in series and redundant groups, and estimate the annual cost of downtime. The guide below the tool explains SLA vs SLO vs SLI, typical exclusions and service credits.

How much downtime does your SLA allow, and what does your system reach?

The calculator has three parts: conversion between availability and downtime, composite system availability, and the cost of downtime. The maths is exact, the formulas are shown next to the results, and every default value can be changed.

1. Availability and allowed downtime

Enter an availability percentage and see how much downtime it allows in each period. Below, you can also convert a known downtime back into a percentage.

Availability
For example 99.9 for "three nines". Up to three decimal places.
A year has 365 days and a quarter is a quarter of a year (91.25 days). Most SLAs are measured per calendar month.

Common levels:

Allowed downtime

PeriodAllowed downtime
Day
Week
Month
Quarter
Year

Formula: allowed downtime = (100 % − availability) × length of the period.

Reverse: from downtime to availability

Achieved availability

Formula: availability = (1 − downtime ÷ length of the period) × 100 %.

2. Availability of the whole system

A service works only when all the components it depends on work. Enter each component with its availability. If a component runs as a redundant group (for example two servers behind a load balancer or a database cluster), enter the number of instances.

1 = a single instance. 2 or more = a redundant group in which one working instance is enough to keep the service running.

Composite availability

Component Instances Availability Downtime per year
Whole system (components in series)
If every component had at least two instances

  • In series (all components are needed): A = A₁ × A₂ × … × Aₖ
  • Redundant group of n instances (one is enough): A = 1 − (1 − a)ⁿ

The calculation assumes that components fail independently of each other and that failover in a redundant group is instant. Shared power, a shared network, the same software bug or a faulty failover lower the real availability.

3. Cost of downtime (optional)

Estimate what one hour of downtime costs you and how much downtime at each availability level could cost per year. All values are editable assumptions.

Cost of one hour of downtime
For example annual online revenue ÷ business hours. Enter 0 if downtime does not stop sales.
Indicative value; replace it with your own employer cost. Eurostat: average hourly labour cost in the EU was EUR 34.9 in 2025 (as of November 2026).
100 % if you operate around the clock. Lower it if part of the downtime falls outside business hours.

Expected annual cost of downtime

AvailabilityDowntime per yearCost per year

Formula: annual cost = (100 % − availability) × 8,760 h × (lost revenue per hour + employees × hourly cost) × share of downtime that hits the business.

The cost assumes that downtime fully uses the limit allowed by the availability level. Reputational damage, contractual penalties and recovery costs are not included.

The calculator is a guide only. Actual availability depends on the architecture, monitoring, maintenance processes and the exact SLA terms of your providers.

The calculation runs in your browser. Your answers are only sent if you submit the contact form below.

What the "nines" really mean

Availability (uptime) is the share of time in which a service works. Allowed downtime is simple to calculate: allowed downtime = (100 % − availability) × length of the period. On paper the difference between 99.9 % and 99.99 % is a single nine; in practice it is ten times less allowed downtime.

AvailabilityPer dayPer month (30 days)Per year (365 days)
99 %14 min 24 s7 h 12 min3 d 15 h 36 min
99.5 %7 min 12 s3 h 36 min1 d 19 h 48 min
99.9 %1 min 26 s43 min 12 s8 h 45 min 36 s
99.95 %43 s21 min 36 s4 h 22 min 48 s
99.99 %8.6 s4 min 19 s52 min 34 s
99.999 %0.86 s26 s5 min 15 s

Most SLAs measure availability per calendar month, so the allowed downtime in February is shorter than in January. The yearly figure is useful for comparison, but the monthly one is what counts in the contract. Calculate exact values for any percentage and period with the uptime calculator on this page.

SLA vs SLO vs SLI: three acronyms, three different things

The terms are often mixed up, but they describe different levels. The Google Site Reliability Engineering book separates them as follows:

  • SLI (Service Level Indicator) is a measured value, for example the share of successful requests, the share of minutes in which the service responds, or response time.
  • SLO (Service Level Objective) is the target for that indicator, for example 99.95 % successful requests in a calendar month. It is an internal goal of the team.
  • SLA (Service Level Agreement) is the contract with the customer that contains the promised level and the consequences of missing it, most often a service credit.

An internal SLO is therefore usually stricter than the SLA promised to customers. SRE calls the gap between the target and the actual state the error budget: while there is enough of it, the team can ship changes; when it runs out, stability takes priority.

What an SLA usually does not count

The percentage in the contract is only half of the information. The other half is the definition of downtime and the list of exclusions. When reading an SLA, check in particular:

  • Planned maintenance. Many providers exclude maintenance windows announced in advance. For users the service is still unavailable, so check how long and how frequent the windows are and whether they fall outside your business hours.
  • The definition of downtime. Does only a complete outage count, or a partial one too? For region-level EC2 availability, for example, AWS counts downtime only when all your running instances in two or more availability zones lose external connectivity at the same time.
  • The measurement window. Monthly, quarterly or yearly. With a yearly window, a single long outage can be "diluted" over the whole year.
  • Who measures. Whether the provider's monitoring or yours counts, and how quickly you have to report an outage.
  • Exclusions. Force majeure, faults on the customer side, network problems outside the provider's domain and preview services are almost always excluded.

Service credits are not insurance

If the provider misses the promised level, you are usually entitled to a service credit, a partial refund of the monthly fee for the affected service. For Amazon EC2, for example, it is 10 % when monthly availability falls below the committed level, 30 % below 99 % and 100 % below 95 %, and the claim must be submitted by the end of the second billing cycle after the incident.

Consider an example: the service costs EUR 2,000 per month and an outage lasts 4 hours in a 30-day month. Availability drops to 99.44 % and you receive a 10 % credit, i.e. EUR 200. If an hour of downtime costs you EUR 1,500, the damage is EUR 6,000. A credit is an incentive for the provider, not compensation for you. When choosing a provider, an architecture that prevents outages matters more than the size of the credit.

Availability of the whole system: chains and redundancy

An online shop needs an internet connection, an application server and a database. If any link fails, the shop is down. For components in series, availabilities multiply: A = A₁ × A₂ × … × Aₖ. Three components at 99.9 %, 99.9 % and 99.95 % give 99.75 % together, which means almost 22 hours of downtime per year instead of 8 hours 46 minutes. Every additional component lowers availability.

Redundancy works the other way round. For a group of n identical instances where one is enough, A = 1 − (1 − a)ⁿ. Two servers at 99 % each reach 99.99 % together, and two at 99.9 % reach 99.9999 %. The condition is that they fail independently. Shared power, the same switch, the same faulty software version or a failed automatic failover break this assumption, so the real availability of redundant systems is lower than the calculated one.

A practical tip: find the weakest link first, because improving it lifts the system the most. Often it is not a server but a single internet connection, a single firewall or a database without a replica.

SLA, RPO and RTO

An SLA sets how much downtime is allowed in a period. RTO (Recovery Time Objective) sets how quickly a system must be running again after a single incident, and RPO (Recovery Point Objective) how much data you can lose. The numbers must be consistent: if the RTO for a critical system is 4 hours, one major incident uses more than a monthly 99.9 % SLA allows (43 minutes). A high SLA therefore requires replication and fast failover, not just good backups.

How to set RPO and RTO per system group and check whether your recovery meets them is explained in the guide backup, RPO and RTO.

SLA contract checklist

  1. Agree with management what an hour of downtime costs and how much downtime per month is still acceptable.
  2. Map the dependencies of the service and calculate the availability of the whole chain, not just individual components.
  3. Check the definition of downtime, the measurement window and the measurement method.
  4. Check the length, frequency and timing of planned maintenance windows.
  5. Read the list of exclusions and the procedure and deadline for claiming credits.
  6. Besides availability, ask for support response times and resolution times by priority.
  7. Align the SLA with RPO, RTO and your disaster recovery plan.
  8. Set up your own independent availability monitoring and monthly reporting.

Humanfrog runs infrastructure in TIER III data centres in Slovenia and designs redundant architectures and monitoring. If you would like an expert to check the results of the calculator or review an existing SLA, get in touch.

Frequently asked questions

How much downtime does 99.9 % uptime allow?
99.9 % availability allows 0.1 % downtime: about 1 minute 26 seconds per day, 43 minutes 12 seconds in a 30-day month and 8 hours 45 minutes 36 seconds in a 365-day year. At 99.99 % it is only about 4 minutes per month or 53 minutes per year.
What is the difference between SLA, SLO and SLI?
An SLI (Service Level Indicator) is a measured value, such as the share of successful requests or of minutes in service. An SLO (Service Level Objective) is the target for that indicator, for example 99.95 % per month. An SLA (Service Level Agreement) is the contract with customers that sets the promised level and the consequences of missing it, most often a service credit.
How do I calculate the availability of several connected components?
If all components are needed, multiply their availabilities: three components at 99.9 %, 99.9 % and 99.95 % give about 99.75 % together. For a redundant group of n identical instances where one is enough, A = 1 − (1 − a)ⁿ; two servers at 99 % each reach 99.99 % if they fail independently.
Does planned maintenance count as downtime?
Often not. Many SLAs exclude maintenance windows announced in advance, force majeure, faults on the customer side and problems outside the provider network. For users the service is still unavailable during that time, so check how much maintenance is allowed and when.
What is a service credit, and does it cover the damage?
A service credit is a partial refund of the monthly fee when the provider misses the promised availability, typically 10 to 100 % of the fee for the affected service. It does not cover lost revenue or staff time, and you usually have to claim it yourself within a deadline. A credit is an incentive for the provider, not insurance for you.
How does an SLA relate to RPO and RTO?
An SLA sets how much downtime is allowed in a period, while RTO sets how quickly a system must be running again after a single incident. With an RTO of 4 hours, one major incident uses more than a monthly 99.9 % SLA allows. RPO defines how much data you can lose, which availability does not cover.

Stay up to date

Regulations, licence prices and technology change fast. When we update the guides and tools in the Lab or publish a new article, we let you know by e-mail. Occasional, and never spam.

Subscribe to the newsletter