Subscribers & updates

Visitors can subscribe to your status page by email, Slack or webhook and hear about outages without checking the page. You keep the page itself current by posting public updates on incidents and scheduling maintenance windows. This page covers both.

How email subscriptions work#

Every published status page has a Get notified about incidents form at the bottom. Subscriptions use double opt-in: nobody is subscribed until they confirm from their own inbox.

Subscribers get two emails per incident on a monitor that's on the page:

Every email has an Unsubscribe link. Emails link to your custom domain if the page has a verified one.

How visitors subscribe#

1. The visitor enters their Email address on your status page and clicks Subscribe.
2. The page shows "Almost done — check your inbox and click the confirmation link."
3. They receive an email titled "Confirm your status page subscription" and click Confirm subscription.
4. On the confirmation page they click Confirm subscription again. They see "You're subscribed to Page title. We'll email you when an incident starts and when it's resolved."

The confirmation link expires after 7 days. If someone asks again within 10 minutes, no second email is sent, so check spam folders before trying again. Asking again with an address that's already confirmed changes nothing, and the page gives the same answer either way, so the form can't be used to find out who is subscribed.

How subscribers unsubscribe#

1. The subscriber clicks Unsubscribe in any incident email.
2. On the page that opens, they click Unsubscribe.

They see "You've been unsubscribed from Page title. You won't receive further emails." They can subscribe again later from the status page.

When emails are sent#

Subscriber emails follow your incidents, with a few safeguards:

• Only confirmed incidents. Emails go out when SutramX opens an incident for a monitor on the page, not on single failed checks. See Incidents.
• Not for suppressed incidents. If alerts for an incident are suppressed (for example by a maintenance window or quiet hours), subscribers aren't emailed. If the suppression ends while the monitor is still down, they are emailed then, together with your team's down alert.
• Resolved only after started. Subscribers get the "has recovered" email only if they got the "experiencing an outage" email for that incident.
• One email per event. Each subscriber gets at most one "started" and one "resolved" email per incident, even if a flapping incident reopens.
• Flapping protection. Each page sends at most 12 "started" notifications per hour. Further incidents in that hour still appear on the page, but aren't emailed.
• Published pages only. Unpublished pages, and pages unpublished because they're over your plan's limit, don't send emails.

Large lists are sent in batches, so the last subscribers on a big list may get the email a few minutes after the first.

Slack and webhook subscriptions#

On Starter, Growth and Pro, the subscribe form also offers Slack and Webhook next to Email. They get the same two updates per incident as email subscribers.

• Slack: the visitor pastes a Slack incoming webhook URL (https://hooks.slack.com/services/…). SutramX posts a test message to the channel and only subscribes it if that works.
• Webhook: the visitor enters an https:// endpoint. SutramX sends a test request and, if the endpoint answers with a 2xx status, shows a signing secret once. Each request is signed JSON with an X-SutramX-Signature header, the same scheme as webhook alerts. See Webhooks.

Every Slack message and webhook request includes an unsubscribe link. A Slack or webhook subscription is turned off after 10 failed deliveries in a row, or straight away if the endpoint says it no longer exists.

See your subscribers#

The Subscribers section of the page editor lists subscribers by channel, on Email, Slack and Webhook tabs, with each one's status (active, awaiting confirmation, or turned off after failed deliveries) and its last delivery. The Share & embed section shows how many email subscribers have confirmed, and how many are awaiting confirmation.

Any member can see the list. Only the workspace owner can remove a subscriber: a removed email address can subscribe again from the page, but a removed Slack channel or webhook can't. You can't import or add subscribers yourself; visitors subscribe from the page. Each page accepts up to 10,000 email subscribers. Deleting a status page removes all of its subscribers.

Visitors who prefer not to subscribe can follow the page's Atom/RSS feed instead (public pages only). See Status pages overview.

Post incident updates#

While an incident is open, tell visitors what's happening by posting public updates. They appear on every status page that shows the monitor, under the incident, oldest first, and in the page's feed.

To post an update yourself:

1. Open the incident from Incidents in the sidebar.
2. Under Notes, write the update in Add a note.
3. Tick Public (show on status page).
4. Click Add note.

The update appears on the page without your name. To take it down, delete the note; it disappears from the page.

To have AI draft the update for you, use Status page updates on the incident page, then review and click Publish. See AI incident assist.

A few tips for good updates:

• Say which service is affected and what customers may notice.
• Post when something changes: when you know the cause, when a fix is rolling out, when you're watching the recovery.
• Leave out internal details such as hostnames, error codes and names of people.
• Don't promise a fix time you can't keep.

If your page offers extra languages, you can add a translation of each update. See AI incident assist.

Announce scheduled maintenance#

You don't post maintenance to a status page directly. Create a maintenance window under Incidents → Maintenance, and it appears on every status page that shows an affected monitor:

• Windows starting within the next 30 days are listed under Scheduled maintenance with their title, description, times and affected components.
• While a window is in progress, it is shown as In progress and the affected components show Maintenance instead of an outage.
• Maintenance windows are included in the page's Atom/RSS feed.

Write the window's title and description for your customers, since they are shown publicly. Subscribers are not emailed about maintenance. Alerts for incidents during the window are suppressed, so subscribers aren't emailed about those incidents either, unless the monitor is still down when the window ends. See Maintenance windows.

Troubleshooting#