Subscribers
Subscribers are customers and users who follow one of your status pages. They are automatically notified about service-status changes and published incident updates — you post once, everyone who opted in hears about it.
Manage them under Monitoring → Subscribers; the sibling page Subscriber Notifications is the audit log of everything that was sent.
How people subscribe
Section titled “How people subscribe”Visitors subscribe on the status page itself — you enable the channels per page in its subscriber settings:
| Channel | Contact point | Confirmation |
|---|---|---|
| Email address | 6-digit code / link by email (double opt-in) | |
| SMS | Phone number | 6-digit code by SMS (double opt-in) |
| Slack | Incoming-webhook URL | Verified immediately by a confirmation post to the webhook |
| RSS / Atom | — | Feeds, no stored subscriber |
Unverified subscribers are deleted automatically after 24 hours — the Deletes if not verified column shows the deadline. The subscribe forms are protected against bots by TrustCaptcha (level configurable per page).
Each notification email contains manage and unsubscribe links, so subscribers help themselves; the links are personal tokens and need no account.
Dashboard actions
Section titled “Dashboard actions”- Verify — manually verify a pending subscriber (e.g. a customer who asked for help); they start receiving notifications immediately.
- Edit — adjust the subscriber’s notification preferences (below).
- Delete — remove the subscriber; they receive nothing further.
What subscribers receive
Section titled “What subscribers receive”Each subscriber has individual preferences (defaults in bold):
| Group | Event | Default |
|---|---|---|
| Services | Service impact starts (degraded / partial / major outage) | on |
| Service recovers | on | |
| Service severity changes (e.g. degraded → major outage) | on* | |
| Service enters or leaves maintenance | off | |
| Service is paused or resumed | off | |
| Incidents | Incident created (and published) | on |
| Incident updated | off* | |
| Incident resolved | on | |
| Include scheduled maintenance | off | |
| Include informational incidents | off |
* Self-service subscriptions start with these defaults; you can fine-tune every subscriber from the dashboard.
Only published incidents ever notify — drafts are silent. Unscheduled incidents and security events are always eligible; scheduled-maintenance and informational incidents require the corresponding opt-in.
Subscriber Notifications (audit log)
Section titled “Subscriber Notifications (audit log)”Monitoring → Subscriber Notifications lists every dispatch, newest first:
- Kind — service-state (impact started, recovered, severity changed, maintenance entered/left, paused, resumed) or incident (created, updated, resolved)
- Status page, subject, and the change (old → new status, or the incident message)
- Recipients — how many subscribers were notified, with a failed badge if deliveries bounced
- Dispatched — per-channel counts (email / SMS / Slack)
Notification emails are rendered with the status page’s branding, language, and legal links; the sender name and reply-to address are configurable per page (plan feature).
Limits
Section titled “Limits”- The total number of subscribers across all pages is a plan limit (badge on the subscribers page). Available channels (email/SMS/Slack/RSS/Atom) also depend on the plan.
- SMS notifications are metered against your messaging credits.
- Notification history is kept according to your plan’s data-retention period.
