Skip to content
Calcrivo

Network Error Budget Calculator

Turn an SLO into a concrete error budget in minutes and failed requests, and track the burn rate against it.

Inputs

%
days
requests
minutes
%

Error Budget

43.2minutes

Failed Requests Allowed

500,000

Budget Remaining

21.2minutes

Burn Rate

1.02× budget pace

Budget Status

Elevated burn — the budget will run out before the period ends

Step by step

  1. Values used

    Service level objective = 99.90 %; Budget period = 30 days; Requests in the period = 500,000,000 requests; Budget consumed so far = 22 minutes; Period elapsed = 50 %

  2. Network Error Budget

    error budget = (1 − SLO) × period; allowed failures = (1 − SLO) × requests; burn rate = share of budget spent ÷ share of period elapsed.

  3. Error Budget

    = 43.2 minutes

  4. Failed Requests Allowed

    = 500,000

  5. Budget Remaining

    = 21.2 minutes

  6. Burn Rate

    = 1.02 × budget pace

  7. Budget Status

    = Elevated burn — the budget will run out before the period ends

How it works

An SLO of 99.9% over 30 days is 43.2 minutes of allowed failure, and the same fraction applied to request volume gives the number of failed requests that fit inside the objective. The burn rate normalises consumption against elapsed time so that 1.0 is on-pace regardless of where you are in the period. Error budgets convert reliability arguments into arithmetic: while budget remains you can ship changes, and when it is gone the answer to a risky change request is no.

Formula

Network Error Budget

error budget = (1 − SLO) × period; allowed failures = (1 − SLO) × requests; burn rate = share of budget spent ÷ share of period elapsed.

1 − SLO
The unreliability you are explicitly allowed
burn rate
1.0 means exactly on pace to exhaust the budget at period end

Frequently Asked Questions

How is Network Error Budget calculated?

error budget = (1 − SLO) × period; allowed failures = (1 − SLO) × requests; burn rate = share of budget spent ÷ share of period elapsed. An SLO of 99.9% over 30 days is 43.2 minutes of allowed failure, and the same fraction applied to request volume gives the number of failed requests that fit inside the objective. The burn rate normalises consumption against elapsed time so that 1.0 is on-pace regardless of where you are in the period.

Why does Network Error Budget matter?

Error budgets convert reliability arguments into arithmetic: while budget remains you can ship changes, and when it is gone the answer to a risky change request is no.

What values do I need to enter?

This calculator takes 5 inputs: Service level objective, Budget period, Requests in the period, Budget consumed so far, Period elapsed. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

You might also need

Related Calculators

Network SLO Compliance CalculatorSLA Availability CalculatorChange Impact Calculator