Kimi won't load, says “server busy”, won't send a login code or stops making slides? Start with the six quick checks, then find your exact problem below, from the chat and apps to Kimi Code and the API.
These fix most problems in a couple of minutes. Work through them in order.
Look at a status tracker or search “Kimi down” on X. If many people report problems, wait; nothing on your side will fix an outage.
Reload the page, then try again in a fresh chat. Very long chats can slow down or fail.
If kimi.com works elsewhere, the problem is your browser: clear cookies for kimi.com and turn off ad blockers.
Some VPNs, proxies and work networks block Kimi. Try mobile data to rule out your network.
Agent tasks such as Slides, Deep Research and Agent Swarm stop when monthly credits run out.
On phones and desktop, install the latest Kimi app or Kimi Work version from the official store or kimi.com.
Before you change settings, find out which side the problem is on. It saves a lot of time.
Two questions tell you whether to fix something or simply wait.
Pick a category or search, then open a problem to see the fixes.
Showing all 25 problems
No matching problems. Try a different word, or contact Kimi support.
The exact wording can differ between the website, the apps and over time, but these are the usual meanings.
| What you see | What it means | What to do |
|---|---|---|
| Server is busy / try again later | Kimi has more requests than it can handle right now | Wait a minute, retry once, start a new chat |
| Usage limit reached | You've used your plan's allowance for now | Wait for the reset or upgrade |
| Network error | Your connection dropped or something blocked the request | Check Wi-Fi, VPN and extensions, then refresh |
| File failed to upload or parse | The file is too big, locked, damaged or a scan | Under 100 MB, no password, OCR for scans |
| Content can't be shown | The request or reply triggered a safety filter | Rephrase the request |
| Context too long | The chat or file is more than the model can hold | New chat, shorter input or split the file |
From Kimi's API error reference. The JSON response includes error.type, error.message and a request_id to send to support.
| Code | Meaning | Fix |
|---|---|---|
| 400 | Bad request: wrong format, missing parameter or input too long | Check the request body and shorten the input |
| 401 | Invalid or missing API key | Check the key and use the endpoint for that key's platform |
| 403 | No permission or balance used up | Top up, or check the API is open to your account |
| 404 | Model or resource not found | Check the model name and your account tier |
| 429 | Rate limit, low balance or engine overloaded | Read error.type, then back off, reduce concurrency or top up |
| 499 | Client closed the connection | Check proxy, KeepAlive and timeout settings |
| 500 | Server error | Retry later; send the request_id to support if it continues |
| 503 | Service temporarily unavailable | Retry later, usually during scaling or maintenance |
Retry-After.Setup, keys and pricing: Kimi API guide. Coding tools: Kimi Code guide.
Open Account, then User Feedback, then Help & Feedback in the lower-left corner of kimi.com.
Go to Settings, then Help & Feedback. Attach a screenshot of the problem.
Your registered phone or email, the device and browser, the time it happened, a screenshot and, for the API, the request_id.