Skip to main content

Error Budget & SLO Burn Rate

Calculate error budget consumption and burn rate from SLOs. Enter values for instant results with step-by-step formulas.

Share this calculator

Formula

Burn Rate = (Budget Consumed %) / (Expected Consumption %)

Expected consumption is linear over the window (day 15 of 30 = 50%). Burn rate >1 means consuming faster than sustainable. Multi-window alerting catches both fast and slow burns.

Worked Examples

Example 1: Standard Web Service

Problem: SLO: 99.9%, 30-day window, 10M requests/month. Day 15: 5,000 failed requests, 30 min downtime.

Solution: Error Budget:\n100% - 99.9% = 0.1%\nRequests: 10M ร— 0.1% = 10,000 allowed failures\nTime: 30 days ร— 1440 min ร— 0.1% = 43.2 min allowed\n\nConsumed:\nRequests: 5,000 / 10,000 = 50%\nTime: 30 / 43.2 = 69.4%\n\nHigher of two: 69.4% consumed\n\nExpected (day 15 of 30): 50%\nBurn rate: 69.4% / 50% = 1.39x\n\nStatus: Elevated\nDays until exhausted: 30.6% / (69.4%/15) = 6.6 days

Result: 1.39x burn rate (Elevated) | 69% consumed | 6.6 days until exhaustion

Example 2: Critical Payment API

Problem: SLO: 99.99%, 7-day window, 1M transactions. Day 3: 50 failures, 2 min downtime.

Solution: Error Budget:\n100% - 99.99% = 0.01%\nTransactions: 1M ร— 0.01% = 100 allowed\nTime: 7 ร— 1440 ร— 0.01% = 1.01 min allowed\n\nConsumed:\nTransactions: 50 / 100 = 50%\nTime: 2 / 1.01 = 198% (OVER BUDGET!)\n\nTime-based exhaustion: 198%\nBudget exhausted - already over!\n\nBurn rate: 198% / 42.9% = 4.6x\n\nStatus: Critical\nAction: Reliability freeze, incident review

Result: 4.6x burn (Critical) | 198% consumed (OVER) | Budget exhausted

Example 3: Healthy Internal Service

Problem: SLO: 99.5%, 30-day window, 50M requests. Day 20: 100,000 failures, 60 min downtime.

Solution: Error Budget:\n100% - 99.5% = 0.5%\nRequests: 50M ร— 0.5% = 250,000 allowed\nTime: 30 ร— 1440 ร— 0.5% = 216 min allowed\n\nConsumed:\nRequests: 100K / 250K = 40%\nTime: 60 / 216 = 27.8%\n\nHigher: 40% consumed\n\nExpected (day 20): 66.7%\nBurn rate: 40% / 66.7% = 0.6x\n\nStatus: Excellent - Under budget!\n\nOpportunity: Can increase velocity,\ntake on riskier changes

Result: 0.6x burn (Excellent) | 40% consumed | Room for velocity

Frequently Asked Questions

What is an SLO?

Service Level Objective is a target reliability level, e.g., '99.9% of requests succeed.' SLOs should be customer-focused, measurable, and achievable. They're internal targets, unlike SLAs which are contractual commitments.

What is an error budget?

Error budget is the allowed failure rate derived from SLO. For 99.9% SLO, error budget is 0.1% of requests or ~43 minutes/month of downtime. It quantifies acceptable unreliability and balances reliability with velocity.

What is burn rate?

Burn rate measures how fast you're consuming error budget relative to expected pace. 1.0 = on track, 2.0 = twice as fast (will exhaust in half the window). High burn rates trigger alerts and may halt deployments.

How do I set SLO targets?

Base on user expectations and business needs. Start with current baseline, aim for achievable improvement. 99.9% is common for most services, 99.99% for critical infrastructure. Higher isn't always better - over-engineering wastes resources.

What happens when error budget is exhausted?

Common policies: freeze feature releases, redirect engineering to reliability work, require reliability review for any changes, increase testing requirements. Goal is to restore budget before resuming normal velocity.

