For API teams who post on a status page while things are on fire
Status CadenceDid the page say it early, keep its promises and own it?
Paste one incident's public updates - time, status, message - with the components you flagged and the time the monitoring alert fired. Your browser checks the four-stage lifecycle, holds every next-update promise to the next post, measures the lag behind the alert and whether a third party said it first, and flags missing time zones, codename titles, vendor blame, named people, speculation and severity that is not breadth of impact. Then the rewrite, and the public postmortem.
The incident as it was posted free
The practice around it - a short interview free
The checks free
What the page flags
The gates
The updates and their promises
The components
Channels, postmortem depth and SLA minutes
Area by area
Your cadence table free
Every update with its gap, its next-update promise and whether the next post kept it - the lifecycle-completeness measurement the skill gates on.
Cadence (Markdown)
The rewritten timeline metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved incidents
How it works - and what is sourced
The checks follow the skill. Every incident runs through Investigating, Identified, Monitoring and Resolved, with timestamps. Every update names the time of the next one, and the page holds that promise to the next post, with five minutes of grace. The first public post should come minutes after the monitoring alert - a lag in tens of minutes means a person is still deciding whether to flip the page, and an outside aggregator reporting first is the failure the practice exists to prevent. Titles state the problem in plain language, never a ticket number or service codename; times carry a zone; updates state what is confirmed, own the failure without naming a vendor or a person, and acknowledge the impact.
Component severity is breadth of impact: degraded is slow for everyone, partial is broken for a subset such as one region, major is unavailable for everyone. The channel ladder starts at the page with email and RSS, promotes webhook push for developer audiences and SMS for enterprise contracts (deleted when there is neither), and moves out-of-band hosting first when the page shares your infrastructure. The postmortem defaults to a status-page summary, drops to a resolved note for a blip nobody outside felt, and rises to an engineering-blog write-up for a major outage or shaken trust. SLA minutes use a 30-day month: 43.2 minutes at 99.9%, 21.6 at 99.95%, 4.32 at 99.99%.