Incident management

When DownCTL detects downtime, it's recorded privately first. Publishing it to your status page is a separate, deliberate step — nothing goes public without you choosing to share it.

Publishing an incident

1. Open the Incidents tab (workspace-level, across all sites, or from a specific site's alert history).
2. Find the detected downtime and click Publish.
3. The incident starts in the Investigating stage and immediately appears on the site's public status page.

Staged updates

Walk visitors through the incident as you learn more — each update is timestamped and shown in order on the status page:

Add an update at any stage with a short note — visitors see exactly what you post, in the order you posted it.

Post-mortems

Once an incident is resolved, you can draft and publish a post-mortem — a longer write-up of what happened, root cause, and remediation. It's optional and can be published any time after resolution, including well after the incident closes.

Reopening or closing

An incident can be reopened if the issue recurs, which resumes it at whichever stage makes sense. Incidents can also be closed directly without walking through every stage, for cases resolved faster than the update cadence would otherwise show.

Subscriber notifications

Visitors to a status page can subscribe with their email. Once subscribed (after confirming via email), they automatically receive a notification when:

• A new incident is published
• The incident's status changes
• A post-mortem is published

Notifications are queued automatically — there's nothing to trigger manually beyond publishing the update itself.

Next steps

• Status page branding — themes, accent color, logo
• Custom status page domain