Incidents and status pages
Respond to problems and keep your users informed.
1Respond
Monitoring → Incidents. Acknowledge, assign, and add notes; the timeline records it all.
2Escalate
Set escalation steps on an alert rule, so someone else is told if nobody responds. To page whoever’s turn it is, see On-call schedules.
3Post-mortems
On a resolved incident, choose Write a post-mortem. It starts as a draft built from the incident: how long it lasted, what the check or rule saw, who responded, your notes, and any deploys in the two hours before it opened as leads. Edit each section, save, and publish it to a status page if you like.
4Publish a status page
Monitoring → Status pages → New status page. Choose the monitors to show, post updates, and let people subscribe by email.
5Groups and reports
Give components a group (such as API or Website) to show them under a heading with the group’s worst status. Every month has a public uptime report (linked as Monthly uptime at the foot of the page) with each component’s uptime, the incidents and total downtime; tick Monthly uptime report to send it to subscribers on the 1st.
6Your own domain
Under Custom domain, enter a domain such as status.example.com, add the two DNS records shown (one proves it’s yours, one sends its visitors here) and check them. HTTPS is set up for you.