Status pages

Why you need it

Every minute of an outage costs you twice: once in lost revenue, once in the support tickets that pile up while your team is heads-down fighting the fire. A status page breaks the second cost by giving customers somewhere to look that isn't your inbox.

• Live in five minutes, not a sprint. Pick a slug, drag your probes into order, you're at status.statuspulse.ai/<you> — no DNS, no certificates, no engineering ticket.
• Looks like your product (Pro+). Your logo, your accent colour, your font — paired with a custom domain like status.acme.com the page passes for a first-party surface.
• Speaks your customers' language. English, Portuguese, Spanish, French, Italian, German. Visitors pick from the footer; the choice sticks.
• One workspace, many pages. Run a separate page per product line, customer tier, or geography — each with its own probes, watchers, and brand.
• The receipts. Public uptime history, incident timeline, SLA badge per probe. Prospects evaluating you can verify your last-90-days story themselves.

Where it pays off

The four jobs a status page does at once:

• Deflect support tickets. "Is it just me?" traffic lands on the page, sees the red banner, waits instead of opening a ticket. One link in your help-centre footer saves real money.
• Set expectations during an incident. The timeline gives your customers something to refresh that isn't your inbox. A regularly-updated page is the single highest-leverage thing you can do during a sev-1.
• Prove uptime to prospects and auditors. The public history is your SLA receipt; pair it with PDF reports for the paper trail.
• Coordinate with partners. Run a separate page on a private hostname for partner-only visibility, with its own watchers and routing.

Not the right tool when: you only need internal alerting and have no external audience — point your probes at a private Slack channel and skip the public page entirely.

Related

• Custom domain
• Custom branding
• Multi-language pages & reports
• Incidents & alerts
• Probes