Maintenance and curation

Planned work does not count against you, false positives can be discarded with a reason, and every correction is logged and reversible.

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

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

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 audit, including “report discarded” and “report restored” with who and when.

Why corrections are visible

An availability number you can defend is one whose corrections survive scrutiny. Perstat does not claim the record is tamper-proof; it claims every change to it is attributed, reasoned, and undoable, which is what a reviewer actually checks. The audit half of this story continues on evidence and retention.