SLA Uptime Reporting Tools
SLA Reports compile monthly uptime against your target, with planned maintenance already excluded, so the number you hand to a customer or an internal stakeholder is defensible the moment they ask how it was calculated. Active monitors get a full Met/Missed verdict and an error budget in minutes; heartbeats appear in the same table with uptime and downtime, but no target or budget — heartbeat SLA targets aren’t a feature yet.
SLA Report Metrics
Pick a month — it defaults to the current one — and see uptime against your SLA target for every active monitor, with maintenance windows already excluded from the math. Download this SLA compliance report as CSV evidence whenever a customer or an internal audit asks for it, instead of reconstructing the numbers by hand.
- Monthly uptime vs. target — every active monitor’s uptime, to three decimal places, against the 90%–99.999% target you set for it.
- Maintenance excluded automatically — estimated maintenance minutes are removed from the month’s available minutes before anything else is calculated.
- Exportable CSV — download evidence for any month, ready to attach to a customer report or an internal review, pulled from the same figures as the API, not screen text.
- Per-monitor granularity — uptime, target, Met/Missed, downtime minutes, error budget, incident count and longest incident, one row per monitor.
SLA Error Budget Metrics
The error-budget bar has no independent axis — its fill is consumed minutes divided by total budget, clamped 0% to 100%, accent-colored while the target is met and red once it’s missed. That means a fully filled bar can read as exactly exhausted or as over budget; the exact used and remaining minutes above the bar are what settles it. Pair incident count with longest incident: a high count points to recurring instability, a dominant longest value points to one concentrated outage.
- Uptime formula — up checks ÷ (up + down checks) × 100, with maintenance checks excluded entirely.
- Error budget — effective minutes × the target’s allowed failure percentage; downtime is the consumed share, remaining can go negative.
- An em dash means unevaluated — usually no target set, or no checks included that month, not automatically a clean record.
- In-progress months — open-incident duration is clamped to now, but the denominator stays the full month’s minutes.
SLA Reports and Status Pages
An SLA Report proves availability internally or to a specific customer. A Status Page does the same thing publicly and continuously — showing live incident state and a rolling uptime percentage for anyone who wants to check.
- Same underlying data — the report and the page both reflect the same monitors and incidents.
- Different audiences — an SLA report for a contract, a status page for everyone else.
- Subscribers stay informed — without you writing an update by hand during an incident.
download, ready for a customer or an internal audit
No manual reconstruction of uptime numbers — the report already excludes maintenance and breaks it down per monitor.
See Maintenance WindowsReady to hand over uptime evidence that holds up?
Free check · 7-day trial · card required