Subscribers
Subscribers receive notifications for incidents and maintenances based on status page and component preferences. A subscriber strategy is how you keep customers informed without overwhelming them: the right people get the right updates at the right time.
How subscriber workflows work
Subscriber management usually starts with deciding scope. Some subscribers want every update on a status page, while others only care about specific components. As incidents and maintenances are published, notification delivery respects that scope and any channel-level preferences.
Subscriber operations are closely tied to Status pages, Incidents, and Maintenances. If publication conditions are not met in those workflows, subscriber notifications for the expected event will not be sent.
Day-to-day subscriber operations
In day-to-day operations, your team adds subscribers, adjusts scope as services evolve, and keeps subscription data clean by removing stale entries or processing unsubscribe requests promptly. When service structure changes, review subscriber scope so customers do not silently lose updates for renamed or regrouped components.
What changes on the public frontend
Subscriber actions do not directly change rendered status page content. They change who receives communication when public updates are published. In practical terms, subscribers affect communication reach, not page layout.
Operational effects
Subscriber configuration strongly influences notification volume. Broad scopes can produce noisy communication during active incidents, while narrow scopes can leave customers unaware of relevant events. Changes to components and status page mappings may also change who is included in future deliveries, so teams should review subscriber coverage after major taxonomy updates.
Email deliverability for subscribers depends on sender configuration in Email sender addresses, and external automation depends on Webhook subscriptions. Keeping these two channels healthy prevents communication blind spots.
Troubleshooting
Subscribers report missing updates. Verify that the incident or maintenance was published to the expected status page and that the subscriber scope includes the affected components.
Too many subscribers are receiving low-impact updates. Review notification practices in incident and maintenance workflows and tighten subscription scope where possible.
Email updates are delayed or absent. Check sender address status and delivery readiness in Email sender addresses, then confirm the event was published with notification enabled.