Status Pages

Pages & Components

A status page is the public face of your service health. This guide covers creating pages, configuring custom domains, managing components, and understanding how overall status is computed.

Creating a status page

From the dashboard sidebar, click Status Pages and then Create Page. Every page requires:

Field	Description
`name`	Human-readable label shown in the header of the public page.
`slug`	URL-safe identifier. Auto-generated from the name but can be customized. Must be unique within the workspace.
`timezone`	IANA timezone (e.g. `America/New_York`) used to display timestamps on the public page.
`is_public`	When enabled, anyone with the URL can view the page. When disabled, only workspace members can access it.

Public vs. private pages

A public page is accessible to anyone on the internet. This is the most common configuration for customer-facing status pages.

A private page requires authentication. Only members of the workspace can view it. This is useful for internal dashboards where you want to communicate service health to your engineering team without exposing it publicly.

You can toggle a page between public and private at any time from the page settings.

Custom domains

Instead of using the default Beacon URL, you can serve your status page on your own domain (e.g. status.acme.com).

CNAME setup

Add a CNAME record in your DNS provider pointing your subdomain to Beacon:

# DNS record
status.acme.com    CNAME    status.beaconstatus.com

Verification

After adding the CNAME, enter your custom domain in the page settings and click Verify. Beacon will check for the CNAME record and, once confirmed, provision a TLS certificate automatically. Verification typically completes within a few minutes.

Tip: DNS propagation can take up to 48 hours in some cases. If verification fails, wait and try again.

Timezone configuration

The timezone you set on a status page determines how all incident timestamps are displayed to visitors. Internally, Beacon stores all times in UTC. The conversion happens at render time on the public page.

Choose the timezone that matches the majority of your users. If you serve a global audience, UTC is a common choice.

Component management

Components appear as rows on the public status page, each with a colored status indicator. You can add, edit, reorder, and delete components from the Components tab in the page settings.

Status values

Each component can be set to one of these statuses:

operational — Green. Service is healthy.
degraded — Yellow. Reduced performance but functional.
partial_outage — Orange. Partial loss of functionality.
major_outage — Red. Complete service unavailability.
maintenance — Blue. Undergoing scheduled maintenance.
unknown — Gray. Status not yet determined.

Reordering components

Drag and drop components in the dashboard to change their display order on the public page. The order is saved automatically. Most teams put their most critical, user-facing services at the top.

Overall status rollup

The banner at the top of the public page shows an overall status. This is computed automatically from the worst-case component status using the following priority (highest to lowest):

major_outage  >  partial_outage  >  degraded  >  maintenance  >  operational

If all components are operational, the banner reads "All systems operational." If any single component is in major_outage, the overall status reflects that, regardless of the other components.

The rollup considers only non-maintenance statuses unless all components are under maintenance. Components with unknown status are excluded from the rollup.

Public URL format

Every public status page is accessible at:

https://usebeacon.pro/status/{workspace-slug}/{page-slug}

For example, if your workspace slug is acme and your page slug is cloud, the URL would be:

https://usebeacon.pro/status/acme/cloud

If you configure a custom domain, the page is also accessible at that domain directly (e.g. https://status.acme.com).