Status pages

Your customers find out about outages one way or another. A status page lets you tell them first, on your terms: a hosted page at status.ops-ping.com/<slug> with curated incident updates, 90-day uptime bars, and optional email subscriptions. This guide covers setup, publishing incidents, subscriptions, and sharing.

Before you start
  • Admin access to the console — status page settings live under Settings.
  • At least one incident you want to publish, per Incidents & services.

  1. Enable and configure the page

    In the admin console, go to Settings > Status Page and enable it. Three settings matter:

    • Slug — the page lives at status.ops-ping.com/<slug>. Pick something stable; customers bookmark it and the link shows up in your support macros. Changing it later breaks every bookmark.
    • Visibility — public (anyone with the URL), secret-link (URL carries a key; anyone without the key gets nothing), or login (OpsPing accounts only). Secret-link is the middle ground for pages you share with a named customer list but don't want indexed.
    • Uptime bars — a rolling 90-day bar per service. On by default; turn it off if your SLA math would make the bars look worse than the prose.
    Note

    Pages are hosted on the status.ops-ping.com domain — custom domains aren't supported yet.

  2. Publish an incident

    Status pages don't mirror your alert queue — publishing is a deliberate act. On the incident detail page, the publish panel creates a statusPageEntry: a customer-facing summary, separate from the internal timeline you write for responders.

    As the incident progresses, post public timeline updates — investigating, identified, monitoring, resolved — and each one appears on the page with a timestamp. Customers see the story you choose to tell; the internal timeline, linked alerts, and responder chatter stay internal. Regenerating or editing the entry later keeps your published edits intact.

    Tip

    Publish within the first few minutes of a customer-impacting incident, even if the update is just "we're aware and investigating." A stale page during an outage costs more trust than the outage itself. Resolve publicly when it's fixed — the resolved entry is the receipt.

    Maintenance windows published to the page notify subscribers too, so planned work doesn't read as an outage.

  3. Email subscriptions

    Visitors can subscribe to the page by email. It's double opt-in: they submit an address, get a confirmation email, and only count as subscribed after clicking the link. No purchased lists, no typos paging strangers.

    Every notification email carries a one-click unsubscribe link. Subscribers only get mail tied to the page — incident updates and maintenance notifications, nothing else.

  4. Share and embed

    The public URL is status.ops-ping.com/<slug>. For secret-link pages, the URL includes the page key — share the exact link from Settings, since the keyless URL returns nothing.

    You can also pull the page's data programmatically. The public API needs no authentication for public pages:

    curl https://api.ops-ping.com/v2/public/status-page/payments

    For secret-link pages, pass the page key:

    curl "https://api.ops-ping.com/v2/public/status-page/payments?key=PAGE_KEY"

    The response carries the page summary, service uptime bars, and published entries with their public timeline updates — enough to build your own widget, link it from your app's footer, or feed an internal dashboard.

    Note

    There's no hosted embed widget yet — the public API is the supported way to render status elsewhere.

Next up Stakeholder status →