Status pages
Advanced status-page workflow
Structure clear customer communication around live monitor data, incidents, and planned work. It is written for the people who manage the page and the customers who read it, so you can confidently explain service health without exposing internal technical details.
Design the structure
- Select a monitor that reflects the service customers depend on.
- Use Current Status Only for a concise health signal.
- Use Status History when customers need recent availability context.
- Use Status History & Chart when response-time trends also matter.
- Prefer customer-facing URLs and names over internal system labels.
Plan incident communication
Monitor state is the technical signal; public status reports explain customer impact. A report can be Created, Degraded, or Resolved. Turn on automatic status-page updates in Structure when new monitor incidents should publish an initial public update automatically.
Separate planned maintenance
Create maintenance entries for scheduled work with an accurate time window.
Write for customers
Describe impact and the next update time, not internal debugging detail.