Is Kimi down?

Moonshot AI

No — Kimi is working normally

Our sources see nothing wrong. If it still fails for you, the cause is most likely on your side — the tips further down cover the usual suspects.

Working since · Checked at

What our sources say

Official status page
Not published
Our test requests, last hour
Not running for this service
Traffic through OpenRouter
0 of 4 models failing, 100% of requests succeeded in 30 min
Reports from visitors, last hour
0

Moonshot AI has no public status page.Open Kimi ↗

Last 24 hours

16:42 UTC — Working17:12 UTC — Working17:42 UTC — Working18:12 UTC — Working18:42 UTC — Working19:12 UTC — Working19:42 UTC — Working20:12 UTC — Working20:42 UTC — Working21:12 UTC — Working21:42 UTC — Working22:12 UTC — Working22:42 UTC — Working23:12 UTC — Working23:42 UTC — Working00:12 UTC — Working00:42 UTC — Working01:12 UTC — Working01:42 UTC — Working02:12 UTC — Working02:42 UTC — Working03:12 UTC — Working03:42 UTC — Working04:12 UTC — Working04:42 UTC — Working05:12 UTC — Working05:42 UTC — Working06:12 UTC — Working06:42 UTC — Working07:12 UTC — Working07:42 UTC — Working08:12 UTC — Working08:42 UTC — Working09:12 UTC — Working09:42 UTC — Working10:12 UTC — Working10:42 UTC — Working11:12 UTC — Working11:42 UTC — Working12:12 UTC — Working12:42 UTC — Working13:12 UTC — Working13:42 UTC — Working14:12 UTC — Working14:42 UTC — Working15:12 UTC — Working15:42 UTC — Working16:12 UTC — Working

24 h agonow

Last 30 days

28 Sept — No data29 Sept — No data30 Sept — No data1 Oct — No data2 Oct — No data3 Oct — No data4 Oct — No data5 Oct — No data6 Oct — No data7 Oct — No data8 Oct — No data9 Oct — No data10 Oct — No data11 Oct — No data12 Oct — No data13 Oct — No data14 Oct — No data15 Oct — No data16 Oct — No data17 Oct — No data18 Oct — No data19 Oct — No data20 Oct — No data21 Oct — No data22 Oct — No data23 Oct — Working24 Oct — Working25 Oct — Working26 Oct — Working27 Oct — Working

30 days agoyesterday

5 of 5 days with data had no problems.

Recent incidents

No incidents in the last 30 days.

About this service

We test the international Moonshot AI platform. The Kimi chat app is a separate front end on top of the same models.

Other model APIs right now

Kimi: common questions

Is the Kimi API down, or is it my code?

Look at the HTTP status. 401 and 403 mean a key or permission problem, 400 and 422 a malformed request, 429 a rate or spending limit. Only 500, 502, 503, 504 and timeouts point at Moonshot AI. If this page is green while you get them, send a minimal request with curl to rule out your client library or proxy.

How should my app handle Kimi outages?

Retry 429 and 5xx responses with exponential backoff and a little random jitter, cap the number of attempts, and set a timeout so stuck streams don't pile up. For anything users see, keep a fallback model from another vendor configured and switch to it automatically after a few failures in a row — the list above shows which ones are healthy right now.

Why do my requests fail when others say it works?

Limits apply per organisation and per model, so your account can be throttled while everyone else is fine. Newly released and very large models are also the first to be rate-limited at busy hours. Check the usage page of your account, try a smaller model and make sure you call the right base URL and region.

Responses are slow but they arrive. Does that count as an outage?

Watch the time to the first token rather than the total time. On our own test requests we flag a slowdown when the first token takes more than 3 seconds and three times longer than the day's median. Long prompts and long outputs are slow by nature and are not treated as a problem.

How do you know whether Kimi is down?

For Kimi we combine the share of successful requests to Moonshot AI's models on OpenRouter and reports from people who press the button on this page. The most serious signal that is still fresh sets the verdict, and stale sources are ignored rather than trusted. The page refreshes by itself; the exact thresholds are on our “How we check” page.

How we check →