Skip to content
Plaza docs

Status template — resolved

Use when the incident is fully resolved, monitoring has shown sustained recovery, and the public timeline is closing.

Title

Section titled “Title”

<short noun phrase> — resolved

Examples:

  • “Elevated payout latency — resolved”
  • “Webhook delivery delays — resolved”

Body

Section titled “Body”
The incident is resolved.


Summary: <one paragraph. What happened, what the customer-visible impact
was, what fixed it. Five sentences max.>


Duration: <HH:MM UTC, YYYY-MM-DD> to <HH:MM UTC, YYYY-MM-DD>. Total: <X
minutes / hours>.


Affected: <surfaces, recapped from the investigating entry. If the impact
turned out narrower than initially posted, say so explicitly: "Initial
reports suggested broader impact; the affected surface was actually only
…">


Postmortem: <link, if SEV-0 or SEV-1. "A public postmortem will be posted
within 14 days." Or: "An internal postmortem is in progress; we will
share notable findings.">

Notes

Section titled “Notes”
  • Do not post “resolved” until the dashboards have been clean for the per-severity hold time (30 min for SEV-1; 60 min for SEV-0).
  • Name what was wrong. Do not say “an issue was resolved” without saying what the issue was. Customers can tell.
  • If the postmortem reveals additional impact not noted at the time, file an addendum on the incident timeline.
  • Pin the resolved entry to the status page for at least 24 hours so customers reading after the fact can see the timeline.
  • Tone per AESTHETIC.md §8.

Note on ownership

Section titled “Note on ownership”

A7 owns the status page configuration in infra/status/. These copy templates live in docs/operations/status-templates/ so A8 can ship them without colliding with A7’s tree. A7 may re-home or symlink these into infra/status/ later as needed.