Status Pages
Subscriber Notifications
Let your users subscribe to email notifications so they are informed the moment an incident occurs -- without needing to check the status page manually.
How subscribers work
Beacon provides an email-based subscriber system with double opt-in. When a user subscribes to your status page, they receive email notifications for every incident event on that page.
Subscriptions are scoped to a single status page. If your workspace has multiple status pages, users subscribe to each one independently.
Subscribe flow
The subscription process follows three steps:
- Step 1: Sign up — The visitor enters their email address in the subscription form on your public status page and submits it.
- Step 2: Confirmation email — Beacon sends a confirmation email containing a unique link. This prevents abuse and ensures the email address is valid.
- Step 3: Confirm — The visitor clicks the confirmation link. Their subscription is now active and they will receive incident notifications going forward.
What triggers notifications
Subscribers receive an email when:
- A new incident is created — The notification includes the incident title, impact level, current state, and the initial update message (if provided).
- An incident receives an update — The notification includes the new update message and the current incident state.
Subscribers are not notified for changes that only affect component statuses without an associated incident. They are also not notified for edits to an incident title or impact level alone -- only new timeline updates generate notifications.
Unsubscribe flow
Every notification email includes a one-click unsubscribe link in the footer. Clicking it immediately deactivates the subscription -- no confirmation required.
Beacon also sets the List-Unsubscribe header on all notification emails, which allows email clients that support it (Gmail, Apple Mail, Outlook) to show a native unsubscribe button.
Unsubscribed users can re-subscribe at any time by going through the subscribe flow again.
Subscriber limits
The number of subscribers per status page depends on your plan:
| Plan | Subscribers per page |
|---|---|
| Free | 100 |
| Pro | 5,000 |
| Business | 25,000 |
| Enterprise | Unlimited |
Only confirmed (active) subscribers count toward the limit. Pending and unsubscribed records are not counted.
Atom feeds
Every public status page provides an Atom feed for users who prefer RSS readers or need a machine-readable feed of incidents. The feed URL is:
https://usebeacon.pro/status/{workspace-slug}/{page-slug}/feed.atom
The feed includes the most recent incidents and their updates. It is updated in real time as incidents are created or updated.
JSON snapshot endpoint
For programmatic consumers, Beacon also exposes a JSON snapshot of the current page status at:
https://usebeacon.pro/status/{workspace-slug}/{page-slug}/api/status.json
This returns the overall page status, all component statuses, and active incidents. No authentication is required for public pages. This endpoint is useful for building custom integrations, dashboards, or scripts that need to check status programmatically without subscribing to notifications.
// Example response
{
"status": "operational",
"components": [
{ "name": "API", "status": "operational" },
{ "name": "Dashboard", "status": "operational" },
{ "name": "Workers", "status": "operational" }
],
"active_incidents": []
}