Incidents
Structured incident management
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
Timeline
A clear, structured timeline
Track every incident through a chronological timeline. Publish updates as the situation evolves.
Incident timeline
Elevated API latency
Investigating
Initial triage and scope
Monitoring
Fix deployed; watching metrics
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
Project dashboard
room project:8f3a…c1
Gateway
fan-out to rooms
Public status page
room page:acme
Communication
Communicate with users
Publish incident updates directly to your status page. Keep users informed with accurate, structured communication.
Components · 90-day uptime
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
- 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.
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

