Assemble a post-incident recap

Build the recap with the current workflow

1. Open the resolved incident and record its start time, recovery time, total duration, affected monitor, and confirming regions.
2. Add the customer-facing context in your normal incident document or stakeholder channel: impact, mitigation, resolution, and follow-up actions.
3. Select Share on the incident detail page and include the read-only timeline link with the recap.
4. Verify that the audience can open the link before sending the final update. Remember that the link expires after its validity period.

Include these facts

• What monitor was affected and when the incident started.
• How many regions confirmed the failure and which probe locations they represent. The incident uses the labels US East, US West, Europe, and Asia for Ashburn, Virginia; San Jose; Stockholm; and Tokyo.
• Whether a responder acknowledged the incident and when recovery was confirmed.
• How long the incident lasted and what customers experienced.
• What you changed or will follow up on after recovery.

Current capability

The Reports workspace describes post-incident customer recaps as a reporting direction, but that page does not currently produce the recap for you. Keep the timeline and public link as evidence, and write the narrative in the format your stakeholders already use.

Related

• Incident lifecycle and statuses
• Share an incident with stakeholders