Incident History List

About this block

Incident History List is the reliability record kept in public. Three incidents run down a rail, each with date, a severity chip, duration, an impact sentence that distinguishes delayed from lost, and a postmortem link. The lede inverts the usual fear, the months you do not see were quiet, sparse history as the brag it actually is.

The incidents are one array. Impact sentences carry the craft, sends delayed, none lost is the difference between an incident and a catastrophe, written precisely. Every entry must link a real postmortem, the link is the credibility.

When to use

Reach for this block on status pages below current-status-list, and in trust centers where the postmortem culture is part of the pitch. A short honest list converts better than an empty one, buyers distrust vendors with no recorded incidents more than vendors with three explained ones.

A natural flow around it on a Marketing Pro page:

Before

• Status and performance blocks covering the present

After

• SLA commitments showing the targets the record is judged against
• Subscribe to updates for readers who want the next one in real time

What you can display

One strong use is the last year of platform incidents. Other records:

• Security disclosures. Resolved vulnerabilities with disclosure timelines, for a security page.
• Deprecation log. API changes that broke things, owned and dated.
• Service credits issued. SLA misses with their remedies, the deepest version of this honesty.

Tip: write impact lines that separate delay from loss, that distinction is the entire reassurance of a good incident record.