Incident management

Follow a failure until service recovery is recorded.

Connect failed checks, active incidents, supported notifications, and healthy recovery into one monitor-linked history.

Start monitoring Read the documentation
Check passed
Check failed
Incident opened
Contacts notified
Recovery recorded

Automatic opening

A failed check can create the active incident.

Monitor context

Keep the affected service attached to the record.

Recorded recovery

A healthy result resolves the active event.

Preserved duration

Retain start, end, state, and elapsed time.

01Detection

Create context at the moment of failure.

A failing check is tied to its monitor and recorded with timestamps and safe failure context inside the authenticated workspace.

02Lifecycle

Recovery belongs in the same record.

The next healthy result resolves the active incident while preserving when it began, when it ended, and how long it lasted.

03Analysis

See incidents beside the checks around them.

Reports compare incident count with uptime, successful and failed checks, and response trends across the selected range.

04Public communication

Publish only reduced, safe incident state.

Status pages deliberately exclude raw responses, private URLs, request configuration, tokens, and internal exceptions.

Continue the workflow

Related capabilities

Explore every feature
Understand

Monitoring reports

Compare incidents with retained checks.

Explore capability Communicate

Status pages

Publish deliberately reduced incident state.

Explore capability Operate

Alerts & notifications

Route opening and recovery events.

Explore capability
Start with PingBeacons

Keep the complete record from failure to recovery.

Connect every active incident to the monitor, checks, notifications, and healthy result that resolved it.

Start monitoring Explore features