Incidents: internal or public at a glance

An internal incident is on no status page, and nobody is notified. A notice at the top of the incident now says so. In the incident list, on the dashboard and on the service page it carries the Internal badge, and the list can be filtered by it.

When creating an incident, Publish now decides whether it appears right away or stays internal for now. Publish puts it on your status pages later. Before that you see where it appears and which message goes to how many subscribers. Whether it goes out at all is your call, through the API and MCP as well. Make internal takes it off every status page at once.

If you mark an incident as resolved only later, enter under Resolved at when it was really over. This works when resolving, in the update form and on the edit page. The downtime of the affected services follows it. AI assistants can set the time through MCP as well.

In Activity you can now pick several people, categories and channels at once. The active filters sit above the list and can be removed one by one. To covers the whole day in your time zone.

An update with the status Resolved closes the incident. In the update form it therefore now needs the Resolve Incidents right, as it already did in the API. Notes on an incident that is already resolved still work without it.

When you make an internal incident public, your subscribers now get the latest message. Until now they got the first one, so for an incident that was already resolved it still said “We are investigating …”. If you publish an incident again, a message that was already sent no longer goes out a second time unless you ask for it.

Visitors now see your status page in their browser's language. If the page does not offer that language, it appears in English if available, otherwise in its default language. Until now, English-speaking visitors to German-only status pages sometimes landed on an English version that does not exist.