Incidents

Incidents communicate problems to your visitors. Manage them under Incidents.

Creating an incident

Incidents → New incident. Set:

• Title — a short summary.
• Impact — none, minor, major, critical, or maintenance.
• Status — investigating, identified, monitoring, or resolved.
• Affected services (optional) — tick the services this incident affects.
• First update (optional) — the opening message on the timeline.

Posting updates

Open an incident and post updates as the situation develops. Each update carries a status; setting the status to resolved marks the incident resolved and stamps the resolution time.

Affected services

Attaching services links the incident to them. On the public page's uptime chart, a day's tooltip shows the incidents that affected that service. Incidents with no attached services are treated as page-wide and show on every service's tooltip. You can edit affected services anytime from the incident's detail page.

Public history

Active incidents appear at the top of the status page. Resolved ones move to Past incidents, and the full timeline is always available at /history (linked from the status page footer).

Every incident also has its own public page (linked from its title on the status and history pages) that you can share directly — it shows the incident's status, affected services, and full update timeline.

Next: Maintenance windows.