> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/v1/instance-status.md). # DataOS Instance Status The DataOS Instance Status page shows the current health of every endpoint configured for your Instance, refreshed in near real time. It provides a quick way to determine whether an Instance-level issue is affecting your applications and workloads. The page answers one question: is the Instance healthy right now? This lets you rule the Instance in or out before investigating Tenant configuration, workload logs, or external systems. ## Access the status page Open the `/status/` path on your Instance domain: ``` https://.instance.dataos.cloud/status/ ``` Replace `` with your DataOS Instance name. **Example:** ``` https://productsandbox.instance.dataos.cloud/status/ ``` If prompted, sign in using your DataOS credentials or SSO. After sign-in, the Instance Status page opens. ## When to check it? * **At the start of the day**, to confirm the Instance is healthy before teams begin work. * **After any change to the Instance**, such as an upgrade or a configuration change, to confirm endpoints return to healthy. * **When a user reports errors or slowness**, before you investigate a Tenant, a workload, or an external system. * **When you raise an incident**, to record what was failing and for how long. ## How the page is organised? The banner at the top of the page summarises every check into a single verdict, for example **All Systems Operational**. If any endpoint is unhealthy, the banner reflects that instead. This is the one line to read first. Endpoints are grouped by the capability they support, making it easy to scan the overall status first. Each group can be expanded to view its individual endpoints, so you only need to open a group when you want to investigate its status. | Group | What it covers | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Control Plane and Data Plane Connectivity | The links between the Control Plane and each Data Plane: network gateways, inbound API traffic routing, and certificate management | | Data Access & Query | The query and data access path used to read data through DataOS | | Data Product Catalog & Discovery | The catalog services that let users find, browse, and inspect Data Products | | Dataplane Readiness | Whether each attached Data Plane is registered and ready to accept workloads | | Lakehouse Management | The services that manage Lakehouse storage and its metadata | | Platform App & Developer APIs | The APIs behind the DataOS applications and the developer-facing interfaces | | Platform Internals | Internal services the Instance depends on but that users do not call directly | | Resource Logs & Metrics | The logging and metrics pipeline that Resource observability depends on | | Resource Orchestration | The services that schedule and run DataOS Resources | | Sign-In & Access Control | Authentication, sign-in, and authorization services | {% hint style="info" %} The exact set of groups and endpoints reflects what is configured for your Instance, so your page may show more or fewer than the groups listed here. {% endhint %} ## How to act on a status? | Status | Meaning | What to do | | -------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | Healthy | The check passed within its configured threshold | Nothing | | Degraded | The endpoint responds, but slowly or intermittently | Check what changed on the Instance recently, then inspect the logs for that service | | Down | Consecutive checks have failed | Treat it as an Instance incident, work through your runbook, and escalate if the service does not recover | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://v2.dataos.info/operate/v1/instance-status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.