Skip to content

Error Budget

In one line

Error budget = 1 - SLO. It is the allowed failures. Under budget → ship features. Over budget → focus on reliability.

In simple words

An error budget is the maximum amount of unreliability your service is allowed. It is calculated as 1 - SLO. For 99.9% SLO, the error budget is 0.1%.

Under budget (few failures) → ship new features. Over budget (too many failures) → stop features, focus on reliability. Near the limit → be cautious.

Example: 10M requests/day, 30 days, SLO 99.9% → budget = 300M × 0.1% = 300,000 allowed failures. The error budget makes reliability a shared, measurable decision.

Example

javascript
const errorBudget = 1 - 0.999;  // 0.001
const allowed = totalRequests * errorBudget;
const remaining = allowed - failedRequests;
const action = remaining / allowed > 0.5 ? 'ship_features' : remaining > 0 ? 'be_cautious' : 'freeze_and_fix';

The error budget tracks allowed vs consumed failures. >50% remaining → ship features. >0% → cautious. 0% → freeze features and fix reliability.

Common confusions

  • Confused with: SLO

    The difference: SLO is the reliability target (99.9%). Error budget is the complement — allowed unreliability (0.1%). SLO says what you must achieve; error budget says what you can spend.

Related terms

Related Resources

Related Lessons

  • SRE

    Error budgets.

Decode error messages

Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.

View errors

← Back to glossary