API 服务可用性低
The Moonshot AI API Service and Kimi API Service had low availability. Moonshot AI reports that the incident is resolved. The outage lasted about 80 minutes, from 09:25 to 10:45 UTC on 19 November 2026.
State
Resolved
Started
Lasted
1 h 20 min
Worst impact
Major outage
Timeline
2 updatesInvestigating
1 h 20 min 100%
Updates
Times in UTCAs posted by Moonshot AI
This incident has been resolved.
API 服务可用性低,可能会影响您的使用体验
Affected components
2Moonshot AI in the last 90 days
Full historyIncidents in 90 days
94
Days with an incident
33
Median duration
22 min
This incident
3.6× the median
Other Moonshot AI incidents
All incidentsMoonshot AI·google登录异常
Google sign-in does not work for the Sign In / Sign Up components and the Kimi Sign In / Sign Up component. Moonshot AI reports that this incident is resolved. The outage lasted 13 minutes.
Moonshot AI·API 服务可用性低
The API Service and Kimi - API Service have low availability for Moonshot AI. Moonshot AI reports that the incident is resolved. It lasted 20 minutes.
Moonshot AI·Minor Service Outage
The K3 component had degraded service in a minor outage. Moonshot AI reports that the outage is resolved. It lasted 12 minutes.
Moonshot AI·Minor Service Outage
Remote Control had degraded performance on Moonshot AI. Moonshot AI reports that the outage is resolved. The outage lasted 6 minutes.
Moonshot AI·Minor Service Outage
Moonshot AI reports degraded service on K3.1 Pro Highspeed. Moonshot AI reports that the incident is resolved. The outage lasted 102 minutes.
Follow Moonshot AI
Your coding agent knows when Moonshot AI is down, and tells you when a failure is theirs, not yours. You can also get Moonshot AI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "moonshot" and tell me if Moonshot AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=moonshot/feed subscribe https://outages.live/feed.xml?providers=moonshotFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane