Status Pages
Status pages let you communicate service health to your customers in real time, with automatic notifications, subscriber management, and full customization.
A status page is a publicly hosted page where your customers and stakeholders can check the current health of your services, view active incidents and maintenance windows, and subscribe to receive notifications.

What's on the page
Every status page shows:
Overall status — a banner at the top that automatically reflects the worst status across all your services: Operational, Degraded, or Unavailable.
Services and containers — your individual components (API, database, CDN, etc.) grouped into containers, each showing its current status:
ok,minor,major, ormaintenance.Uptime graph — a rolling history of each service's availability over a configurable period (e.g. last 30 or 90 days).
Active notices — ongoing incidents, in-progress maintenance windows, and active announcements, each with a full timeline of updates.
Notice history — past incidents and maintenance windows in reverse chronological order.
Notices
Notices are the posts you publish to keep your subscribers informed. Three types cover every situation:
Incident
An unplanned service disruption (minor or major)
Maintenance
A planned or essential maintenance window
Info
A general announcement with no implied service impact
Each notice can have multiple updates posted over time, letting you communicate as the situation evolves.
Subscriptions and notifications
Visitors can subscribe to your status page and receive notifications whenever a notice is created or updated. Three channels are available: email, Slack, and RSS. Subscribers can filter notifications to only the services they care about.
Subscriber-level Slack notifications (where your customers connect their personal Slack account) are separate from the organization-level Slack integration used by Incident Management.
Key features
Custom domains — Assign your own domain (e.g. status.acme.com) with automatic DNS verification and SSL provisioning. Once active, the custom domain becomes the canonical URL.
Access control — Keep your page public, restrict it to logged-in organization members, or limit access to specific IP addresses or CIDR ranges. Modes can be combined.
Customization — Set your brand colors, fonts, logos, and header/footer content to match your product.
Incident automations — Connect incoming webhooks to automatically create notices when your own monitoring or alerting tools fire. Useful for reducing manual work during incidents.
Multiple pages — One organization can run multiple status pages — useful for separating internal and external audiences, or different product lines.
Last updated