Service transparency you can rely on.
The OpenClawAi.run status page will provide real-time visibility into platform health, instance creation latency, console availability, and incident updates. We believe transparent status reporting is a core feature, not just a support tool.
What will appear on day one
The first version of the status page highlights overall service state, component health, incident timelines, and explanations for common "not a bug" scenarios such as idle auto-pause. The goal is to reduce confusion and help you decide quickly whether to retry or wait.
Components we will track
The hosted OpenClaw instance relies on multiple components. Tracking them separately helps you understand whether an issue is global or limited to a specific subsystem.
Instance creation
Status for queue length, average boot time, and errors when capacity is constrained.
Console access
Health indicators for dashboard load, session list refresh, and WebSocket connectivity.
Runtime execution
Signals for tool execution latency, sandbox availability, and error rates.
Gateway routing
Routing reliability for inbound channels like Telegram, Discord, or other connectors.
Credential services
Availability of BYOK storage, validation, and deletion workflows.
Notification system
Email and RSS alerts for incidents and scheduled maintenance windows.
Status categories you will see
We will use clear, human-readable status labels so you know what is happening without guessing.
Operational
The platform is running normally. Minor incidents are listed separately in the timeline.
Degraded performance
Some components may be slow or queued, but most features remain accessible.
Partial outage
One or more components are failing. The status page will describe affected areas.
Major outage
Most services are unavailable. We will post frequent updates until recovery.
Incident timeline preview
Each incident includes a timestamped timeline so you can see progress without refreshing support tickets. We follow a simple state progression: Investigating -> Identified -> Monitoring -> Resolved.
Sample incident entry
Title: Instance creation queue increased
Status: Monitoring
Impact: Some users may experience a 2-5 minute delay during instance creation.
Updates: 10:02 UTC investigating, 10:18 UTC identified, 10:40 UTC scaling capacity,
11:05 UTC monitoring, 11:30 UTC resolved.
The goal is not to write long reports. It is to show what is happening right now and when the next update will arrive.
Not every pause is an outage
Instances auto-pause when idle, and the free beta has clear runtime limits. The status page will highlight these rules to prevent confusion. If your instance pauses, check the console first before assuming there is a platform incident.
We will also link to troubleshooting steps so you can verify whether the issue is related to limits, credentials, or a broader system event.
Subscribe for updates (coming soon)
Status subscriptions will include email and RSS notifications. You can subscribe to all incidents or only to critical outages so you are not overwhelmed.
Stay informed without noise
We will only send alerts when there is meaningful impact. For general news and documentation updates, check the docs and FAQ pages or reach out directly to support.
If you need a specific SLA or custom reporting, contact support to discuss enterprise options.
Scheduled maintenance and historical context
The status page will also include planned maintenance windows so you can avoid running critical workflows during upgrade periods. Each maintenance entry will specify the date, expected duration, and affected components, along with a post-maintenance summary.
As the service matures, we will publish lightweight historical metrics such as recent incident counts and average instance creation time. These summaries help you judge stability without overwhelming you with dashboards. If you need a custom availability report, reach out to support and we will discuss options.
Status FAQ
How often will the status page update?
During incidents, updates will be posted regularly with timestamps. Outside incidents, the page will reflect current component health.
Does an auto-paused instance mean the service is down?
No. Auto-pause is part of the lifecycle policy. If the platform is down, the overall status will reflect it.
Transparency starts with the status page
The status page will launch alongside the hosted OpenClaw instance. Until then, you can use the docs and FAQ to understand lifecycle limits and expected behavior.