Subscribers
Subscribers receive notifications when you open an incident, post an update, or schedule maintenance. They sign up themselves from the public status page.
Channels
| Channel | When to use it | Plan |
|---|---|---|
| Default. Works for everyone, low friction. | All | |
| SMS | Critical services. Higher priority for the recipient. Costs apply. | Pro+ |
| Webhook | Pipe incidents into Slack, Teams, Discord, or any custom HTTP endpoint. | All |
Verification
All channels use double opt-in. After signing up the subscriber receives a verification message. Notifications only go out after the link or code in that message is confirmed.
This is required by GDPR and prevents abuse (someone subscribing a third party without consent).
Component subscriptions (Pro+)
By default subscribers receive notifications for every incident on the page. On Pro and above, subscribers can pick specific components or component groups — they only hear about incidents affecting those.
Useful when a page covers many independent services and not every subscriber cares about all of them.
Per-maintenance notification control
When scheduling a maintenance, you choose which lifecycle events trigger notifications:
- Scheduled — when the maintenance is created
- Reminder — one hour before it starts
- Started — when status flips to In Progress
- Completed — when it ends
You can turn each phase on or off, or disable notifications entirely with a master toggle.
Self-service management
Every subscriber notification email contains a Manage preferences and Unsubscribe link. Subscribers can change channels, switch components, or unsubscribe without contacting you.