> ## Documentation Index
> Fetch the complete documentation index at: https://cortex-foundation-add13747-droid-2a5c5e50-docs-ferndesk-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# System status

> Live availability for Cortex Web, API, Chat, Code, and Bot — incidents, maintenance, and history.

<div className="status-cortex-logo">
  <img src="https://mintcdn.com/cortex-foundation-add13747-droid-2a5c5e50-docs-ferndesk-pro/mRlLmc4oADWhn8g2/logo/banner-light.png?fit=max&auto=format&n=mRlLmc4oADWhn8g2&q=85&s=1c6d57f45d2af6b80f2eb1619d14d9d9" alt="Cortex" width="220" data-path="logo/banner-light.png" />
</div>

Live component health, incident history, and scheduled maintenance are published on **[status.cortex.foundation](https://status.cortex.foundation)**. Bookmark that page; this article explains what it covers and how it relates to product troubleshooting.

<p className="ink-cta-row">
  <a className="ink-btn" href="https://status.cortex.foundation">Open status.cortex.foundation</a>
  <a className="ink-btn ink-btn-quiet" href="/getting-started/troubleshooting">Troubleshooting</a>
</p>

## What we report

| Component | What it covers                                                                               |
| --------- | -------------------------------------------------------------------------------------------- |
| **Web**   | The Cortex website and signed-in app shell at [cortex.foundation](https://cortex.foundation) |
| **API**   | Product API routes used by Chat, Code, Bot, Design, and the CLI                              |
| **Chat**  | Conversations, tools, Deep Research, images, and related Chat services                       |
| **Code**  | Code Cloud sessions, desktop/CLI coding agent backends, and related Code services            |
| **Bot**   | Bot computers, approvals, routines, and related Bot services                                 |

Component names stay product-facing. Individual incidents may mark one or more of these surfaces as affected.

## During an incident

1. Check the status page for the current banner and component states.
2. Subscribe there if you want updates for the next change.
3. Keep any `request_id` from an error in the app — see [Troubleshooting](/getting-started/troubleshooting) and the [problem catalog](/problems).

User-facing error text names a Cortex surface, never a vendor. Status updates are the place for fleet-wide notices.

## Documentation vs status

| Resource                                                     | Use it for                                                |
| ------------------------------------------------------------ | --------------------------------------------------------- |
| [status.cortex.foundation](https://status.cortex.foundation) | Live uptime, incidents, maintenance windows               |
| [Troubleshooting](/getting-started/troubleshooting)          | What a specific product message means and what to do next |
| [Security and privacy](/security/overview)                   | Data handling — not availability                          |
| [Changelog](/changelog)                                      | What shipped — not outages                                |

## Related

* [Troubleshooting](/getting-started/troubleshooting) — what a message in the product means.
* [Chat](/chat) · [Code](/code) · [Bot](/bot) · [CLI](/cli) — the surfaces status reports on.
* [Problem catalog](/problems) — the error codes behind a failed request.