How much can break?

An SLOService Level Objective — a target for how reliable a service should be, like 99.9% of requests served OK over a month. is a promise; the error budgetThe flip side of the SLO: the small fraction you're allowed to fail. Spend it on risky deploys; run out and you've broken the promise. is the slack it leaves you. Pick a target and see exactly how much downtime — or how many failed requests — you're allowed before you've broken it, and how fast you're spending it.

Target
Keep% available over awindow.
That's an error budget of 0.28% — up to 2h of downtime per 30 days.
Allowed downtime
Per periodDowntime
day
3m 59s
week
27m 55s
30 dayswindow
2h
quarter
5h 59m
year
1d
Budget burnBurn rate: how fast you're spending the budget relative to time. 1× lands you at empty exactly on reset day; 2× burns it in half the window.
Window50% in
So far:of downtime.
1h 48mBudget left
10.03%Used
0.2×Burn rate
On trackOn track at 0.2× the budgeted pace, with 1h 48m to spare.
based on the SRE error-budget model