Cloud SLA Calculator
Work out the service credit an SLA breach earns and compare it against what the downtime actually cost the business.
Inputs
Credits apply to the affected service charge, not the whole invoice.
Service Credit Due
$4,000.00
Credit Rate Applied
10%
Actual Downtime
259.2minutes
Downtime Allowed by the SLA
43.2minutes
Downtime Beyond the Allowance
216.0minutes
Modelled Business Loss
$51,840.00
Credit as a Share of the Loss
7.7%
Outcome
The credit recovers only part of the modelled business loss
Step by step
Values used
Contracted SLA target = 99.90 %; Measured uptime in the period = 99.40 %; Days in the billing period = 30 days; Spend on the affected service = 40,000 USD/month; Credit below the SLA target = 10 % of spend; Second credit threshold = 99 %; Credit below the second threshold = 25 % of spend; Third credit threshold = 95 %; Credit below the third threshold = 100 % of spend; Business loss per hour of downtime = 12,000 USD/hour
Cloud SLA
allowed downtime = (1 − target) × period minutes; credit rate is the tier the measured uptime falls into; credit = affected spend × credit rate; loss = downtime hours × loss per hour.
Service Credit Due
= 4,000.00
Credit Rate Applied
= 10
Actual Downtime
= 259.2 minutes
Downtime Allowed by the SLA
= 43.2 minutes
Downtime Beyond the Allowance
= 216.0 minutes
Modelled Business Loss
= 51,840.00
How it works
An SLA converts a percentage into an error budget of minutes, and the credit is a step function of where measured uptime lands rather than a proportional refund. Because the credit is a percentage of the affected service charge, it is bounded by what you spend, while the loss is bounded by what your business earns. Service credits are a pricing mechanism, not insurance: a 25% credit on a $40,000 service is trivial next to a day of lost revenue, which is why resilience engineering is worth more than SLA negotiation. Credit tiers and claim windows differ by provider and contract, so read your own agreement rather than relying on these defaults.
Formula
Cloud SLA
allowed downtime = (1 − target) × period minutes; credit rate is the tier the measured uptime falls into; credit = affected spend × credit rate; loss = downtime hours × loss per hour.
- period minutes
- Days in the billing period multiplied by 1,440
- credit tier
- A step function — typically 10% below target, 25% below 99% and 100% below 95%
- coverage ratio
- Service credit divided by the modelled business loss
Frequently Asked Questions
How is Cloud SLA calculated?
allowed downtime = (1 − target) × period minutes; credit rate is the tier the measured uptime falls into; credit = affected spend × credit rate; loss = downtime hours × loss per hour. An SLA converts a percentage into an error budget of minutes, and the credit is a step function of where measured uptime lands rather than a proportional refund. Because the credit is a percentage of the affected service charge, it is bounded by what you spend, while the loss is bounded by what your business earns.
Why does Cloud SLA matter?
Service credits are a pricing mechanism, not insurance: a 25% credit on a $40,000 service is trivial next to a day of lost revenue, which is why resilience engineering is worth more than SLA negotiation. Credit tiers and claim windows differ by provider and contract, so read your own agreement rather than relying on these defaults.
What values do I need to enter?
This calculator takes 10 inputs: Contracted SLA target, Measured uptime in the period, Days in the billing period, Spend on the affected service, Credit below the SLA target, Second credit threshold, Credit below the second threshold, Third credit threshold, Credit below the third threshold, Business loss per hour of downtime. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Do I get the credit automatically?
Usually not. Most providers require you to file a claim within a fixed window, often 30 to 60 days after the incident, with your own evidence of the impact. Credits that nobody claims are simply never paid, so the FinOps team normally owns the process.
You might also need
- Cloud Availability CalculatorCommonly used together
- Cloud Disaster Recovery CalculatorCommonly used together
- Cloud Compliance Cost CalculatorCommonly used together
- Chargeback CalculatorAlso in Multi-Cloud & FinOps
- Cloud ROI CalculatorAlso in Multi-Cloud & FinOps
- Cloud Waste CalculatorAlso in Multi-Cloud & FinOps