Skip to content

Status pages

Status pages that only say what you decided to say

Pick the monitors to publish as components, name them for customers, and keep targets, credentials and internal notes private.

status.acme.exampleDemo page, isolated from production data
◆ Degraded performance on one component
  • WebsiteOperational
  • Customer portalOperational
  • Email deliveryDegraded performance

Grey days mean no data, not uptime. Availability is time-weighted over evaluable time.

  • Components and groups

    Map components to monitors or manage them manually. Group them the way customers think about your service.

  • History that distinguishes no data

    Daily bars show availability from rollups; days without evaluable time are grey, never green.

  • Announcements

    Notices, incident updates and planned maintenance with a safe text subset. No scripts or embeds can be injected.

  • Access control

    Public, or password protected. Private pages are never indexable; public pages are indexable only when you opt in.

  • Custom domains

    Verified with a DNS TXT record and a CNAME before they serve. Unknown hosts are refused; removed domains stop serving immediately.

  • Stale data is visible

    Pages serve a stored projection. If the control plane cannot refresh it, visitors see the last known state with its timestamp.

Status delivery is prepared for a separate failure domain. Until it is independently deployed we do not claim independent status availability.