Incidents

Every important failure has a timeline, a status and a clear path to resolution.

Upcron opens an incident when a monitor, heartbeat, SSL check or component enters a failing state. Incidents contain the affected resource, the current status, automatic lifecycle events and human-authored updates.

Incident lifecycle

  • Open — Upcron detected a failure and notifications may be sent.
  • Update — Add context for your team or status-page subscribers.
  • Resolve — Confirm the service has recovered.
  • Reopen — Reopen a resolved incident if the problem returns.

Investigating an incident

  1. Open the incident from the Incidents section or from the affected monitor.
  2. Review its timeline, resource and latest check or ping status.
  3. Check the linked integrations and notification delivery.
  4. Add an update when the team has useful context.
  5. Resolve the incident once the resource is healthy again.

Status-page updates

Incident updates can be shared with linked status pages through Upcron's status-page notification flow. Keep updates short, factual and useful to the people waiting for recovery.

API and automation

Incident list, detail, update, resolve and reopen operations are available through the API reference when the corresponding endpoints are enabled.

Troubleshooting

Incident remains open after recovery
  • Check the latest monitor or heartbeat status
  • Confirm the resource is no longer inside a failing or maintenance state
  • Refresh the incident timeline before resolving it manually
Notifications were not sent
  • Check active integrations and notification trigger configuration
  • Verify that the resource is not covered by an active maintenance window
  • Send a test notification from the linked integration