Skip to main content
A status update is the public write-up of an incident: what is going on and where you are in the response. It is separate from the Tallwatch opens when monitors go down. Group status and uptime bars on the already follow those monitors. The timeline, RSS feed, and subscriber email do not. Those change only when you publish.

​
How it works

Live from monitors. Group status and uptime bars update as the attached monitors change. Visitors can see a group in its worst state without a written update. Only when you publish. Previous incidents, RSS, and email update when you post from the incident’s Customer comms panel. Detected incidents are never auto-published.

​
What to publish

From the incident in the app:
  1. Notify customers — first public post (title and message are prefilled; edit if you want).
  2. Post update — append a message to the same thread.
  3. Mark resolved — close the public incident and email subscribers.
Each update uses a public status (investigating, identified, monitoring, or resolved) and a short message. Severity applies on the first post only. Open More options if you need to change the title, severity, or status before sending. Pair planned work with a so the public page shows the window as well as any copy you post.

​
Email and RSS

Visitors subscribe with email (double opt-in, one-click unsubscribe). Email goes out when you publish, not when a monitor changes state. RSS for a public page:
Password-protected pages return 404 on RSS.