SLA calculator: uptime, downtime and the ticket SLA formula
An SLA percentage is a budget. Allowed downtime is the minutes in the period times (1 − SLA ÷ 100), so 99.9% gives you 43 minutes 12 seconds in a 30-day month. For tickets, SLA compliance is the tickets that met the target divided by the tickets measured, times 100, and a 95% target on 240 tickets lets you miss 12.
| Per day | 1m 26.4s |
|---|---|
| Per week | 10m 4.8s |
| Per month (30 days) | 43m 12s |
| Per year (365 days) | 8h 45m 36s |
| Allowed at 95% | 12 |
|---|---|
| Missed so far | 9 |
| Left | 3 |
The SLA formulas
| What you want | Formula |
|---|---|
| Uptime percentage | (minutes in the period − downtime) ÷ minutes in the period × 100 |
| Allowed downtime | minutes in the period × (1 − SLA ÷ 100) |
| Ticket SLA compliance | tickets that met the target ÷ tickets measured × 100 |
| Misses you can afford | tickets measured × (1 − target ÷ 100), rounded down |
The arithmetic is the easy part. The arguments happen over what goes into it. For uptime, downtime means minutes the service couldn't be used, and some SLAs leave scheduled maintenance out of the count. For tickets, "measured" means the tickets under that SLA that closed in the period, and the clock may not run the whole time: in HaloPSA, the With User status puts a ticket on hold by default and pauses the SLA timer, so time spent waiting on the user doesn't count against you. The Ticket SLA tab works for a response-time SLA too: count the tickets that missed the response target instead.
Downtime by SLA level
Here's what each common uptime SLA allows for a service that has to be up around the clock.
| SLA | Per day | Per week | Per 30-day month | Per 365-day year |
|---|---|---|---|---|
| 99% | 14m 24s | 1h 40m 48s | 7h 12m | 3d 15h 36m |
| 99.5% | 7m 12s | 50m 24s | 3h 36m | 1d 19h 48m |
| 99.9% | 1m 26.4s | 10m 4.8s | 43m 12s | 8h 45m 36s |
| 99.95% | 43.2s | 5m 2.4s | 21m 36s | 4h 22m 48s |
| 99.99% | 8.6s | 1m 0.5s | 4m 19.2s | 52m 33.6s |
Two uptime calculators can give different answers for the same SLA, and the month is why. Take a month as a twelfth of a 365.24-day year instead of 30 days, and 99.9% allows 43 minutes 50 seconds. Set the days to the month your contract measures.
How Microsoft 365's SLA counts downtime
Microsoft measures each calendar month, and it doesn't just count how long an outage lasted. It counts user-minutes: each incident's minutes times the number of users it hit, against every user's minutes in the month. Say a 300-user client loses Exchange Online for 2 hours, but only 50 users are affected. That's 6,000 downtime user-minutes out of 12,960,000 in a 30-day month, or 99.954% uptime. That's above 99.9%, so no credit. The Exchange Online credit is 25% below 99.9%, 50% below 99% and 100% below 95%, and credits are your only remedy. Your client felt that outage a lot more than 0.046% of their month, so log it whatever the SLA says.
What resolution target can L1 tickets actually hit?
Uptime math is fixed. Ticket targets are a judgment call, and the easy way to make it is to look at how fast a typical ticket closes. Rallied's own numbers show why that's a trap. Across 2,099 tickets Rallied worked in October 2026, half closed within 5.3 hours of being opened, and a quarter took longer than 46 hours. Set a resolution target at the median and you miss half your tickets by design. Set it at the 75th percentile and you still miss a quarter. A 95% target has to sit beyond both.
A paused SLA clock leaves out the waiting on the user, so read these hours as the most your clock would show. The shape holds anyway, and it's why we'd set resolution targets per ticket type, well past each one's 75th percentile. Onboarding's is 73.1 hours, more than four times the 17.0 hours for password resets. As one MSP put it on a call with us, "A customer is waiting for an hour for one of the L1 guys to pick up the ticket and then it gets resolved in 30 seconds." That wait is the tail, and it's what breaks the SLA. We go deeper on where ticket time goes in MSP ticket resolution time benchmarks and how to cut first response time, and the MSP ROI calculator puts a cost on the same tickets.
Close L1 tickets inside your SLA
Rallied is an AI agent that works password resets, MFA issues, onboarding and offboarding inside ConnectWise, HaloPSA or Autotask. It runs the fix in Microsoft 365 and your RMM, then writes the notes back to the ticket. It's resolving tickets the same week you connect it.