Status / Kimi (Moonshot AI)
K Live monitoring · checked every 2 minutes · last check 6s ago
Is Kimi down? Kimi (Moonshot AI) status right now
No, Kimi is up and working normally.
Operational Current status
100% Uptime 24h
100% Uptime 30 days
1184 ms API response time
Last 24 hours 05:54 UTC · 0 checks · 0 failed · avg — 06:24 UTC · 0 checks · 0 failed · avg — 06:54 UTC · 0 checks · 0 failed · avg — 07:24 UTC · 0 checks · 0 failed · avg — 07:54 UTC · 0 checks · 0 failed · avg — 08:24 UTC · 0 checks · 0 failed · avg — 08:54 UTC · 0 checks · 0 failed · avg — 09:24 UTC · 0 checks · 0 failed · avg — 09:54 UTC · 0 checks · 0 failed · avg — 10:24 UTC · 0 checks · 0 failed · avg — 10:54 UTC · 0 checks · 0 failed · avg — 11:24 UTC · 0 checks · 0 failed · avg — 11:54 UTC · 0 checks · 0 failed · avg — 12:24 UTC · 0 checks · 0 failed · avg — 12:54 UTC · 0 checks · 0 failed · avg — 13:24 UTC · 0 checks · 0 failed · avg — 13:54 UTC · 0 checks · 0 failed · avg — 14:24 UTC · 0 checks · 0 failed · avg — 14:54 UTC · 0 checks · 0 failed · avg — 15:24 UTC · 0 checks · 0 failed · avg — 15:54 UTC · 0 checks · 0 failed · avg — 16:24 UTC · 0 checks · 0 failed · avg — 16:54 UTC · 0 checks · 0 failed · avg — 17:24 UTC · 0 checks · 0 failed · avg — 17:54 UTC · 0 checks · 0 failed · avg — 18:24 UTC · 0 checks · 0 failed · avg — 18:54 UTC · 0 checks · 0 failed · avg — 19:24 UTC · 0 checks · 0 failed · avg — 19:54 UTC · 0 checks · 0 failed · avg — 20:24 UTC · 0 checks · 0 failed · avg — 20:54 UTC · 0 checks · 0 failed · avg — 21:24 UTC · 0 checks · 0 failed · avg — 21:54 UTC · 0 checks · 0 failed · avg — 22:24 UTC · 0 checks · 0 failed · avg — 22:54 UTC · 0 checks · 0 failed · avg — 23:24 UTC · 0 checks · 0 failed · avg — 23:54 UTC · 0 checks · 0 failed · avg — 00:24 UTC · 0 checks · 0 failed · avg — 00:54 UTC · 0 checks · 0 failed · avg — 01:24 UTC · 0 checks · 0 failed · avg — 01:54 UTC · 0 checks · 0 failed · avg — 02:24 UTC · 0 checks · 0 failed · avg — 02:54 UTC · 12 checks · 0 failed · avg 856 ms 03:24 UTC · 15 checks · 0 failed · avg 547 ms 03:54 UTC · 15 checks · 0 failed · avg 688 ms 04:24 UTC · 15 checks · 0 failed · avg 756 ms 04:54 UTC · 15 checks · 0 failed · avg 759 ms 05:24 UTC · 15 checks · 0 failed · avg 815 ms 24h ago now
API response time (24h) 0 1279 2559 p50 463 ms · p95 1669 ms (ms, UTC)
90-day uptime history 2026-06-27: no data 2026-06-28: no data 2026-06-29: no data 2026-06-30: no data 2026-07-01: no data 2026-07-02: no data 2026-07-03: no data 2026-07-04: no data 2026-07-05: no data 2026-07-06: no data 2026-07-07: no data 2026-07-08: no data 2026-07-09: no data 2026-07-10: no data 2026-07-11: no data 2026-07-12: no data 2026-07-13: no data 2026-07-14: no data 2026-07-15: no data 2026-07-16: no data 2026-07-17: no data 2026-07-18: no data 2026-07-19: no data 2026-07-20: no data 2026-07-21: no data 2026-07-22: no data 2026-07-23: no data 2026-07-24: no data 2026-07-25: no data 2026-07-26: no data 2026-07-27: no data 2026-07-28: no data 2026-07-29: no data 2026-07-30: no data 2026-07-31: no data 2026-08-01: no data 2026-08-02: no data 2026-08-03: no data 2026-08-04: no data 2026-08-05: no data 2026-08-06: no data 2026-08-07: no data 2026-08-08: no data 2026-08-09: no data 2026-08-10: no data 2026-08-11: no data 2026-08-12: no data 2026-08-13: no data 2026-08-14: no data 2026-08-15: no data 2026-08-16: no data 2026-08-17: no data 2026-08-18: no data 2026-08-19: no data 2026-08-20: no data 2026-08-21: no data 2026-08-22: no data 2026-08-23: no data 2026-08-24: no data 2026-08-25: no data 2026-08-26: no data 2026-08-27: no data 2026-08-28: no data 2026-08-29: no data 2026-08-30: no data 2026-08-31: no data 2026-09-01: no data 2026-09-02: no data 2026-09-03: no data 2026-09-04: no data 2026-09-05: no data 2026-09-06: no data 2026-09-07: no data 2026-09-08: no data 2026-09-09: no data 2026-09-10: no data 2026-09-11: no data 2026-09-12: no data 2026-09-13: no data 2026-09-14: no data 2026-09-15: no data 2026-09-16: no data 2026-09-17: no data 2026-09-18: no data 2026-09-19: no data 2026-09-20: no data 2026-09-21: no data 2026-09-22: no data 2026-09-23: no data 2026-09-24: 100.00% up · 0 failed / 87 checks 90 days ago 100% uptime today
FAQ Is Kimi down? No, Kimi is up and working normally. ModelBank checks Kimi (Moonshot AI) every 2 minutes from Cloudflare’s global network and also reads the official status page. Last check: 6s ago.
What is Kimi’s uptime? Measured by ModelBank: 100% in the last 24 hours, 100% over 30 days and 100% over 90 days.
What should I do if Kimi is not working? First check this page and the official status page. If Kimi is up for everyone else, try clearing cache, logging out and in, switching network, or checking your API key and rate limits (HTTP 429). If it is a real outage, switch to an alternative model — see the alternatives on this page — or use a router with automatic failover.
Having problems with Kimi? 0 reports in the last hour · 0 in 24h
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Signals
Our API probe API responded HTTP 401 in 1184 ms
Official status All Systems Operational
Status since 2h ago
Components Website
Open API
API Service
Open Platform Portal
Sign In / Sign Up
File uploads
Search
Model
Vision Model
Thinking Model
Text Model
Research Model
K2 Model
Moonshot models USD per 1M input / output tokens
Alternatives if it’s down
Embed this status [](https://modelbank.ai/status/kimi)
Get notified when Kimi goes down We’ll notify you the moment ModelBank detects a Kimi outage, and again when it recovers.
Get free alerts Browser push · Slack / Discord · Feishu / DingTalk / WeCom · RSS — free, no sign-up