better-stack-status-pages

# Better Stack Status Pages ## Overview Status pages in Better Stack provide a public-facing view of your service health. They automatically reflect monitor statuses and allow manual incident and maintenance updates. MSPs use status pages to communicate service availability to clients without exposing internal monitoring details. ## Anti-triggers - **"Is this service up right now?"** — a status page is outbound communication, not the source of truth for health. Use `betterstack-monitors` for the check and `betterstack-incidents` for the event. - **Better Stack's own availability** — that is status.betterstack.com, not a page you manage; for connection failures use `betterstack-api-patterns`. ## Key Concepts ### Status Page Components Status pages are composed of resources (components) that map to monitors: - Each resource shows a status indicator (operational, degraded, downtime, maintenance) - Resources are automatically updated based on linked monitor status - Resources can be grouped into sections for organization ### Component Statuses - **Operational** - Service is fully functional - **Degraded Performance** - Service is working but with reduced performance - **Partial Outage** - Some aspects of the service are unavailable - **Major Outage** - Service is completely unavailable - **Maintenance** - Service is under planned maintenance ### Maintenance Windows Maintenance windows allow you to: - Schedule downtime in advance - Notify subscribers before ma...