Keep customers informed during an outage.
Show which services are affected, share progress updates as you learn more, and let customers know when everything is back to normal.
- Resolved14:19 UTCCheckout has been operating normally since 14:14. Total impact: 17 minutes.
- Monitoring14:18 UTCRollback complete. Latency is back under target; watching for five minutes.
- Identified14:12 UTCA release at 13:58 exhausted the database pool. Rolling back now.
- Investigating14:05 UTCCheckout latency is above target for some customers. Responders are on it.
Publish updates during an incident
Customer updates come out of the incident your team is already working in, so the page keeps pace with the response. Here is one incident, from the first update to the resolved note.
What you can put on the page
Your domain, your branding, the services your customers recognise, and a record of what happened.
Serve the page at status.yourcompany.com after verifying the domain with a DNS record.
domainYour logo, favicon and accent colour, in a light or dark page.
brandingGroup components the way customers think about them — API, website, checkout — rather than by service name.
componentsLink a component to an uptime monitor so its status follows what the checks report.
monitorsCustomers subscribe from the page and confirm by email; each update goes out to the confirmed list.
subscribersAnnounce scheduled work ahead of time, with its start and end shown on the page.
maintenancePublish the page, or keep it readable only inside your organisation while you set it up.
visibilityPast incidents and per-component uptime stay on the page for the history window you choose.
historyWrite the update once.
An incident in Moneat can own a status-page incident. Post an update there and it reaches the page, so the customer-facing record does not depend on someone remembering to copy it across.
- Create or attach. Open a new status-page incident from the incident, or link one that already exists.
- Update from one place. Progress notes go to the linked page, and resolving the incident resolves it there.
- Choose what customers see. Customer-facing wording and affected components are set separately from the internal timeline.
- Several pages at once. One incident can update more than one status page in a single command.
Put up a status page.
Connect your uptime monitors, group them into the services your customers recognise, add your domain and branding, and publish.