Skip to content
Omnikalc

Error budget burn rate calculator

Enter the SLO, the compliance window, the current error rate and the budget already used to get the error budget, the burn rate, the hours before the budget is gone and the burn rates that trigger alerts.

Updated on
Your inputs
%

Value out of range

days

Value out of range

%

Value out of range

%

Value out of range

Results

Burn rate

14.40 ×

Severe: page the on-call team
Error budget over the window
43.2 min of full outage
Share of the budget burned per hour
2.00 %
Hours until the remaining budget is gone
40.0 h
Burn rate that uses 2 % of the budget in 1 hour
14.4 ×
Burn rate that uses 5 % of the budget in 6 hours
6.0 ×

The error budget burn rate calculator gives the error budget of a service level objective, the burn rate of the current error rate, the share of budget used per hour and the hours before the budget is exhausted.

How the calculation works

  • Enter the SLO and the compliance window.
  • Enter the current error rate and the budget already consumed.
  • The calculator gives the burn rate, the error budget, the hourly consumption, the hours left and the alert thresholds.

Example

A 99.9 % SLO over 30 days allows 0.1 % of errors, which is 43.2 minutes of complete outage. With an error rate of 1.44 %, the burn rate is 1.44 / 0.1 = 14.40: the budget burns 2.00 % per hour. If 20 % is already used, the remaining 80 % last 40.0 hours. The alert thresholds are 14.4 for 2 % in 1 hour and 6.0 for 5 % in 6 hours.

Why it matters

The calculator helps site reliability engineers, developers and managers who define service level objectives to set alerts that react quickly to real incidents without waking people for minor blips.

Good to know

Alerts on the burn rate are better than alerts on a fixed error threshold, because they take into account how much budget the SLO leaves. Teams often combine a long window and a short one, for example one hour and five minutes, so that an alert fires only when the problem is both significant and still happening. The error rate here can mean failed requests or degraded minutes, depending on how the SLO is defined, so use the same unit as the objective. Higher objectives leave very small budgets: 99.99 % over 30 days is only 4.3 minutes. A budget that is never spent can also be a sign of excess caution.

The uptime and SLA calculator converts availability targets into downtime, the MTBF and availability calculator links failures and repairs, the queue wait time calculator covers waiting lines and the server capacity calculator sizes servers.

Frequently asked questions

What is a burn rate?

It compares the current error rate with the rate the SLO allows. A burn rate of 1 uses exactly the whole budget by the end of the window. A burn rate of 10 would use it up in a tenth of the window. It is the error rate divided by (100 − SLO), in percent.

How are the alert thresholds chosen?

A common approach is to alert when a given share of the budget is spent in a short time. Using 2 % of a 30-day budget in one hour needs a burn rate of 0.02 × 720 = 14.4, and 5 % in six hours needs 6. Fast burns page someone, slow ones open a ticket.

What if the budget is exhausted?

Many teams then slow down risky changes and focus on reliability until the window recovers. The budget turns an abstract promise into a shared quantity that product and engineering teams can discuss, trading speed of delivery against stability.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.