Skip to main content
RubixKube publishes real-time status for every platform service at rubixkube.ai/status. Check there first whenever something feels slow or off, so you can quickly tell whether an issue is on our side or yours.

Open the live status page

Real-time health for every RubixKube service, with 7-day uptime and 30-day incident history.

​
What the status page shows

At a glance the page shows an overall banner (for example, “All systems operational”) and a live updated-seconds-ago timestamp. Each service has its own row with a 7-day uptime bar, a uptime percentage, and an operational state pill.

​
Services tracked

  • API. The public API at api.rubixkube.ai. Powers the console, the Rubix CLI, Observer registration, and all integrations.
  • Dashboard. The web console at console.rubixkube.ai.
  • AI Agents. The Cloud-side agents that power investigation, memory, and chat (RCA Pipeline, Memory, SRI Agent).
  • Investigations. The orchestration layer that runs RCAs, turns insights into reports, and drives remediation proposals.
  • Topology Engine. Builds and maintains the live Knowledge Graph of your environments.
  • Insights Engine. Detects anomalies and opens insights that feed investigations.
  • Event Streaming. The ingestion path Observers use to stream signals into RubixKube Cloud.
  • Graph Store. The storage layer behind the Knowledge Graph and historical incident data.

​
Incident history

The status page also maintains a 30-day incident history so you can see whether a recurring issue has happened before and how it was resolved.

​
During an incident

1

Check the status page first

Open rubixkube.ai/status. If the overall banner shows a degraded or outage state, the issue is on our side and the page will list the affected services.
2

Check your notification channels

Critical incidents are also posted to the channels you have configured for RubixKube updates (Slack, Teams, email). See Notifications.
3

Reach support if impact is significant

Email connect@rubixkube.ai with your Tenant ID, the timestamp of what you observed, and any relevant screenshots or logs. See Collecting diagnostics for the full list.

​
What counts as an incident

RubixKube reports on the services listed above. If your own infrastructure is degraded (cluster nodes unready, cloud provider outage, network partition on your side), it shows up in your environment cards and insights, but it does not affect the public status page. The Troubleshooting guide is the starting point there.

​
Reporting a suspected issue

If something feels off and the status page shows everything as operational, it is likely either a self-serve issue or a tenant-specific edge case.

Try the Troubleshooting guide

Covers the common self-serve fixes for console, observer, and integration issues.

Email support

For tenant-specific problems. Include your Tenant ID, timestamps, and any relevant logs or screenshots.

Troubleshooting

Self-serve diagnostics for common RubixKube issues.

Frequently Asked Questions

Quick answers to the most common questions.

Notifications

Route incident and status updates to your team channels.

Observer Agent

How the in-environment Observer connects back to the control plane.