SLA & SLO Uptime Reports

What SLA / SLO Reports Are

The SLA / SLO Reports page turns the raw results of your monitors into the language your business and customers care about: uptime against a target. For each monitor you set an SLO target (for example 99.9%), and LoadFocus tells you whether you are meeting it, how much of your error budget is left, alerts you when a target is breached, and emails a recurring SLA report to your team.

SLA / SLO Reports are a paid feature. On the free plan the page invites you to upgrade.

Open it from SLA Reports in the sidebar, or go to /sla.

The report table

Each row is one monitor (an API check) or a check group, evaluated over the time window you select at the top right.

• Monitor — the API check or check group this row reports on. Group rows show the number of member checks in parentheses.
• Uptime — the time-weighted percentage of successful checks over the selected window. A check that was down for one hour out of a 30-day window lowers uptime in proportion to that hour. When there are no results in the window, uptime shows a dash (—).
• SLO target % — your uptime objective for this monitor, for example 99.9. Type a value to set it; everything else on the row (error budget, status, breach alerting) is measured against this target. Leave it blank to stop tracking an SLO for that monitor.
• Error budget — how much of your allowed downtime has been consumed in the window. If your target is 99.9% over 30 days, your budget is roughly 43 minutes of downtime; the bar fills as that budget is used. 0% means none used, 100% means the budget is exhausted (and the SLO is breached).
• Status — a quick verdict for the window: OK (meeting the target), Breached (error budget exhausted), or No data (no results in the window).

How uptime and error budget are calculated

Uptime is time-weighted: each result counts for the time until the next result, so a short outage on a 1-minute check and the same outage on a 5-minute check affect uptime consistently. The error budget is 100% − target worth of downtime; the percentage consumed is the share of that allowance already spent in the window.

Breach alerting

The Breach Alert column lets each monitor notify you the moment it is about to miss its SLO, without you having to watch the page.

• Alert on breach — toggle on to enable SLO breach alerting for this monitor.
• Budget consumed % — the threshold at which the alert fires. 100 means "alert only once the entire error budget is gone"; a lower value (for example 80) warns you earlier, while you still have budget left to react.
• Window — the rolling period over which the budget is evaluated for alerting: 24h, 7d, or 30d.

Breach alerts are routed to the check's own alert channels (the same email, Slack, PagerDuty, Opsgenie, Discord, or webhook channels you configured for the check) under a dedicated slaBreaches event, so they are independent from up/down and SSL alerts. You will also receive a recovery notification when the monitor climbs back above its target. See Alert Channels to configure where alerts go.

Time window and export

• Time window (top-right selector) — the reporting period used for every row: Last 24h, Last 7 days, Last 30 days, or This month (the current calendar month). All periods are computed in UTC.
• Export CSV — download the current table (uptime, SLO target, error budget and status for every monitor) as a CSV file, ready for a spreadsheet or a customer-facing SLA review.

Scheduled SLA reports

Below the table, Scheduled SLA Report emails a recurring summary to your team so nobody has to open the dashboard.

• Enable — turn automatic SLA reports on or off.
• Cadence — how often the report is sent: Weekly or Monthly. A report always covers the most recently completed period (last week or last month), never a period that is still in progress.
• Timezone — the timezone used to decide period boundaries and the send time, for example UTC or Europe/London.
• Recipients (team members) — who receives the report. Only members of your team can be selected, which keeps the report inside your organisation and gives every recipient a way to opt out.

Each scheduled email lists the monitors, their uptime against target for the period, and how many SLOs were breached, with a link back to this page.

Notes

• All windows and report periods are evaluated in UTC.
• A row that shows No data has no check results in the selected window — confirm the monitor is actually running, not just saved (see Understanding API Check Results).
• SLO targets, breach-alert settings, and report settings are saved as you change them.