About this block

Past Incidents List is the Acme incident history: seven resolved incidents grouped by June, May, and April 2026, each row showing an INC ID badge in outline, the incident title, a duration chip, the resolved-at timestamp, an impact summary, and a View postmortem link. June carries Elevated authentication latency (38 min, ~12% of EU users) and Webhook delivery delays (1 hr 12 min, 847 endpoints). May adds three incidents including API rate limit headers missing at just 6 min. April closes with a CDN origin timeout cascade at 1 hr 41 min. An honest footer note reads: every incident lasting more than 5 minutes gets a public postmortem, published within 5 business days and not edited after.

Incidents are grouped into a MonthGroup array. Duration is a plain string so it accommodates both minutes and hours without parsing logic.

When to use

Reach for this block on the status or ops history page, wired to your incidents API ordered by resolved date descending. Link postmortem URLs to your internal wiki or a public postmortem page.

A natural flow around it on an Application Pro page:

Before

• Component status list
• App shell

After

• Activity
• Admin moderation

What you can display

One strong use is the resolved-incidents log with postmortem links. Other history list configurations:

• Deployments log. Grouped by week, each row with a version badge, deployer avatar, and rollback link.
• Audit changelog. Config changes timestamped and attributed to a user, read-only by policy.
• Maintenance history. Completed windows with affected components and customer impact notes.

Tip: the immutability note on the postmortem footer is the strongest trust signal on the whole page, say it plainly and mean it.