Introduction
Concepts behind status pages—their audiences, value, and core components.
Status Pages are the public (or private) communication surface for your service availability. They aggregate monitor state, historical uptime, incident timelines, and maintenance schedules into a single branded site.
Core Capabilities
| Feature | Purpose |
|---|---|
| Public / Private Modes | Control audience (customers vs internal teams). |
| Live Status Blocks | Show real‑time component health via monitor requirements. |
| Historical Uptime | Visualize reliability over selectable windows (day/week/month/90d). |
| Incident & Maintenance Panels | Contextual timeline of disruptions and planned work. |
| Custom Branding (plan‑based) | Logo, colors, custom CSS, domain mapping. |
When to Create Multiple Pages
- Different customer segments (e.g., Enterprise vs Public APIs)
- Separate internal SRE dashboard (private) vs external marketing transparency (public)
- Regional product splits where not all customers are affected by local issues
Best Practices
- Keep component naming user-friendly (“Payments API”) vs internal hostnames.
- Limit initial page to critical services; expand gradually.
- Communicate incidents promptly then update status page as RCA refines.