How do I calculate downtime from SLO?

Monthly downtime = (100% - SLO%) ร— 43,200 minutes/month. 99.9% = 43.2 min/mo, 99.99% = 4.32 min/mo, 99.999% = 26 sec/mo. This assumes even distribution; incidents are typically clustered.

Background & Theory

The Error Budget & SLO Burn Rate Calculator applies the following established principles and formulas. Break-even analysis identifies the sales volume at which total revenue equals total costs, producing neither profit nor loss. The formula divides total fixed costs by the contribution margin per unit, where contribution margin equals selling price minus variable cost per unit. If a software product has $50,000 in monthly fixed costs and each licence generates $20 above its variable cost, break-even requires 2,500 unit sales per month. Above that threshold, each additional unit contributes directly to profit. Gross margin expresses the percentage of revenue remaining after direct cost of goods sold: gross margin equals revenue minus COGS, divided by revenue. A SaaS company with 80 percent gross margins retains $0.80 of every revenue dollar to cover operating expenses, while a manufacturer with 30 percent gross margins faces much tighter operating leverage. Customer acquisition cost (CAC) divides total sales and marketing expenditure in a period by the number of new customers acquired in that same period. Customer lifetime value (LTV) estimates the total profit attributable to a customer relationship. The standard formula multiplies average revenue per user (ARPU) by gross margin and divides by the monthly churn rate. A business with $50 ARPU, 75 percent gross margin, and 2 percent monthly churn has an LTV of $1,875. The LTV:CAC ratio benchmarks unit economics health; a ratio above 3:1 is generally considered sustainable, while ratios below 1:1 indicate the business is acquiring customers at a loss. Burn rate measures monthly cash expenditure net of revenue. Cash runway equals current cash reserves divided by net monthly burn. A company with $1.2 million in the bank burning $100,000 per month has twelve months of runway. The Rule of 40 is a benchmark for SaaS health: the sum of annual revenue growth rate (as a percentage) and profit margin (as a percentage) should equal or exceed 40. High-growth companies burning cash can still pass this rule if their growth rate compensates.

History

The history behind the Error Budget & SLO Burn Rate Calculator traces back through the following developments. Early economic thought centred on mercantilism, the 16th and 17th century doctrine that national wealth derived from accumulating precious metals through export surpluses and colonial extraction. Adam Smith's "Wealth of Nations" in 1776 dismantled this framework, arguing that genuine prosperity arose from specialisation, division of labour, and freely operating markets. David Ricardo extended Smith's work with the theory of comparative advantage in 1817, demonstrating mathematically that mutually beneficial trade was possible even when one country was less productive in every industry. Alfred Marshall's "Principles of Economics" published in 1890 provided the modern framework of supply and demand curves, consumer surplus, price elasticity, and marginal analysis, establishing neoclassical economics as the dominant academic paradigm for decades. The Great Depression exposed the limits of laissez-faire assumptions, and John Maynard Keynes's "General Theory of Employment, Interest and Money" in 1936 argued that private-sector aggregate demand failures required countercyclical government fiscal intervention to restore full employment, shifting the policy consensus toward active macroeconomic management. The post-World War II decades constructed mixed-economy models combining market allocation with expanded welfare states and Keynesian demand management. Milton Friedman and the Chicago School challenged this consensus from the 1960s onward, championing monetarism and arguing that stable money supply growth was superior to discretionary fiscal policy. Their influence shaped the deregulatory and privatisation policies of the Reagan and Thatcher eras in the 1980s. Behavioural economics emerged through the work of Daniel Kahneman and Amos Tversky in the 1970s and Richard Thaler in the 1980s, using psychology to demonstrate that real human decision-making deviates systematically from rational-actor models through heuristics and biases. The rise of the internet and mobile platforms in the 2000s and 2010s created a new category of platform economics, where network effects, near-zero marginal cost of digital goods, and two-sided market dynamics generated winner-take-most competitive outcomes requiring new analytical frameworks for business valuation.

References