Components
Component health
Map devices, services, or customer-facing features to status components.
Keep customers informed during a service issue.
Publish customer-facing service status and incident updates. Give customers a place to check progress while your team investigates.
- Show customer-facing health from service endpoints, heartbeats, user-impact monitors, and incidents.
- Publish incident and maintenance context from the ops workflow while keeping internal detail private.
- Use pages, custom domains, markdown guidance, and history as support and trust evidence.
Live status pages
Give customers a reliable answer before they need to open a ticket.
Monitors
Availability state
Drive status from heartbeat, service, and user-impact monitors.
History
Uptime record
Keep historical availability visible for enterprise buyers and support reviews.
Incident communication that follows ops
Give support and customer success a place to send customers while engineering works the problem.
Triage
Decide what customers should see
Start from alerts, monitors, or customer reports, then publish only the safe summary.
Updates
Keep everyone aligned
Post clear progress notes that support, account teams, and customers can all reference.
Resolution
Close the loop
Preserve timestamps, mitigation notes, and recovery evidence for post-incident reviews.
Trust surface
Status pages become proof that your team is operating the product professionally.
Branding
Your domain and brand
Publish under your own customer-facing identity.
Docs
Helpful context
Link documentation, runbooks, or customer guidance beside incidents.
Dashboards
Operational proof
Pair status with dashboards when customers need deeper visibility.