Status pages, incidents, and subscribers

When to use a status page#

Use a status page when customers or stakeholders need a simple, customer-safe view of service health and incident communication without access to the Watchfox app.

Create your first status page#

1. Open Status Pages.
2. Click New Page.
3. Enter a public title and slug.
4. Choose public or private access according to the intended audience.
5. Save the page and open its detail.

Add components#

• Add monitor-backed components with public-safe names such as Website, API, Checkout, or Client portal.
• Use tags and component mapping intentionally when several monitors belong to one public service.
• Do not expose internal IDs, private URLs, secrets, raw provider errors, or quota details.

Incidents and updates#

Automatic monitoring incidents provide the operational state. Manual status-page incident updates provide customer-facing context. Write what users need to know: impact, current action, workaround when available, and the next expected update.

Maintenance windows#

Use maintenance communication for planned work and configure the corresponding maintenance mute in Watchfox so expected downtime does not create avoidable alert noise.

Subscribers#

Status-page email subscriptions use double opt-in. Confirmation and unsubscribe links lead to the relevant public status-page surface, not to an authenticated workspace that the subscriber may not access.

Subscriber email addresses, confirmation tokens, unsubscribe tokens, and delivery quota internals must never appear in public HTML or JSON.

Custom domains#

Eligible plans may attach a custom hostname. Enter only the hostname, without https:// or a path, then complete the required DNS validation. Test custom domains only on hostnames you control.

Before sharing#

• Open the page anonymously.
• Verify component names and state.
• Test private-token behavior when private access is used.
• Confirm subscriber confirmation and unsubscribe behavior when enabled.
• Confirm no internal data is exposed.