Error budget calculator
Decide whether to slow releases or keep shipping, using the same burn-rate figure UptimeMonitor360 alerts on.
| Total budget | 43.2 min |
|---|---|
| Consumed | 18.0 min (41.7%) |
| Remaining | 25.2 min |
| Burn rate | 1.04× (1.0 = on track to spend exactly the budget) |
| Projected exhaustion | day 28.8 of 30 |
| Status | attention |
Budget = window × (1 − target). Burn rate compares consumption with the share of the window elapsed, the same figure UptimeMonitor360 uses for burn alerts.
Track error budgets automatically with SLO objectives and burn alerts. Free for 5 monitors, no credit card.
Start monitoringHow it measures
- Budget = window length × (1 − target).
- Burn rate = consumed budget share ÷ elapsed window share; above 1.0 the budget runs out before the window ends.
Limits
- Calendar months vary in length; pick the window your SLO document uses.
- Partial outages (degraded service) count only if your SLO defines them as bad minutes.
Troubleshooting
- Burn rate looks alarming after a short outage early in the window
- Early in a window any downtime shows a high rate. Look at the projected exhaustion day and the remaining budget as well.