Incidents

Structured incident management

Detect, manage, and communicate incidents with clear timelines and real-time updates.
Timelines · visibility · WebSockets · status pages

Problem

Incidents without structure create confusion

During incidents, teams lose clarity. Updates are scattered, timelines are unclear, and communication breaks down.

Scattered updates

Unclear timelines

Broken handoffs

Statuslab provides a structured system to manage incidents from detection to resolution.

Lifecycle

A complete incident lifecycle

Every incident follows a defined lifecycle. Status transitions are explicit, consistent, and visible across the system.

  • Defined states
  • Clear transitions
  • Consistent updates
Incidents product page

Timeline

A clear, structured timeline

Track every incident through a chronological timeline. Publish updates as the situation evolves.

Add updates at any stagePublic or internal visibilityTimestamped entriesOrdered event history

Incident timeline

Elevated API latency

INC-204
  1. Investigating

    Initial triage and scope

  2. Monitoring

    Fix deployed; watching metrics

  3. Resolved

    Closed with timeline record

Real-time

Real-time visibility

Incident updates propagate instantly across dashboards and status pages.

  • Live updates via WebSocket
  • No refresh required
  • Immediate status changes

Realtime layer

WebSocket /status

Connected
  • Project dashboard

    room project:8f3a…c1

  • Gateway

    fan-out to rooms

  • Public status page

    room page:acme

Payload
monitorcomponentincident

Communication

Communicate with users

Publish incident updates directly to your status page. Keep users informed with accurate, structured communication.

Public incident visibilitySubscriber notificationsIncident history
Status pages
status.yourdomain.com

Components · 90-day uptime

APIOperational
99.98%90 days
DashboardOperational
99.95%90 days

Incident · scheduled maintenance Sat 02:00 UTC

History

Full incident history

Access both active and resolved incidents with complete timelines.

  • Active incidents view
  • Historical archive
  • Filtering by status
  • Pagination for large datasets

Incidents

3 active
  • INC-914InvestigatingToday · 09:12
  • INC-908MonitoringYesterday · 16:40
  • INC-901ResolvedJan 12 · 11:05

Archive · filters · pagination

Impact

Map incidents to system components

Link incidents to affected components to reflect real system impact.

Component-level impact

Tie incidents to the services your customers already see on the page.

Status propagation

Component state reflects incident state when you want it to.

Visibility per service

Show scope without over-sharing internal detail.

Maintenance

Planned maintenance, handled clearly

Manage scheduled maintenance alongside incidents.

Maintenance windowsStart, complete, cancelPublic visibility
Maintenance

Visibility

Separate internal and public communication

Not every update needs to be public. Maintain internal notes while publishing structured external updates.

Internal

Operator-only context

  • Notes for the response team
  • Links and references that do not belong on the public page
  • Staging updates before you publish externally

Public

What subscribers see

  • Structured updates on your status page
  • Clear timestamps and state
  • Controlled narrative under your rules

Summary

Incident management, without ambiguity

Statuslab provides a structured, real-time system for managing incidents and communicating status with clarity.

  • Explicit lifecycle and timelines
  • Dashboards and pages stay in sync
  • Public and internal updates on your terms

Manage incidents with precision

Create an account, open the incidents workspace, and connect your status page when you are ready.