Error Budget

/
Glossary
/
Error Budget

An error budget is the amount of unreliability a service is permitted before reliability work takes priority over feature work. It is the gap between a service's target reliability and 100%, spent deliberately rather than treated as accidental downtime. In site reliability engineering, the error budget connects measured reliability targets, residual risk, and release velocity for product and platform engineering teams.

The framework was introduced in the Google SRE Book to make reliability-versus-velocity tradeoffs explicit for shipping teams. Perfect availability is the wrong default for most production services, because the cost of approaching it rises sharply while marginal customer benefit shrinks. A Service Level Objective of 99.9% creates a 0.1% error budget, about 43 minutes every 30 days according to Google Cloud CRE. Teams spend that budget on faster releases until feature work must pause.

Availability and latency budgets still matter for infrastructure health, yet AI-enabled systems can stay up while returning wrong, stale, or unsafe answers to real users. Traditional coverage stops at uptime and latency, so a service can meet every infrastructure SLO and still fail its users in production. Mature programs track answer quality regression, fallback rate, and policy compliance with burn thresholds. Semantic failure then consumes budget like outages, instead of hiding behind green weekly reviews.

Faster incident handling protects the same reliability budget without freezing the product roadmap while the error budget is burning. Across customers operating at petabyte scale, Traversal delivers 85%+ improvement in MTTR, leaving more of each period's error budget available for planned product risk.

Related

Service Level Objective (SLO)

A Service Level Objective (SLO) is a target value for a service's reliability: for example, "99.9% of requests will complete in under 200 milliseconds over a 30-day rolling window." SLOs are the foundational unit of measurement in modern reliability engineering and the input that defines a service's error budget.

Site Reliability Engineering (SRE)

Site Reliability Engineering (SRE) is the discipline of applying software engineering practices to operations problems: automating toil, defining measurable reliability objectives, balancing velocity against risk through error budgets, and treating production reliability as an engineering function rather than a reactive support burden.

MTTR (Mean Time to Resolution)

MTTR (Mean Time to Resolution) is the average time it takes to fully remediate a production incident: from initial detection through investigation, remediation, and verification that the issue has been corrected. It is the headline metric for incident response programs.

Toil

Toil is the manual, repetitive, automatable operational work that scales with service growth: work that produces no enduring engineering value, consumes time that could be spent on higher-leverage activity, and accumulates as a structural tax on engineering capacity.