Alerts from a status page

A status page is not only a display: it carries alerts in both directions. Your users can subscribe to be told about incidents and maintenance, and they can report a problem your monitors have not caught yet.

status.acme.com API Website Subscribe Report issue 1 · SUBSCRIPTIONS — YOU → YOUR USERS Visitor enters emailconfirms via link Incident / maintenancepublished or updated email to every subscriber 2 · ISSUE REPORTS — YOUR USERS → YOU Visitor: "checkout is broken for me"email · optional monitor · message Email tothe org owner 🔔 bell in thedashboard top bar you verify, then create an incident (or dismiss)

Subscriptions — you notify your users

1. The visitor clicks Subscribe on your status page and enters an email address.
2. They receive a confirmation link. Nothing is sent until they click it (double opt-in).
3. From then on, they get an email on every new incident and every incident update (identified, monitoring, resolved) published on that page.
4. Every email carries an unsubscribe link. Subscriber addresses are stored by OKStatus for this purpose only and never shared.

Subscriptions are handled entirely by OKStatus — no mailing tool to configure. The subject line is [OKStatus] <incident title> — <status>.

These emails are about the incidents you write. A monitor flipping to Down does not email subscribers by itself, and a scheduled maintenance window is shown on the page but not emailed — post an incident if your users need a heads-up in their inbox.

Issue reports — your users alert you

When Allow visitor issue reports is enabled in the page settings (it is by default), the public page shows a Report an issue button. A visitor fills in their email, optionally the affected service, and a message.

The report reaches you in two places:

• an email to the organisation owner,
• the bell in the dashboard top bar, where reports pile up until you handle them.

Reports are clearly labelled as visitor-submitted. They are a signal, not a confirmed outage: check the monitor, then either create an incident from the report or dismiss it. The endpoint is rate-limited by IP address to keep abuse out.

Badges and the floating widget

The status badge and the floating status widget are one-way: they show live monitor status inside your own site or README and never send anything. Use them when a page in your product should reflect your status without people having to subscribe.