Glossary · Incidents and alerting

What is a postmortem?

Incident review

A postmortem, also called an incident review or retrospective, is a written account after an incident of what happened, why, how it was handled and what will change so it doesn’t happen again.

How it works and why it matters

A useful postmortem has a timeline with times, the impact (who was affected and for how long), the contributing causes, what went well and what didn’t, and a short list of actions with owners and dates.

Postmortems are blameless: they ask how the system and the process allowed the mistake, not who made it. People who fear blame leave out details, and the details are where the fixes are.

Publishing a short version builds trust. Customers who were affected want to know the outage was understood and what changes; a clear public review often does more for trust than a perfect uptime record.

How Uptimecheck helps

After an incident in Uptimecheck, write an incident review: what happened, why, and what you’re changing. Keep it for the team, or show it under the incident on your status pages. The incident’s timeline of checks, alerts, acknowledgements and notes gives the review its times.

See Incident management

14-day free trial · No credit card required

Read more in the guides

Guides 5 min read

Incident Communication: A Plan and Templates for Every Stage

How to tell customers about an outage: who speaks, how often, on which channel and in what words. A one-page plan, severity levels, update cadence and ready-to-use templates for status pages, email and social media.

Read

Questions

When should you write a postmortem?

For every incident above a set severity, for any incident customers noticed, and for near misses that could have been serious. Write it within a few days, while people remember.

What does a blameless postmortem mean?

It looks for the conditions that made a mistake possible, such as a missing check, an unclear runbook or a risky default, instead of naming the person who made it.

Should a postmortem be public?

A public version, without internal names and details, is worth writing for incidents customers noticed. Say what happened, how long it lasted, what caused it and what you are changing.

Downtime is obsolete.

Set up your first monitor in under a minute, or look around the live demo first.

14-day free trial · No credit card required