Summary · api.example.com · Q2 2026
| Metric | Value |
|---|---|
| Availability, gross | 99.925% |
| Availability, after excluding announced maintenance | 99.994% |
| Confirmed incidents | 1 |
| Maintenance windows | 1 |
| Check interval | 30 s |
| Checks executed | 1,572,480 (6 regions, 91 days) |
| Regions confirming | na (Newark), eu (Frankfurt), as (Singapore), sa (São Paulo), af (Johannesburg), oce (Sydney) |
Windows
| Window (UTC) | Cause | Duration | Counted against SLA |
|---|---|---|---|
| 2026-05-03 02:41:12 to 02:48:24 | incident, quorum-confirmed | 00:07:12 | yes |
| 2026-05-17 22:00:00 to 23:30:00 | maintenance, announced | 01:30:00 | no, excluded |
The exclusion matches an announced maintenance window and carries its announcement timestamp and real boundaries.
Incident record
| Time (UTC) | Event |
|---|---|
| 02:40:42 | check fails, eu (Frankfurt) |
| 02:41:12 | quorum confirms, na (Newark) and as (Singapore) agree. Incident opens. |
| 02:41:12 | page sent, push |
| 02:44:03 | acknowledged |
| 02:48:24 | recovery confirmed across regions. Incident closes. |
| 02:55:00 | post-mortem opened, 2 action items |
The window in the SLA table above, 02:41:12 to 02:48:24, runs from confirmation to confirmed recovery. An incident starts at the quorum confirmation, not at the first failed check or a rounded minute. The 30 seconds before confirmation are visible in the record, neither silently stretched nor shrunk. The sample monitor runs a policy of 1 failed check per region with a quorum of 2 regions, not the default of 2 consecutive checks.
Why this holds up
- Timestamps come from the monitoring system itself, not from a human recollection.
- Announced maintenance stays visible and is excluded by its window.
- Later false-positive curation is a separate action with an actor, a reason, a previewed before-and-after effect, and a reversal.
- Availability is floored, never rounded up. An SLA number should be a lower bound you can defend.
- Linked status-page components use the same monitor and incident record. Publishing remains an explicit action.
Recompute the math yourself: the quarter’s 91 days are 131,040 minutes. Confirmed incident time of 7:12 and announced maintenance of 90:00 make 99.925% gross. Excluding the announced maintenance turns it into 99.994% counted.
This is an editorial example, not an assurance report or a regulatory filing. Each monitor view offers a PDF report for 7, 14, 30, or 90 days on every plan. The report is not signed or certified. Perstat provides an organization CSV plus manifest manually, on request.