Status updates tell visitors what is going on, in your own words. People who subscribe to the page hear about them right away.
Post an update
- Open the status page and choose the Updates tab.
- Choose Report incident and enter a Title.
- Pick the Status. Start with Investigating, then Identified, Monitoring and finally Resolved. Use Notice for news that isn’t a problem.
- Write the Message, or open Templates for a suggested text you can edit.
- Pick the Affected components. Subscribers who follow only other components aren’t notified. Choose none for the whole page.
- Give each affected component its impact: Degraded performance (slow or flaky, but working), Partial outage (down for some users or features) or Major outage (down for everyone). From checks leaves it to the monitor.
- Keep the box that notifies subscribers ticked and choose Post update.
While the update is open, each affected component shows the worse of your impact and what the checks find. An update can make a component look worse, but it can’t hide an outage the checks confirmed. The JSON summary and the badge follow the same rule.
An update stays at the top of the page until it is resolved. To continue the thread, choose Post update on it.
Subscribers
- Visitors subscribe on the public page by email, Slack, Microsoft Teams, Discord or webhook, to the whole page or to chosen components.
- Email subscribers confirm their address first. Chat subscribers get a first message right away, so a wrong address shows up before it is saved.
- Everyone can unsubscribe from any message.
- The Updates tab says how many people subscribe, and how many haven’t confirmed yet.
- Subscribers also hear about planned maintenance.
Language and times
Choose the page’s Language on the Settings tab: English, Swedish, Danish, Norwegian, Finnish, German, French, Spanish or Dutch. Times on the page are in UTC, with the zone written out, so every visitor reads the same clock. For widgets and badges, see how to customize a status page.