Updated 25 October 2026 · By the Upcertain team
When an incident opens and closes
- It opens when a check fails and every confirmation check after it fails too.
- Its start time is the first failed check, so the recorded duration matches what users saw.
- It resolves on its own at the first passing check, and every channel that got the alert gets the recovery.
- If the monitor fails again later, a new incident opens. Incidents are never reopened.
Acknowledge
Open the incident from the alert, or from Incidents in the app, and acknowledge it. Acknowledging records who took it and stops repeat reminders on every channel. Owners, admins and editors can acknowledge; email alerts show the button only to people who can use it.
What the incident shows
- The cause: a status code, a timeout, a missing or unwanted keyword, a DNS failure, a refused connection, a certificate problem or a missed heartbeat.
- The failed request (method, URL and headers) and the response (status, headers and the start of the body), when the check made one.
- A timeline of detection, confirmation, alerts, acknowledgement, notes and recovery.
Notes for your team
Add notes to the timeline: what you found, what you changed, who is on it. Notes are visible to members of the account, not on status pages.
Tell customers
Use Post status update on the incident to publish an update to the status pages that show the affected monitor. It appears on the page and goes by email to the page's subscribers. Short templates are in incident communication templates.
Find and export
The incident list searches by monitor, filters by status or tag and sorts. Export the list as CSV with the incident id, monitor, target, status, cause, status code, detail, start, resolution, duration in seconds and who acknowledged it. The REST API and the MCP server return the same records.