System Status,
Engineered.
Monitor services across regions. Model components and publish incident timelines from one project. Branded status pages update in real time. Operators and subscribers see the same system state.
Core Model
A Structured System for System Status
One configuration path: probes run monitors, components represent state, incidents structure communication, and status pages publish what subscribers need.
Monitors
Probe-generated signals and check history.
Components
Rolled-up state shown on your public page.
Incidents
Structured timelines and visibility rules.
Status pages
Branded subdomain, subscribers, uptime.
Capabilities
Everything you need to manage system status
Deep links go to product pages for detail.
Monitor systems
Run HTTP and TCP checks across regions with real-time visibility and history.
ProductManage incidents
Create, update, and resolve with structured timelines and visibility controls.
ProductPublish status
Share operational state with components, uptime, and maintenance windows.
ProductNotify subscribers
Email subscribers when incidents change. Verification flow included.
ProductMonitoring
Reliable monitoring across regions
Configure HTTP and TCP monitors. HTTP checks record DNS and connect timings where applicable. Run checks on a schedule or on demand. Review history, charts, and statistics in the dashboard.
Incidents
Structured Incident Communication
Track incidents from open to resolved. Post updates as facts change. Control which updates appear on your public status page.
Incidents & AlertsIncident timeline
Elevated API latency
Investigating
Initial triage and scope
Monitoring
Fix deployed; watching metrics
Resolved
Closed with timeline record
Status Pages
Public status pages, built for clarity
Publish components, active incidents, maintenance windows, and rolling uptime in one place. One source of truth for customers and internal teams.
Status pagesComponents · 90-day uptime
Subdomain · branding · theme
Real-time
Real-time Updates, Built In
Status changes propagate over WebSocket connections to /status. Channels for project dashboards and public pages keep operators and visitors in sync without manual refresh.
Realtime layer
WebSocket /status
Events flow through one gateway to project dashboards and public status pages.
Project dashboard
room project:…
Gateway
Fan-out to rooms
Public status page
room page:…
Infrastructure
Built for distributed systems
Regions and probe workers run checks close to your users. The API coordinates scheduling, state, and delivery at scale.
Region registry
Probe workers register per region. The control plane tracks heartbeats and routes checks without duplicating configuration.
| Region | Label | Probes | Median RTT |
|---|---|---|---|
| eu-central | 12 | 38ms | Healthy |
| us-east | 14 | 22ms | Healthy |
| ap-southeast | 10 | 51ms | Healthy |
Use cases
Designed for modern systems
One workspace for teams that ship software and teams that run it—same monitors, incidents, and status pages.
SaaS platforms
Communicate availability and incidents with timelines customers can trust.
ExampleCustomer-facing status during deploys.
APIs
Monitor endpoints and publish the same state you use internally.
ExamplePublish API availability beside internal monitors.
Infrastructure teams
Track health across services and regions from one project.
ExampleOne map for services and regions.
Trust
Clarity when it matters most
During incidents, unclear communication erodes trust. Statuslab keeps updates structured, timelines explicit, and visibility consistent across operators and subscribers.
- Timestamps on incident updates
- Explicit state—not vague labels
- Subscriber visibility you control
Security and data handling are summarized on the security page.