Availability SLO

Computation

Each check produces an up or down result per region. The availability fraction is:

availability = up_checks / total_checks

The fraction is computed over a rolling window (default 7 days). 99.95% means 0.05% of check results in the window were down.

Configuration

Open the monitor edit form and scroll to SLO Settings. Availability fields:

slo_target_percent — SLO target (%)

Minimum acceptable availability. Common values: 99.9, 99.5, 99.0.

slo_window_days — Rolling window (days)

Rolling look-back period. Default: 7. Shorter windows react faster; longer windows smooth noise.

Both fields are tunable on Business and Founder plans only. Free and Pro monitors use 99.5% / 7 days.

Availability panel

Budget remaining

Percentage of total error budget not yet consumed. At 99.5% / 7 days the total budget is 0.5% × 604,800s ≈ 50 min. 10 min consumed → ~80% remaining.

Used / Allowed

Raw downtime consumed vs. total allowed, in human-readable format (e.g., "10 min used / 50 min allowed").

Burn rate

Current consumption rate relative to sustainable rate. 2.0× = consuming twice as fast as the SLO allows.

Burn-rate classes

Normal

Burn rate ≤ 1.0×. On track to end the window with budget remaining.

Warning

Burn rate > 1.0×, budget not yet exhausted. Trending toward breach.

Exhausted

Error budget fully consumed; SLO target missed for this window.

Insufficient data

A monitor with insufficient check history shows a Collecting data placeholder instead of budget figures. Burn-rate evaluation is gated by warmup — see Burn-rate incidents.

Check interval and SLO precision

Each failed check creates an interval of unknown downtime bounded by the check spacing. A 5-minute interval with one failed check charges the worst-case 5 minutes against the budget; the actual outage may have lasted seconds.

Per-plan minimum check intervals: see Billing & Plans. For detection gaps between checks, see What 5-minute check intervals actually miss.

Plan tier matrix