Find out your level of availability, how much time you can fail per month and how that affects your operation.
| Period | Inactivity allowed | Availability |
|---|---|---|
| Diary | - | - |
| Weekly | - | - |
| Monthly | - | - |
| Quarterly | - | - |
| Annual | - | - |
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.
In e-commerce
→ lost sales
In health
→ close attention
In banking
→ failed transactions
In internal operations
→ manual processes
Detect incidents before the user does
Automatic notification of critical events
Reduce response times (MTTA)
Automate actions and escalation
Reducing detection, response and resolution times has a direct impact on your SLA and business continuity.
SLA Frequently Asked Questions
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.
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.
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.
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%.
