Subscribers
Subscribers are people who receive email notifications when incidents are created or updated on your status page. You can add subscribers from the Middleware console and allow public visitors to subscribe from the live status page.
Enable subscriptions#
On the Settings tab of your status page, configure the notification toggles under Notifications:
| Setting | Description |
|---|---|
| Subscribe to status page | Master toggle. When enabled, a Subscribe button appears on the public page |
| Allows email-based subscriptions (requires the master toggle) | |
| Slack | Coming soon — not yet available in the public UI |
| Auto refresh | Polls for updates on the public page (separate from notifications) |
Both Subscribe to status page and Email must be enabled for visitors to subscribe via email.
Add subscribers from the console#
1 Open the Subscribers tab#
Go to Synthetics → Status Page, open your page, and select the Subscribers tab.
2 Add a subscriber#
Click Add Subscriber and enter an email address. Middleware validates the email format before saving.
The subscriber is associated with this status page and receives notifications for all incidents on it.
3 Manage existing subscribers#
The subscribers table shows all recipients with their email address and subscription type. You can:
- Search — filter subscribers by email address
- Edit — update a subscriber's email address
- Delete — remove a subscriber from the notification list
Public email subscription#
When subscriptions are enabled, visitors to your public status page see a Subscribe button. Clicking it opens a dialog where they can enter their email address to receive incident notifications.
Middleware validates email addresses on the public form using standard format rules. Successful subscriptions are added to the same subscriber list visible in the console.
What subscribers receive#
Email notifications are sent when you create or update an incident. Each email includes:
- Incident title — the summary you entered
- Affected services — names of services impacted by the incident
- Status — current workflow status (Investigating, Identified, Update, Monitoring, or Resolved)
- Message — your update text or the default message
- Link — URL to your public status page
Notifications are sent on every incident save, including follow-up updates as you progress through the incident lifecycle.
Subscription types#
| Type | How it is added | Status |
|---|---|---|
| Console or public Subscribe button | Available | |
| Slack | OAuth flow for public visitors; admin-managed in console | Coming soon |
| SMS | Toggle exists in settings | Limited availability |
Best practices#
- Add internal stakeholders first — include engineering leads, support teams, and account managers before going live
- Test with a non-production incident — create a test incident with Not Affected impact to verify emails arrive
- Keep the subscriber list current — remove addresses when team members leave
- Enable public subscribe for customer transparency — letting customers self-subscribe reduces manual list management
Next steps#
- Managing Incidents — create incidents that trigger notifications
- Getting Started — enable subscription toggles during setup
Need assistance or want to learn more about Middleware? Contact our support team at [email protected] or join our Slack channel.