Features

An incident cycle documented start to finish.

Every incident follows a timestamped cycle — investigating → identified → monitoring → resolved — each step attributed to the team member who performed it. Nothing gets communicated without a trace.

INCIDENT #142

Latence élevée — API paiement

Major
Investigating14:02 · Kevin R.
Identified14:11 · Kevin R.
Monitoring14:34 · Sarah L.
Resolveden attente

How it works.

01

Confirmed detection

Multi-region monitoring triggers the incident, or a user reports it via "Report an issue".

02

Documented cycle

4 timestamped steps, each attributed to a team member — a reviewable history, not just a status.

03

Multi-channel communication

Real-time status page, email subscription, RSS feed, and maintenance windows announced ahead of time.

What's included.

Configurable escalation

Anti-spam cooldown and daily summaries — the alert gets through without flooding the team.

9 alert channels

Email, Slack, Discord, Teams, Telegram, PagerDuty, Splunk, Google Chat, Ntfy.

Manual incidents

Declare an incident yourself, even when automated monitoring didn't see it coming.