Incidents
Incidents overview
Follow detection, acknowledgement, assignment, recovery, and resolution.
An incident records a confirmed monitoring problem and the team’s response from detection through resolution.
Incident timeline
The typical flow is:
- A check fails.
- PingAgain confirms the problem according to the monitor policy.
- An incident opens with a severity and affected monitor.
- A team member acknowledges it and can take assignment.
- Notes record useful investigation updates.
- Healthy confirmation marks monitoring recovery.
- A team member resolves the incident after the response work is complete.
Open Incidents for the account-wide list, or open a monitor’s Incidents section for that monitor.
Recovery versus resolution
Recovery is a monitoring event: healthy checks confirmed that the monitored target is responding again. Resolution is a team decision: the investigation, communication, and follow-up are complete.
An incident can therefore be recovered but not yet resolved. This gives the team time to add a final note or finish follow-up without presenting the target as still failing.
Next: learn how to manage an incident, configure alert destinations, or control status-page incident visibility.