System status - Cortex Docs

Live component health, incident history, and scheduled maintenance are published on status.cortex.foundation. Bookmark that page; this article explains what it covers and how it relates to product troubleshooting.

Open status.cortex.foundation Troubleshooting

What we report

Component	What it covers
Web	The Cortex website and signed-in app shell at 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

Check the status page for the current banner and component states.
Subscribe there if you want updates for the next change.
Keep any request_id from an error in the app — see Troubleshooting and the problem catalog.

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	Live uptime, incidents, maintenance windows
Troubleshooting	What a specific product message means and what to do next
Security and privacy	Data handling — not availability
Changelog	What shipped — not outages

Troubleshooting — what a message in the product means.
Chat · Code · Bot · CLI — the surfaces status reports on.
Problem catalog — the error codes behind a failed request.

⌘I