Status-page subscriptions
Email and webhook subscriptions for public incident and maintenance updates.
Status-page subscriptions deliver incident and maintenance updates by email or webhook.
This is distinct from alerting. Alert channels are the operator's own pager; subscriptions are the audience's.
How readers subscribe
On a public page with the subscribe form enabled, readers pick Email or Webhook, optionally select specific components (none selected means all components), and select Subscribe.
Nothing is ever delivered to an unconfirmed destination:
- Email. Submitting the form sends one message containing a confirmation link. Nothing else is sent until it is clicked. Re-submitting the same address re-issues the link rather than creating a second subscription.
- Webhook. The endpoint receives a
subscription.verificationPOST and must answer 2xx. A URL that does not answer never becomes deliverable.
The response is identical whether or not the destination was already subscribed.
Email subscriptions require the instance mail relay. Without one, the public form offers only webhook subscriptions.
Subscription events
Notices are scoped exactly as the page itself is scoped, so a subscriber is never told about something the page does not show:
- an incident belongs to a page when its explicit component impact intersects the page's components, or—with no impact set—when its monitors intersect the page's monitors. An organization-wide declaration with no monitors at all appears on every page.
- a maintenance window belongs to a page when it is general, or when its monitors intersect the page's.
Incidents produce one notice per public update. Internal notes are never included. Maintenance produces up to four notices: when the window is scheduled, one hour before it starts, when it starts, and when it completes.
Every notice carries a preferences link and an unsubscribe link, and mail also carries a one-click unsubscribe header. Unsubscribing removes the subscription immediately, including notices already queued.
Manage subscribers
Status pages → ⋯ → Subscribers… lists every subscriber with its confirmation state and last-notified time. Filter by health: All subscribers, Confirmed and healthy, Awaiting confirmation, or Confirmed with delivery issues. You can remove any subscriber; removals are written to the audit log. You cannot add a subscriber from the console—consent has to come from the destination.
The Delivery history table shows each notice, its status (pending, delivering, retrying, succeeded, failed), attempt count, error, and when it was sent. Resend on a failed notice queues a new delivery.