Skip to content
Calcrivo

Network SLO Compliance Calculator

Compare measured availability against an SLO and see the compliance margin plus how much downtime is left in the period.

Inputs

%
days
minutes
days

Availability Achieved So Far

99.9460%

Downtime Allowed in the Period

21.6minutes

Downtime Remaining

7.6minutes

Downtime Budget Consumed

64.8%

Compliance Status

At risk — burning budget 1.08 times faster than the period elapses

Step by step

  1. Values used

    Availability SLO = 99.95 %; Measurement period = 30 days; Downtime recorded so far = 14 minutes; Days elapsed in the period = 18 days

  2. Network SLO Compliance

    allowed downtime = period × (1 − SLO); achieved availability = (elapsed − downtime) ÷ elapsed.

  3. Availability Achieved So Far

    = 99.9460

  4. Downtime Allowed in the Period

    = 21.6 minutes

  5. Downtime Remaining

    = 7.6 minutes

  6. Downtime Budget Consumed

    = 64.8

  7. Compliance Status

    = At risk — burning budget 1.08 times faster than the period elapses

How it works

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

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.

You might also need