Public Status Pages & Incident Management

Open project settings, go to Reliability ops, and fill in the status page title, slug, and description. Enable it to publish at /app/status/{slug}.

Define the services on the status page — website availability, user journeys, or a custom component. These appear on the public page and link to incidents and maintenance windows.

From the Status page, choose a finding and open it as an incident. Review the prefilled source, severity, title, and summary, then publish the incident when it is ready.

When an alert rule threshold is crossed, NorthDuty creates or updates an incident. Subsequent alerts for the same rule increment the occurrence count without sending a new notification.

Add a maintenance window with a start time, end time, and reason. Alerts that fire during the window are suppressed. The window appears on the public status page so customers know what to expect.

Does NorthDuty include public status pages?

Yes. Every project can publish a public status page at a custom slug. Add status components, and incidents and maintenance windows appear on the page automatically.

How does incident management work in NorthDuty?

When an alert rule threshold is crossed, NorthDuty creates an incident and records each subsequent match as an occurrence — deduplicating notifications instead of resending them. You can also open a concrete health finding as an incident from Status, then update it from Investigating through to Resolved.

How do maintenance windows suppress alerts?

When a maintenance window is active, NorthDuty suppresses new alert notifications for that project. The window appears on the public status page so customers can see planned work without interpreting it as an unexpected outage.

Can I create incidents manually?

Yes. You can create incidents manually from project settings, or start from a concrete health finding on the Status page and let NorthDuty prefill the source, severity, title, and technical summary.