error budget tracker
Plug in your SLO and past incidents. See budget consumed, how it recovers as incidents age out, and how much further outage you can still absorb.
// danger zone
// config
your slo target and the rolling window you're tracking against.
%
→ budget40m
// incidents
click a row to edit, click again to close. add as many as you've had.
no incidents yet.
// status · 2026-04-26
today's math: budget you had, how much you've burned, what's left.
budget40m
consumed0s (0.0%)
remaining40m (100.0%)
// budget over rolling window#n = incident, matches list above
y = % of error budget remaining · x = time. past incidents eat budget; it recovers as they age out.
100%50%25%0%
-28dnow+7d+14d+28d
// forecast (no new incidents)
budget at future dates, assuming no new incidents happen.
now100.0%
+7d100.0%
+14d100.0%
+28d100.0%
// what can you still absorb
how long an outage of a given severity you could take from here.
full outage40m100% of traffic
partial1h 21m50% of traffic
degraded6h 43m10% of traffic
// policy
healthy ≥ 50% · at risk 25–50% · freeze < 25%
"freeze" = convention to pause risky releases while budget is low.
healthy(≥ 50% remaining)
// summary
self-contained snapshot. paste anywhere — reads without the tool.
// share
permalink that restores this exact state. send it anywhere.