Error Budget Burn Rate Calculator
See how quickly your team is consuming the error budget by comparing observed downtime to the allowance implied by your availability SLO.
Examples
- SLO 99.9%, 30-day window, 7 days elapsed, 25 downtime minutes ⇒ 2.48 x
- SLO 99.5%, 30-day window, 15 days elapsed, 40 downtime minutes ⇒ 0.37 x
FAQ
What burn rate should trigger an alert?
Many SRE teams alert at 2× burn for short windows or 4× for very short windows, but adjust thresholds to your risk tolerance.
Why include elapsed days?
Burn rate normalizes consumption by the fraction of the SLO window that has passed, revealing acceleration or slowdown.
Does this handle partial outages?
Yes. Enter total minutes of unavailability across the elapsed period, regardless of how incidents were distributed.
Additional Information
- Burn rate above 1× means you are consuming the error budget faster than time is passing.
- Allowed downtime equals window length × (1 − SLO) × total minutes.
- Combine burn rate with remaining budget to forecast exhaustion dates.