Status pages

Tell customers what is happening while you fix it.

Create public or private status pages with components, incidents, scheduled maintenance, subscribers, uptime history, branding, and custom domains.

Reduce repeated support tickets.: Give users a single source of truth during incidents so your team can focus on fixing the problem instead of replying to the same question in every channel.
Connect status to monitoring.: Link checks and components so status pages reflect the systems your team is already monitoring.
Use the right page for the audience.: Publish a public customer-facing page, keep an internal page private, or create branded pages for different products and clients.
Communicate before and during maintenance.: Scheduled maintenance windows make planned work visible ahead of time, while incident updates keep subscribers informed if something unexpected happens.

Frequently asked questions

The short version. The docs have the details when you need them.

Can I use a custom domain?: Yes. Status pages support custom domains, branding, and private pages.
Can users subscribe to incidents?: Yes. Users can subscribe to updates for your status page.
Can status pages show uptime history?: Yes. Status pages can show component status and uptime history for the services you expose to customers or internal stakeholders.
Can I use third-party components?: Yes. Status pages can include third-party components, so dependencies can appear alongside systems you monitor directly.

Create the page customers will check before they open a support ticket, then connect it to the monitoring you already trust.