Collect subscribers from the public status page where the workspace allows it.
Menu
Product
Resources
Tools
PricingLog inFeature · Status communication
Subscriber notifications for incidents and maintenance
Let customers follow service updates by email or configured channels so support teams can reduce repeat tickets during incidents.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Send incident, maintenance, and recovery notices only for affected components.
Respect verification, unsubscribe, and workspace access rules.
Watch the signal
Track the public evidence customers actually experience.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
Customer-controlled updates
Subscribers choose to receive updates for the services they care about instead of relying on ad hoc ticket replies.
Verified delivery path
Email subscription flows should verify ownership, handle unsubscribes, and avoid exposing subscriber lists publicly.
Incident fit
Subscriber notifications work best when public components, severity, and incident states are already mapped to customer impact.
Safe for public status pages
- Website and application availability
- API health endpoint status
- DNS and SSL issues affecting customer access
- Maintenance windows and incident timelines
- High-level region coverage
Internal operations only
- SSH, admin panels, databases, queues, and backups
- Server names, origin IPs, provider IDs, and ports
- Firewall rules, file paths, and secret-related config
- Primary or backup probe node details
- Customer-specific private control panels
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.