Compare measured availability against an SLO and see the compliance margin plus how much downtime is left in the period.
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.
Network SLO Compliance
allowed downtime = period × (1 − SLO); achieved availability = (elapsed − downtime) ÷ elapsed.
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.
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.
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.