Network SLO Compliance Calculator
Compare measured availability against an SLO and see the compliance margin plus how much downtime is left in the period.
About Network SLO Compliance Calculator
The allowance is fixed by the SLO and the period length, so compliance is a subtraction. Comparing the share of budget spent with the share of the period elapsed gives the burn ratio, which flags a breach before it happens rather than after. A month is compliant until it suddenly is not, and the burn ratio is what tells you to freeze risky changes while there is still budget to protect.
Formula
Network SLO Compliance
allowed downtime = period × (1 − SLO); achieved availability = (elapsed − downtime) ÷ elapsed.
- SLO
- Availability objective for the period
- burn ratio
- Budget consumed divided by the fraction of the period elapsed
Worked example
With the default values below, Network SLO Compliance Calculator returns Availability Achieved So Far of 99.9460%. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Availability SLOaccepts 50–100 %
- 99.95 %
- Measurement periodaccepts 1–366 days
- 30 days
- Downtime recorded so faraccepts 0–500,000 minutes
- 14 minutes
- Days elapsed in the periodaccepts 0.1–366 days
- 18 days
Results
- Availability Achieved So Far
- 99.9460%
- Downtime Allowed in the Period
- 21.6 minutes
- Downtime Remaining
- 7.6 minutes
- Downtime Budget Consumed
- 64.8%
- Compliance Status
- At risk — burning budget 1.08 times faster than the period elapses
Step by step
- 1Values used
- 2Network SLO Compliance
- 3Availability Achieved So Far= 99.9460
- 4Downtime Allowed in the Period= 21.6 minutes
- 5Downtime Remaining= 7.6 minutes
- 6Downtime Budget Consumed= 64.8
- 7Compliance Status= At risk — burning budget 1.08 times faster than the period elapses
Assumptions and limits
- The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or fees or charges into account.
- Figures are rounded for display to 4 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is Network SLO Compliance calculated?
allowed downtime = period × (1 − SLO); achieved availability = (elapsed − downtime) ÷ elapsed. The allowance is fixed by the SLO and the period length, so compliance is a subtraction. Comparing the share of budget spent with the share of the period elapsed gives the burn ratio, which flags a breach before it happens rather than after.
Why does Network SLO Compliance matter?
A month is compliant until it suddenly is not, and the burn ratio is what tells you to freeze risky changes while there is still budget to protect.
What values do I need to enter?
This calculator takes 4 inputs: Availability SLO, Measurement period, Downtime recorded so far, Days elapsed in the period. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Related Calculators
You might also need
- SLA Availability CalculatorCommonly used together
- Maintenance Window CalculatorCommonly used together
- Network Error Budget CalculatorCommonly used together
- Telecom Network Health Score CalculatorCommonly used together
- Network Compliance Score CalculatorAlso in Network Operations
- Power over Ethernet (PoE) Budget CalculatorAlso in Network Operations
