Notifications: Subscribers vs Internal Alerts

There are two different “notification” concepts in StatusPage.me:

• Status page subscriber notifications (public-facing) — your visitors subscribe and get updates when you post incidents or maintenance.
• Internal alerts (team-facing) — you and your team get alerted when something needs attention.

This page explains how they fit together and points you to the right settings screens.

If you’re trying to notify users who visit your status page, you want subscriber notifications: Managing Status Page Subscribers.

Status Page Subscriber Notifications (Public)

Subscriber notifications are sent when you publish updates your users should know about:

• A new incident is created
• An incident is updated or resolved
• Scheduled maintenance is announced, started, or completed

To enable the public Subscribe button:

1. Go to your status page settings
2. Open the Subscribers tab
3. Enable Allow visitors to subscribe via email
4. Save

Subscribers can stay on All components or narrow incident-driven emails to selected service entries from the public subscribe modal.

Learn more:

• Managing Status Page Subscribers
• Per-Component Subscriber Notifications

Internal Alert Channels (Team)

Internal alerts are delivered to notification channels (email/webhook/Slack/Discord/Telegram/Microsoft Teams/Pushover and more).

Configure channels here: Notification Channels Overview.

If you want your own signed-in dashboard to also show browser notifications, in-app notification history, or a looping critical incident alarm sound, configure those separately in Personal Notification Preferences.

If you want monitor-created incidents to be assigned to a rotating responder, set up an on-call schedule: On-Call Scheduling.

For page-attached monitors, alert routing is managed at the status page level — all channels linked to that page fire when the monitor goes down. The monitor create/edit screen does not offer per-monitor channel selection for these monitors.

For private (standalone) monitors — monitors not attached to any status page — you select alert channels per monitor. Open the Notification Channels card on the Edit Monitor page and click Configure to choose which of your channels should receive alerts for that specific monitor. See Private (Standalone) Monitors.

⚠️ Important: these personal browser/alarm preferences are an extra responder convenience layer. They do not replace your shared notification channels.

If you need to grant teammates access to manage alerts and status pages, see Teams.

Publishing Updates (What Triggers Subscriber Emails)

Subscribers only receive notifications for updates you publish:

• Creating and managing incidents
• Scheduling maintenance windows

Advanced Alert Types

Beyond basic up/down alerts, StatusPage.me supports several advanced alerting modes:

Timeout Rate Alert

If a monitor consistently times out (e.g., 80%+ of recent checks time out) without fully crossing the quorum-down threshold, a timeout rate alert fires. Set a threshold percentage on the monitor edit screen.

This catches scenarios where an endpoint sometimes responds but is heavily degraded under load.

Error Rate Alert (Degraded Mode)

Similar to timeout rate, but covers all failing checks — not just timeouts. Useful for multi-region setups where one region fails intermittently, keeping overall quorum as “up” while a meaningful fraction of users experience errors.

Partial-Failure Escalation

For multi-region monitors: if some regions have been failing for more than a configured threshold (default: 15 minutes) without reaching full quorum-down, you receive a partial-failure escalation alert summarising which regions are affected.

Cross-Monitor Correlation

When 5 or more monitors on the same status page go down within 30 seconds of each other, a possible provider outage consolidated alert fires — so you get one actionable notification instead of 5+ individual ones.

Causal Chain / Root-Cause Hints

When a monitor goes down, StatusPage.me checks whether a related SSL or tool-monitor alert fired in the last 10 minutes for the same domain. If so, the down notification includes a possible root cause hint (e.g., “SSL certificate expiring soon”) to speed up diagnosis.

Rich Notification Context (all plans)

Every down notification includes:

• Last success timestamp — when the monitor last reported up
• Failing / healthy regions — breakdown by check region
• HTTP status code (when available)
• Possible root cause (when a tool-monitor alert is correlated)

Related Guides

• Set up your first monitor
• Create your first status page
• Analytics dashboard
• Notification Channels Overview
• Notification Hub
• Personal Notification Preferences
• Error Budget & SLA Burn-Rate Alerts
• Timeout Rate Alerting

What’s Next?

• Manage status page subscribers
• Target subscriber delivery by component
• Set up internal notification channels
• Understand uptime and SLA reports
• Choose monitoring locations
• Down Prediction Alerts — get warned before a monitor goes down