# Example Postmortem DD/MM/YYYY

**Date**: DD/MM/YYYY

**Author(s)**: Engineer 1, Engineer 2. These should usually be the people involved in dealing with the incident and aftermath.

**Severity Level/Scope**: Outage level 1-5 as per guidelines

### TL ; DR
Short description everyone in the company can understand about what happened and how is the team solving it on a high level.
### Impacted Services
 - Service X was unresponsive to users in Y region
 - Functionality Y was unavailable to all users
### Technical background
Technical details of the impacted services or resources that failed in order to understand the context in which they failed, if necessary.
### Root cause
A deep analysis that starts on the surface symptoms of the incidence and goes all the way down to a primary cause. This can be usually done using the [5 Whys](https://en.wikipedia.org/wiki/5_Whys). This investigation should strive to be [blameless](https://codeascraft.com/2012/05/22/blameless-postmortems/) and find the faults in the system that allowed the incident to happen, not the human errors involved. Remember processes fail, not people.
### Timeline
All times in CET:
  - **9:00 am** first thing happened
  - **11:00 am** we saw thing X was going on, so we pushed a fix to mitigate this
  - **12:00 am** service returned to normal
### Lessons learnt
- Prevention
  - Item1
  - Item2
- Detection
  - Item1
  - Item2
- Mitigation
  - Item1
  - Item2
### Action points
| Definition | Team | Type | Priority | Reference |
| ---- | ---- | ---- | ---- | ---- |
| Set up firewall on deployment | platform | prevention | High | n/a DONE |
| Add CW alarm on elevated 499 errors | cx | detection | Low | JIRA Link |
| Restore user data from backup | cx | mitigation | Very High | JIRA Link |
### Statistics, logs and metrics
Images that describe the latency, downtime, links to log files, metrics that estimate the damage, whatever the author deems relevant goes here.