Status pages & incident communication — found from sitemap — openstatus

Cited by

Facts read from this source

• Subscriber definition Report an error

  “A subscriber in openstatus is an entity (typically a user or an integration) that opts to receive real-time notifications and updates regarding incidents and status changes on a specific status page.”

• Subscriber notification types Report an error

  “Subscribers only receive status report updates and scheduled maintenance.”

• Public self subscription email only Report an error

  “Entering an email address — the public form is email-only.”

• Subscriber opt in confirmation Report an error

  “Opt-in confirmation — a verification email is sent, and the subscription only activates once the recipient confirms it.”

• Subscriber component scoping Report an error

  “Scope selection (optional) — where enabled, choosing which page components to be notified about instead of the whole page.”

• Subscriber dashboard addition Report an error

  “Beyond public self-subscription, administrators can add subscribers directly from the dashboard.”

• Dashboard email no confirmation Report an error

  “By adding an email here you confirm the contact has consented to receive status updates; no confirmation email is sent.”

• Subscriber no broadcast Report an error

  “There is no ad-hoc broadcast: subscribers are only reached through status report updates and maintenance notifications.”

• Slack subscriber self subscribe Report an error

  “Any channel in a Slack workspace that has the openstatus app installed can subscribe itself by running the slash command in that channel”

• Slack subscribe no confirmation Report an error

  “The subscription is created immediately without a confirmation step, the bot joins the channel if it can, and the channel receives updates for the whole page.”

• Slack protected pages rejected Report an error

  “Protected pages (password, email domain, or IP restriction) are rejected with "Protected status pages can't be subscribed to from Slack".”

• Slack commands Report an error

  “/openstatus subscriptions — list the pages this channel is subscribed to. /openstatus unsubscribe [status-page-url] — stop updates. The URL is optional when the channel follows exactly one page.”

• Feeds Report an error

  “Every status page exposes read-only feeds that need no subscription at all. Feed readers and scripts poll them directly:”

• Feeds password query param Report an error

  “On a password-protected page, append ?pw=your-secret-password to read them.”

• Webhook channel native payloads Report an error

  “Webhook — POSTs each update to a URL. Slack, Discord, and Microsoft Teams URLs receive channel-native messages; any other URL receives a generic JSON payload.”

• Webhook custom headers Report an error

  “You can attach custom request headers to every webhook request — for example, a shared secret or an authorization token your receiver verifies.”

• Webhook timeout Report an error

  “Each webhook request is given 5 seconds to complete. If your endpoint has not responded within that window, the request is aborted and treated as a failed attempt.”

• Webhook retries Report an error

  “Failed attempts are retried with jittered exponential backoff (≈200 ms base delay), up to 3 retries (4 attempts total).”

• Webhook retry conditions Report an error

  “Only transient failures are retried: Network errors and timeouts (no HTTP response). 5xx responses — a server-side error on your end that may clear. 429 Too Many Requests — your endpoint asked us to back off.”

• Webhook send test Report an error

  “The Send test action emits the same envelope with type: "test" and a data.test object”

• Webhook generic payload versioned Report an error

  “The version field is bumped on any breaking change, so pin to it when consuming the payload.”

• Social notifier example Report an error

  “statuspage-socials-notifier is a reference receiver that consumes the generic payload and cross-posts each update to your X (Twitter) and Bluesky accounts.”

• Slack connect scoped subscriptions Report an error

  “This is the path for Slack Connect channels shared with customers, where the owner decides which components each customer sees.”

Scores citing this record

• The Agency Developer Status pages & incident communication
• The Customer Support Lead Status pages & incident communication
• The E-Commerce Operations Manager Status pages & incident communication
• The SaaS Platform Engineer Status pages & incident communication
• The Information Security Officer Status pages & incident communication
• The Skeptic Status pages & incident communication