Status pages
Pages and components, maintenance windows, and the public status page URL.
Status pages
A status page groups components, each optionally bound to a monitor, behind one public URL. When a bound monitor's status changes, the component it is bound to follows automatically.
No Status pages screen in the console yet
Status is one of the console's eight planned sections, and it has not been built. There is no page editor and no rendered public page. The public URL is a JSON endpoint today, not an HTML page. This section documents the real API surface, not the planned console screens.
Status pages are owned by a user, not an organization
Every other resource in these docs is scoped to your organization. Status
pages are still scoped to the user who created them (GET /status-pages
returns pages you personally own), which is a known gap on the roadmap to
close, not a design choice to route around. A status page created by one
teammate is invisible to another through this API today.