Evidence and retention

Exclusion windows with real boundaries, availability floored instead of rounded, and retention that is enforced twice.

Window boundaries are real

An incident’s SLA window runs from quorum confirmation to confirmed recovery, the same boundaries you were paged on. An exclusion window derived from a discarded false positive is computed per affected region: from the last good check before the incident to the first good check after it. Nothing is stretched to a flattering minute.

The math

Availability is floored, never rounded up: an SLA figure should be a lower bound you can defend. The sample SLA report shows the full structure with numbers that add up; hand it to anyone and let them recompute it.

Retention

Availability history is retained per plan: 7 days (Free), 30 (Pulse), 90 (Sentinel), 1 year (Command), 2 years (Enterprise). Retention is enforced twice: expired data is pruned, and reads clamp to the window, so a report can never quietly draw on data the plan does not carry. Long windows are served from daily rollups, so a 365-day view is fast without approximating.

Export

Availability evidence is exportable on request today; self-service export is the stated next step. If you leave, request a final export and we delete: the exit is on the security page, stated as policy.

What this is, and is not

Perstat produces the independent availability evidence that feeds an assurance report or a DORA incident notification. It is not the report itself and it does not make you compliant; the evidence page for leadership draws that boundary precisely.