Maintenance and curation
Maintenance windows
Section titled “Maintenance windows”Announce a window and, for its duration, no new incidents open and the time is SLA-neutral. The window still lands on the record and can show as a banner on your status page, with a visibility toggle per window. Planned work is visible, not counted against you, and never silently excluded.
Outage curation
Section titled “Outage curation”Measured downtime is kept separate from the incident story. A false positive can be discarded with a reason; before it is applied, the product previews the uptime effect, before and after. Every discard is soft, carries the actor, and is reversible. A restored window is exactly the window that was discarded, on its real boundaries.
History
Section titled “History”Three tabs carry the full story, org-wide and per monitor, deep-linkable:
- Timeline: raw status changes per region, unedited.
- Outages: the curated downtime record, discards included and labeled.
- Activity: the configuration history, including “report discarded” and “report restored” with who and when.
Why corrections are visible
Section titled “Why corrections are visible”Corrections are easier to review when their actor, reason, effect, and reversal remain visible. Perstat makes that narrower product claim; it does not claim the record is tamper-proof or that an auditor must accept a correction. Continue with the documented boundaries under evidence and retention.