The Incidents page shows a full history of all incidents on your team — open, acknowledged, and resolved. This article explains how to navigate and filter the list.
Opening the Incidents List
In the left sidebar, click Incidents.
Filtering Incidents
By Status
Use the Status filter tabs at the top of the page:
- All — every incident regardless of status
- Open — incidents that haven't been acknowledged or resolved
- Acknowledged — incidents someone is actively working on
- Resolved — closed incidents
By Severity
Use the Severity filter dropdown to show only incidents of a specific severity level: Critical, High, Medium, or Low.
Combining Filters
Status and severity filters work together. For example, filter by Open status and Critical severity to see only the most urgent active incidents.
What Each Row Shows
| Column |
Description |
| Severity badge |
Color-coded severity level (Critical = red, High = orange, Medium = yellow, Low = blue) |
| Title |
Auto-generated description of what failed |
| Monitor |
The endpoint that triggered the incident |
| Status |
Current lifecycle status |
| Started |
When the incident was created |
| Duration |
Time since the incident started (or total duration if resolved) |
Viewing an Incident's Details
Click any row to open the incident detail page. The detail page shows:
- Full incident information (status, severity, timeline)
- The affected monitor
- Check history around the time of the incident
- Pulse AI analysis (if available)
- Resolve and acknowledge buttons (if you have permission)
Viewing Incidents for a Specific Monitor
On the monitor detail page, there is a Recent Incidents section that lists only incidents associated with that specific monitor. This is useful for reviewing the incident history of a particular endpoint without filtering the full incidents list.
Related Articles
Still have questions? Contact support.
Related Articles
Viewing Check History
The check history is a log of every HTTP request PulseAPI has made to a monitor. It's the primary tool for diagnosing problems, understanding patterns, and reviewing past incidents. How to Access Check History In the left sidebar, click Monitors. ...
Understanding Incident Severity Levels
Every incident in PulseAPI has a severity level: Critical, High, Medium, or Low. This article explains how severity is determined and how to use it effectively. How Severity Is Determined Severity is set by the alert rule that triggered the incident. ...
What Is an Incident?
An incident is PulseAPI's record of a problem with one of your monitors. This article explains what triggers an incident, what information it contains, and how it relates to alert rules. What Creates an Incident Incidents are created automatically — ...
Resolving an Incident
Resolving an incident closes it — the problem is fixed and the endpoint is healthy. Incidents can be resolved automatically by PulseAPI or manually by a team member. Prerequisites: You must be a team Owner, Admin, or Member to resolve incidents. ...
Acknowledging an Incident
Acknowledging an incident tells your team that someone is aware of the problem and actively working on it. It moves the incident from Open to Acknowledged status. Prerequisites: You must be a team Owner, Admin, or Member to acknowledge incidents. ...