Search blocks by description or jump to a page.
SLA card showing the uptime target, actual this period, error budget bar, and the last published breach record.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Sla Summary Card shows the full SLA picture for Jun 2026: a 99.9% uptime target beside the actual 99.94% marked On target, then the error budget bar at 60% consumed (17.5 of 43.8 minutes remaining), resetting Jul 1. The last breach section names the incident honestly: Webhook delivery on May 3 for 17 min 22 sec, tagged with its postmortem ID PM-2026-0503, and a permanent note that all breaches are published and historical records are never removed.
Budget math is derived from the data constants so the bar stays consistent with the numbers. The breach record and the never-removed note are the copy that turns an SLA page from a formality into a trust signal.
Reach for this block on a status or settings page where you publish SLA performance to customers or internal stakeholders. Wire the budget values to your uptime monitoring API.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the monthly uptime SLA card. Other health summary cards:
Tip: naming the last breach in the card itself, rather than linking to a separate page, signals that the team does not hide incidents.