Keep visitors informed during an incident

A little context goes a long way

Owners and admins on Business or Enterprise can open Status page → Incidents. Save your status-page draft first. Choose Draft an update to write a title, public message and incident state.

Choose up to 100 affected components from the published page, or leave the selection empty for a page-wide update. You need permission to manage selected monitors. Titles allow 120 characters and messages allow 4,000 characters of plain text.

Start from a detection, safely

In Detections, choose Draft public update beside a downtime record. UptimeOwl opens a private draft using the published component label and neutral starter wording. A recovered detection starts in Watching recovery; an open detection starts in Taking a closer look.

The monitor must already be a published component that you can manage. Raw errors, response logs, target URLs, private monitor names and diagnostic details are not copied. Repeating the action opens the same incident draft instead of making a duplicate. Seeding never publishes automatically.

Review before an update leaves the nest

Each publication adds a timestamped history entry. Visitors can follow an incident and browse earlier updates. Saving another draft never rewrites an already published entry. If another admin saves first, reload the draft before retrying.

1. Write your public explanation and select the affected components.
2. Save public draft. Existing public wording stays unchanged.
3. Use Review draft to check the wording, then Publish update and confirm. Your status page must already be published.

Keep the story moving

Taking a closer look means you are investigating. The cause is in sight means you have identified the issue. Watching recovery means you are checking that service stays steady. Back on steady ground marks the incident resolved.

Write and publish a fresh message when moving to another state. A healthy monitor check does not automatically resolve a public incident, and a public incident does not pause checks or change alerts. No subscriber emails are sent by this feature yet.

Bring an incident back inside

Unpublish hides the whole incident and its history while keeping your draft and records. Publishing again makes that history visible again and adds the reviewed draft as a new entry. To permanently remove an incident and all its published entries, choose Delete and confirm. This cannot be undone; use Unpublish if you may need the history again. Individual timeline entries cannot be deleted separately.

Public incidents use their reviewed component labels even if a monitor is later renamed, paused or removed. They are separate from plan-limited detection history. Unpublishing the status page, suspension or loss of status-page eligibility hides all public incidents.

Public lists show 20 incidents at a time, newest created first. Each incident history shows 20 updates at a time, newest published first. Times are displayed in UTC.