SLA Calculator

Find out your level of availability, how much time you can fail per month and how that affects your operation.

SLA Calculator - Downtime and Downtime Cost Calculator | 24Cevent
SLA Availability Calculator
99.9%
99.9% SLA availability and downtime
Period Inactivity allowed Availability
Diary - -
Weekly - -
Monthly - -
Quarterly- -
Annual - -


Want to take your calculation one step further?

Downtime Cost Calculator
SLA level
SLA selected above
Change the value in the calculator 1
99.9%
Monthly turnover $500,000 USD
$10K$5M
Incidents / period 5 incidents
150
MTTR 30 min
1 min8 hrs
Mean Time To Resolve - average time to solve an incident
Contractual penalty 10 %
0%100%
Customers affected 500 customers
10100K
Monthly revenue per customer $100 USD
$1$10K
Period under review
Results for the selected period
Allowable fall time
-
according to SLA
Actual downtime (MTTR × incidents)
-
-
Cost per minute of fall
-
USD / minute
Estimated total loss
-
downtime + penalty
Contractual penalty
-
-
Potential savings with 24Cevent
-
90% reduction in response time
How much downtime can you afford? -
How much time are the incidents costing you? -
How risky is it for you not to comply with your SLA agreement? -
Your potential loss in the period
-
Are you willing to risk that?

What is SLA

and how is downtime calculated?

A Service Level Agreement (SLA) defines the minimum percentage of time a system must be available. An SLA of 99.9% sounds high, but it is equivalent to almost 9 hours of downtime per year.

The calculation considers four key factors: the percentage of SLA committed, your company's billing (which determines the cost per minute), the MTTR (mean time to resolution) and the number of incidents in the period analyzed.

In addition, contractual penalties for non-compliance can multiply the economic impact.

Why is it important?

Rule of 9s
Convert your SLA to real-time allowed downtime.
SLA New Downtime / year Downtime per month Downtime per week
99% 2 nines 99 87h 39m 7h 18m 1h 40m
99.9% 3 nines 999 8h 45m 43m 49s 10m 4s
99.95% 3.5 nines 9995 4h 22m 21m 54s 5m 2s
99.99% 4 nines 9999 52m 35s 4m 23s 1m
99.999% 5 nines 99999 5m 15s 26s 6s
The more “9s” your SLA has, the lower the allowed downtime and the higher the operational requirements.

A fall

is not just a number

In e-commerce

→ lost sales

In health

→ close attention

In banking

→ failed transactions

In internal operations

→ manual processes

How to improve your SLA

in practice

Detect incidents before the user does

Automatic notification of critical events

Reduce response times (MTTA)

Automate actions and escalation

The SLA improves when you improve your operations

Reducing detection, response and resolution times has a direct impact on your SLA and business continuity.

SLA Frequently Asked Questions

What does a 99.9% SLA mean?

An SLA of 99.9% (three nines) allows a maximum of 8 hours 45 minutes of downtime per year, 43 minutes 49 seconds per month, or 10 minutes 4 seconds per week. This is the most common standard for cloud services and enterprise applications.

How much downtime does a 99.99% SLA allow?

An SLA of 99.99% (four nines) allows only 52 minutes 35 seconds of downtime per year, 4 minutes 23 seconds per month, or approximately 1 minute per week. Requires redundant infrastructure and automatic incident response.

How is the downtime cost calculated?

Cost per minute = Monthly billing ÷ (30 days × 24 hours × 60 minutes). It is then multiplied by the actual minutes of inactivity (MTTR × number of incidents) and the contractual penalty is added if applicable.

What is MTTR and why does it matter for SLA?

MTTR (Mean Time To Resolve) is the average time it takes your team to resolve an incident from the time it is detected. It is the main factor that determines whether you meet or break your SLA. Reducing MTTR with automation can be the difference between meeting 99.9% or dropping to 99.5%.

Improve your SLA
without expanding your team

Discover how to automate the management of alerts and incidents in your operation.

✓ No credit card required · Ready in 1–2 hours