An incident opens when an outage is confirmed. A failed check is repeated before anything happens, so a single blip never wakes anyone. The incident closes by itself when the monitor recovers.
What we saw
Open the incident from Incidents in the sidebar. What we saw keeps the evidence from when it started:
- The failing check, with the address it connected to, the headers and the start of the response.
- Network path: when the server didn’t answer, a traceroute shows where the path breaks.
- Screenshot: when the server did answer, a real browser photographs what visitors saw. Screenshots are kept for 90 days.
Timeline and notes
- Timeline shows every check, alert and note, so you see who was alerted and when.
- Choose Acknowledge to tell the team you are on it. See escalation and acknowledging.
- Add notes as you work. Only your team sees them.
Write an incident review
- Open the incident and find Incident review.
- Write what happened, why, and what you are changing. Start from a template gives you a structure.
- To show it under the incident on your status pages, turn on Show on status pages and choose Publish. Otherwise choose Save to keep it for the team.
Customers trust a page that explains outages more than one that never has any. Incidents also shows MTTA and MTTR for the last 30 days. More on incident management.