An SLO breach costs the business in four ways: failed customer transactions while it happens, service credits if the SLA is also breached, slower delivery while the team pays back reliability, and lost trust that shows up later in churn and renewals. Error-budget burn rate is the earliest warning that these costs are coming.
How do error budget and burn rate affect the SLO and the SLA?
They are links in one chain. The error budget is how much failure the SLO allows. Burn rate is how fast that budget is being used. When the budget runs out, the SLO is breached. If the failures continue past the gap between the SLO and the looser SLA, the SLA is breached too.
| Stage | What it means | Business impact |
|---|---|---|
| High burn rate | Failures are using the budget faster than the SLO allows | Customers are already seeing failures; no contractual cost yet |
| Error budget low or exhausted | Little or no room for further failures | The error budget policy slows or freezes releases |
| SLO breached | The internal reliability target is missed | Reliability work displaces planned features; leadership attention |
| SLA breached | The customer commitment is missed | Service credits, possible termination rights, renewal risk |
Each step costs more than the one before, and each is harder to reverse. Burn rate is the only one of the four that warns before the cost arrives.
Cost 1: failed customer transactions
The first cost starts with the burn itself. Every bad event counted against the error budget is a customer who could not pay, sign in or get a shipment dispatched.
An illustrative example: a payment service handles 50,000 transactions an hour with an average value of $40. A faulty deployment pushes the failure rate to 0.8%, a burn rate of 8× on a 99.9% SLO.
50,000 × 0.008 = 400 failed payments400 × $40 = $16,000Some of those customers retry and succeed; some do not come back. Either way, the cost scales with how long the burn continues, which is why the time it takes to stop it matters.
Cost 2: slower delivery under the error budget policy
When the budget runs low, a typical error budget policy puts reliability work first and pauses risky releases. That protects customers, but it delays roadmap work the business was counting on.
A burn caught early leaves budget in hand and releases continue. A burn left to exhaust the budget can freeze a team’s releases for days or weeks while it recovers.
Cost 3: service credits when the SLA is breached
If the SLA is breached, the cost becomes contractual. With an illustrative 99.5% monthly SLA that pays a 10% credit for availability between 99.0% and 99.5%:
$20,000 monthly fee × 10% = $2,00050 × $2,000 = $100,000 for the monthCredits are usually the smallest part of the cost of an SLA breach, but they are the part that appears on the invoice. What is an SLA? explains how credit tiers work.
Cost 4: trust, churn and renewals
The longest-lasting cost is harder to measure. Customers who experience repeated failures open more support tickets, escalate to account managers, and bring the incidents up at renewal. For a business-critical service, a single visible breach can shift a renewal conversation from expansion to retention.
This is also why SLOs are set from customer-facing SLIs: they measure the experience that drives these decisions.
Why acting on burn rate is the cheapest point to intervene
Return to the Dispatch API used across these guides. A day after a faulty deployment, its burn rate is 8× and 85% of its error budget is used. The SLO is still met, and the SLA is not yet at risk.
- Act now: roll back, stop the failures, keep 15% of the budget. Releases continue; no credits are owed.
- Act in 13.5 hours: the budget is exhausted and the SLO is breached. The policy freezes releases.
- Act later still: failures eat through the buffer between the 99.9% SLO and the 99.5% SLA. Credits become due.
The cost of the same incident depends mostly on when it is stopped. That is the idea behind pre-breach SLO management: treat burn rate, not the breach, as the trigger to act.
Frequently asked questions
What is the business impact of an SLO breach?
An SLO breach usually means customers have already experienced failures, the team must prioritise reliability over planned work under its error budget policy, and the buffer before the customer SLA is gone or nearly gone.
Does an SLO breach cost money directly?
Not usually through the contract, because SLOs are internal. The direct contractual cost, service credits, comes with an SLA breach. But the failed transactions and delayed releases behind an SLO breach have real cost.
How does burn rate relate to business risk?
Burn rate shows how fast the error budget is going. A high burn rate means an SLO breach, and possibly an SLA breach, could arrive within hours. It is the earliest of the reliability signals, and the one that leaves time to act.
How do you estimate the cost of downtime?
Multiply the failed transactions per hour by their average value, add the cost of any SLA credits, and add the engineering time diverted to recovery. The result is an estimate; lost trust and churn are harder to price but often larger.
Key takeaways
- Burn rate, error budget, SLO and SLA form one chain; cost grows at each step.
- The costs are failed transactions, slower delivery, service credits and lost trust.
- Credits are visible but often the smallest cost.
- Acting while burn rate is high and budget remains is the cheapest point to intervene.