Incidents · Pro+
SLO / error-budget impact per incident
Statuspage.io records that an incident happened. StatusPulse computes how much it cost you — in error-budget terms, against your SLA, using your actual probe data.
Why you need it
On every incident detail page, a per-component "SLO impact" table joins probe results from the incident window to your configured SLA targets.
- Probe-derived uptime. Per-component uptime % during the incident window using the same Up/Degraded/Down counts the StatusReportBuilder computes elsewhere.
- Downtime in window. Failed-share multiplied by window length — honest estimate without per-check interval metadata.
- Error budget burned. Share of the monthly error budget consumed by the incident. Bold + coral when burn exceeds 100% so a single budget- blowing incident is visible at a glance.
- SLA breach badge. Components whose uptime in window fell below the configured SLA target get a "SLA breached" tag.
Sort order: SLA-breached first, then by budget-burn descending — the worst impact rises to the top.
Where it pays off
The "how bad was this really?" answer you actually need:
- Incident review. Was this a 30-minute inconvenience or did it eat the month's reliability budget?
- Customer-facing SLA conversations. "We breached the API gateway SLA target — here are the numbers."
- Capacity / investment decisions. Repeated budget-burn on the same component is a priority signal nothing else surfaces this clearly.
Available on Pro+. Already on StatusPulse? See the full config in Help →
Related
Try SLO / error-budget impact per incident in StatusPulse
5 probes, 1 status page, forever. No credit card. US or EU host — you choose.