How is uptime percentage calculated?

Uptime percentage is calculated using the formula: Availability (%) = (Total Time - Downtime) / Total Time × 100. For example, if a service ran for 720 hours in a month with 43 minutes of downtime, the availability would be 99.9%.

How much downtime does a 99.9% SLA allow?

A 99.9% SLA (three nines) allows approximately: 43.8 minutes per month, 10.1 minutes per week, 1.44 minutes per day, or 8.76 hours per year. This is the standard for most production services.

What is the difference between 99.9% and 99.99% availability?

99.9% (three nines) allows ~43.8 minutes of downtime per month, suitable for standard production applications. 99.99% (four nines) allows only ~4.38 minutes per month, requiring redundant infrastructure and high availability. The difference can cost significantly more in infrastructure.

What is an SLA and how does it relate to downtime?

An SLA (Service Level Agreement) is a contract that defines the expected service level, including the guaranteed uptime percentage. For example, a 99.9% SLA means the provider guarantees the service will be available 99.9% of the time, and any downtime below that threshold may result in credits or penalties.

Back to tools

99% SLA - Uptime Calculator

Select an SLA level or enter downtime minutes to see the allowed downtime per period.

SLA 99% SLA 99.9% SLA 99.95% SLA 99.99% SLA 99.999% SLA 99.9999%

Availability & SLA Calculator

Calculate availability from downtime or downtime from SLA requirement

Downtime minutes per month

Enter the downtime minutes for each month to get a more accurate annual average.

Select SLA level

Maximum allowed downtime

SLA Level	Day	Week	Month	Quarter	Year	Typical use
99%	14 min 24 s	1 h 41 min	7 h 12 min	21 h 36 min	3 d 16 h	Dev / testing
99.9%	1 min 26 s	10 min 5 s	43 min 12 s	2 h 10 min	8 h 46 min	Standard production
99.95%	43 s	5 min 2 s	21 min 36 s	1 h 5 min	4 h 23 min	High availability
99.99%	9 s	1 min	4 min 19 s	12 min 58 s	52 min 34 s	Enterprise
99.999%	< 1 s	6 s	26 s	1 min 18 s	5 min 15 s	Mission critical
99.9999%	< 1 s	< 1 s	3 s	8 s	32 s	Fault tolerant

Downtime cost calculator

Hourly revenue ($)

What is availability?

Availability measures the percentage of time a service is operational. It is calculated by subtracting downtime from total time divided by total time. It is the most common metric used in SLA contracts to guarantee service quality.

Availability (%) = (Total Time - Downtime) / Total Time × 100

Example: 30 days = 720h. If the service was down 7.2h: (720 - 7.2) / 720 × 100 = 99% availability

What is an SLA?

An SLA (Service Level Agreement) is a contract between provider and customer that defines the minimum acceptable service level. It typically includes guaranteed uptime percentage, maximum incident response time (MTTR), and penalties for non-compliance.

Why percentiles matter

The gap between 99.9% and 99.99% is massive: the former allows 43 minutes of downtime per month, the latter only 4.3 minutes. For an e-commerce site earning $100k/day, 1 hour of downtime costs ~$4,166. Choosing the right SLA is a business decision, not a technical one.

Mean time metrics

MTBF (Mean Time Between Failures) = Total Operational Time / Number of Failures
MTTR (Mean Time To Repair) = Total Repair Time / Number of Repairs
MTTA (Mean Time To Acknowledge) = Total Time to Acknowledge / Number of Incidents

SLA Service Credit

Typical penalty when SLA is not met:

• Below 99.9% but ≥ 99.0% → 10% credit
• Below 99.0% → 25% credit

What Does a 99% SLA Mean?

A 99% SLA —often referred to as "one nine" availability— allows your service to be down for up to 7.2 hours per month or 3.65 days per year without breaching the agreement. It tolerates a full 1% of annual downtime. The 99% SLA availability meaning is straightforward: out of every 100 hours of operation, one hour can be a failure. This is the most basic entry-level SLA in the industry, designed for workloads where cost dominates and downtime windows don't translate into critical losses. Unlike 99.9% agreements, the permitted downtime here is 10 times higher, which fundamentally changes both infrastructure requirements and budget.

Who Is It For?

This SLA for development environments is purpose-built for engineering teams running test servers, CI/CD pipelines, and staging environments. It is also the ideal SLA for startups that have not yet launched paid features or monetized their platform. A classic CI/CD SLA example: if your Jenkins server goes down for 3 hours on a Saturday afternoon, development pauses but revenue keeps flowing. It also fits internal company servers, documentation sites, educational labs, and any non-critical workload where the team can tolerate a few hours of interruption.

Infrastructure Requirements

A 99% SLA does not require geographic redundancy, load balancers, or multi-AZ databases. A single instance —a standard VPS or a standalone server— is perfectly adequate. Basic monitoring suffices: a health-check endpoint polled every 5 minutes with email or Slack alerts when it fails. Backups can be daily with a 7-day retention period stored on the same cloud provider. You do not need automatic failover, real-time replication, or dedicated DevOps support.

Cost Savings

The cost difference is dramatic: a 99% SLA is 5 to 10 times cheaper than a 99.9% SLA. In practical terms, a startup can save between 200 and 1,000 USD per month on cloud infrastructure by skipping high-availability instances, standard SSD instead of replicated storage, and omitting load balancers, floating IPs, and advanced monitoring suites. If your current cloud bill is around 300 USD per month, upgrading to a 99.9% SLA could triple or quadruple that cost without delivering proportional business value.

When to Upgrade

You should consider upgrading to a higher SLA tier when your service starts serving external paying customers or when downtime begins to directly impact revenue. If 7.2 hours of monthly downtime starts generating recurring support tickets or eroding user trust, your SLA has become a bottleneck. The natural next step is a 99.9% SLA for standard production, which cuts allowed downtime to 43 minutes per month —a 10x improvement that transforms the end-user experience.

View all tools