Free Calculator

SLA Calculator

Calculate uptime SLA and ticket compliance

Converge Converge Team
•

Uptime SLA

Per Day
1m 26s
Per Week
10m 5s
Per Month
43m 50s
Per Year
8h 46m
Nines
Three Nines (99.9%)

Ticket SLA Compliance

Compliance Rate
92.0%
Acceptable
8 tickets missed target

Formula: (Resolved on Time ÷ Total Tickets) × 100

An SLA calculator converts abstract percentages into concrete numbers — minutes of allowed downtime, or the share of tickets you actually delivered on time. The two halves of the SLA story are often confused: uptime SLA is an infrastructure commitment (the system stays online), and ticket SLA compliance is a support commitment (we respond or resolve within X). This page covers both.

When someone says "99.9% uptime," it sounds almost perfect — but it allows 8 hours and 46 minutes of downtime per year. According to Gartner, the average cost of IT downtime is $5,600 per minute, or over $300,000 per hour. For e-commerce businesses, Statista estimates that a single hour of downtime during peak shopping costs an average of $500,000 in lost revenue. These numbers explain why the difference between "three nines" and "four nines" matters.

Ticket SLA compliance is the corresponding metric on the support side. If your team commits to first-response within one business hour and resolves 92 of 100 tickets within that window, compliance is 92%. The benchmark for healthy support operations is 95%+. Falling under 90% is a strong signal of capacity, triage, or staffing problems — not just slow agents.

The concept of "nines" in availability is standard across the technology industry. AWS, Azure, and Google Cloud all publish SLAs in this format. AWS guarantees 99.99% for most services, which means no more than 52.6 minutes of downtime per year. Violating that threshold triggers service credits — and the same accountability principle applies to ticket SLAs in customer-facing contracts.

How to Use This Calculator

  1. Uptime SLA: enter or pick a target uptime percentage. Read the maximum allowed downtime per day, week, month, and year.
  2. Ticket SLA Compliance: enter your total tickets in the period and how many were resolved within the SLA window. The calculator shows your compliance rate, the count of missed tickets, and a simple grade.
  3. Compare scenarios: try different uptime tiers, or model what compliance looks like if you cut missed tickets in half.

Pro Tips

  • Each nine is 10x harder: Going from 99.9% to 99.99% doesn't just reduce downtime by 0.09% — it reduces it by a factor of 10. The engineering effort and cost increase dramatically with each nine.
  • Exclude planned maintenance: Most SLAs exclude scheduled maintenance windows. Clarify this in your agreements to avoid disputes.
  • Measure from the customer's perspective: Internal monitoring might show 100% uptime, but if customers experience DNS issues or CDN problems, their experience is different.
  • Set realistic ticket SLA targets: A 1-hour first-response SLA at 95% compliance is achievable for most teams. Promising 15 minutes at 99% requires 24/7 staffing or automation; underestimate and you erode trust every time you breach.
  • Track misses, not just the rate: 95% compliance on 1,000 tickets is 50 missed customers. Each one deserves a follow-up, not just a number on a dashboard.

Frequently Asked Questions

What is an SLA?
A Service Level Agreement (SLA) is a contract between a service provider and customer that defines the expected level of service, including uptime guarantees, response times, and remedies for failures. In technology, SLAs typically specify an uptime percentage like 99.9% or 99.99%, which determines the maximum allowed downtime.
What is the difference between uptime SLA and ticket SLA?
Uptime SLA is an infrastructure metric — the percentage of time a service is available (e.g. 99.9%). Ticket SLA is a support metric — the percentage of customer tickets resolved within a target window (e.g. 95% within 24 hours). Both are 'SLAs' but they measure different things and are computed differently. Use the uptime card for infrastructure availability and the compliance card for support performance.
What is the difference between 99.9% and 99.99% uptime?
99.9% uptime allows 8 hours and 46 minutes of downtime per year. 99.99% allows only 52 minutes and 36 seconds per year — roughly 10x less. Each additional nine dramatically reduces the allowed downtime window, which is why 'five nines' (99.999%) is considered the gold standard for critical infrastructure.
How do you calculate SLA uptime?
SLA Uptime % = ((Total Time - Downtime) / Total Time) × 100. For example, if a service was down for 4 hours in a 30-day month: ((720 - 4) / 720) × 100 = 99.44%. You can also work backwards: Allowed Downtime = Total Time × (1 - SLA% / 100).
How do you calculate SLA compliance for support tickets?
SLA Compliance % = (Tickets Resolved on Time / Total Tickets) × 100. If you closed 92 out of 100 tickets within your stated response or resolution window, your compliance is 92%. Most successful support teams target 95% or higher. Anything below 90% means a meaningful share of customers are missing their promised window.
What is a good ticket SLA compliance rate?
95% compliance is the industry benchmark for healthy support operations. 90-95% is acceptable but indicates either understaffing or unrealistic SLA targets. Below 90% usually means the team needs more capacity, the SLA needs adjusting, or the volume needs better triage. World-class teams hit 98%+ consistently by reserving capacity for spikes.
What is a reasonable SLA for a SaaS product?
Most SaaS products offer 99.9% uptime (about 8.7 hours downtime per year). Enterprise services often guarantee 99.95% or 99.99%. Anything below 99.5% is considered poor for paid services. Cloud providers like AWS and Azure typically offer 99.99% for their core services.
What happens when an SLA is breached?
Most SLAs include service credits as compensation for breaches. Typically, providers offer 10-25% credit on the monthly bill per defined violation threshold. Some enterprise contracts include financial penalties or termination rights. The key is having clear, measurable metrics and an agreed process for claiming credits.
Should SLA be measured in calendar time or business hours?
It depends on the service. Customer-facing applications should use calendar time (24/7) since customers expect availability anytime. Internal tools may use business hours (e.g., 8am-6pm weekdays). Make sure the SLA clearly defines the measurement period to avoid disputes.

Related Free Tools

Response Time Calculator Support Cost Calculator CSAT Calculator

Ready to try Converge?

$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.

Start Free Trial