Updated 2026-06-26
A status page gives your users a place to check on your service — and to find out about incidents — without emailing your support inbox.
Creating a page
Pick a name and a URL slug; your page is reachable immediately at
<slug>.<status-pages-domain>. Then choose which checks to show and how —
each component can optionally display its uptime percentage and response
time alongside its current state.
Incident history
A status page can show its incident history (on by default), going back a configurable number of days (90 by default). Visitors see current incidents with their update timeline as well as recently resolved ones.
Keeping a page private
If a status page shouldn't be fully public, set a password on it — visitors need the password to view it. This is useful for a status page you want to share with a specific client rather than the whole internet.
Subscribers
Turn on "Allow visitors to subscribe to updates" in the page editor to show a "Subscribe to updates" box on the public page (off by default for new and existing pages). Once enabled, visitors can subscribe with their email to be notified when an incident opens, resolves, or a maintenance window is scheduled. Subscriptions are double opt-in (a confirmation email is sent before they start receiving notices), and every notice includes a one-click unsubscribe link.
Branding
By default, status pages show a small "powered by Status" footer. Plans with status page branding removal can turn this off.
How many pages you can create
Your plan sets how many status pages you can run and how many subscribers each one can have. See Choosing a plan for the specifics, and Custom domains for status pages if you want the page on your own domain instead of the default one.