Incidents

4 open

4

Open

2

Mitigated

7

Resolved today

Severity 1

SEV1

Elevated 5xx on the ingest API

ingest-eu-central · started 14:02 UTC

41m MO TS Investigating
SEV1

Scheduled exports failing for large workspaces

export-worker · started 12:31 UTC

2h 12m DK Mitigated

Severity 2

SEV2

Dashboard load times above 3s in ap-southeast

web-ap-southeast · started 11:04 UTC

3h 39m LR Monitoring
SEV2

Webhook retries queued behind a slow consumer

webhook-dispatch · started 09:48 UTC

4h 55m RG Identified

Severity 3

SEV3

Stale avatars served from the CDN edge

cdn · resolved 08:12 UTC

22m HB Resolved
Full incident history
">

The prompt

Build an incident management board with Tailwind CSS. The header has a title, a live pill with a pulsing red dot reading how many incidents are open, and two buttons — a bordered "Subscribe" and a dark "Declare incident". Below, three summary tiles for open, mitigated and resolved-today counts with muted labels. The main list groups incidents by severity: a small uppercase group heading with a coloured square, then rows in a bordered card. Each row shows a severity chip, the incident title in medium weight, a muted line with the affected service and start time, a duration in monospace, a small stacked avatar pair for responders, and a status pill on the right. Include two Sev-1, two Sev-2 and one Sev-3 example, with the resolved one dimmed and struck through in its title. End with a link to the full timeline.

Paste it into Claude, Cursor, v0 or any AI coding tool. Prefer the finished markup? .