How do I post an incident update on my status page?

Status page updates let you communicate with your users during an incident (or planned maintenance) without waiting for your monitoring to do the talking.

Posting an update

1. Open your status page.
2. Click Create update.
3. Pick a severity for the update: Info, Warning, High, Resolved, or Scheduled. Each one gets its own colour on the page, so visitors can tell a quick heads-up from a full-blown outage at a glance.
4. Write a short summary for the title and a longer explanation for the body.
5. Optionally, link the update to a specific monitor so readers know exactly what's affected.
6. Publish.

Subscribers (see the next section) are notified automatically. Visitors on your status page see the update prominently at the top of the page.

A typical incident timeline

You post updates as the situation develops, and they stack into one timeline:

1. High: "We're seeing elevated error rates and are looking into it."
2. Warning: "Root cause identified as a database replica failure. Failing over now, some requests may still error."
3. Info: "The failover completed. We're watching for any remaining errors."
4. Resolved: "The issue is fully resolved. Apologies for the disruption."

Each update appends to the same page, so the full history stays visible to visitors after the fact.

Scheduled maintenance

For planned work, use the Scheduled severity. You can post the update days or weeks in advance so subscribers see it before the work begins.

Posting status page updates through the API

You can also post status page updates via our API, which is great for automating post-incident updates from your deploy pipeline or internal incident management tool.