Is Kimi Code down?
How to check Kimi Code's status properly
Moonshot tracks no dedicated "Kimi Code" component. The tool depends on the "Open API" / "API Service" components (and the model components behind them), so those are what the panel filters to.
"Kimi" is the consumer chat product — it can be degraded while the API serving Kimi Code stays green, and vice versa.
The status page is hosted at status.moonshot.cn and reports in China Standard Time; incident timestamps are UTC+8.
Is it down, or is it just you?
A 401 or 403 error is almost always your own auth — an expired token or a session that needs re-login, not an outage. A run of 5xx errors, or a 529 "overloaded" response, during an incident that's actually listed on the vendor's status page is on them, not you.
Before you conclude it's a real outage: try a second surface (the web app instead of the CLI, or vice versa), rule out your own network or VPN, and only then treat the vendor's official status page as the final word.
What to do while Kimi Code is down
- Errors right after a big release (like Kimi K3) are usually capacity, not your setup — retry with backoff or drop to a K2-family model for the session.
- Subscription "credit exhausted" messages are quota, not an outage — Kimi Code credits drain fast on long agentic tasks.
- Kimi Code works with an API key too: if the subscription surface misbehaves while the API is green, metered API access is the workaround.
- For longer outages, an editor-agnostic tool like Aider pointed at another provider keeps you shipping.
Frequently asked questions
How do I check if Kimi Code is down?
The live board above reads Moonshot's official status API (status.moonshot.cn) directly in your browser, filtered to the Kimi and API components that Kimi Code depends on. If the board is unreachable, open status.moonshot.cn itself.
Why is Kimi Code slow or erroring with no incident listed?
The usual culprits are subscription credit limits (long agentic tasks drain them quickly, especially on the token-hungry K3 model) or launch-week congestion that never reaches the status page. Switching to metered API access, or to a K2-family model, isolates the layer.
Does Kimi Code have its own status page?
No — Moonshot publishes one status page for the whole platform at status.moonshot.cn, with components for the Kimi app, the Open API, and the model families. There's no Kimi Code-specific component, so API-component incidents are the closest official signal.