outages.live
Live
Moonshot AIIncident ·

Minor Service Outage

ResolvedOfficial update
0

Moonshot AI reports that the K3 component operated with degraded service. Moonshot AI reports that the incident is resolved. The outage lasted 9 minutes.

State

Resolved

Started

Lasted

9 min

Worst impact

Degraded

Timeline

2 updates
04:0004:0204:0404:0704:09
DegradedUpdate postedTimes in UTC

Components degraded

9 min 100%

Updates

Times in UTC

As posted by Moonshot AI

Resolved
Components degraded

Affected components

1
K3

Moonshot AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

25

Median duration

22 min

This incident

59% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 h 40 min
median 22 min
90 days agoToday

Other Moonshot AI incidents

All incidents

Moonshot AI·Kimi Code K3 模型服务出现错误

Moonshot AI reports that the K3 model service and Kimi Code - K3 had many errors, and most requests did not complete. The incident is resolved. It lasted 4 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reported degraded service on the K3 component. Moonshot AI reports that the incident is resolved. The incident lasted 3 minutes.

Resolved

Moonshot AI·Kimi Code K3 TTFT 响应延迟升高

Moonshot AI reports that some requests to K3 and Kimi Code - K3 had higher TTFT latency. Moonshot AI resolved the incident. The incident lasted about 48 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that its K3 component did not work correctly. Moonshot AI now reports that the outage is resolved. The outage lasted 66 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that K2.7 Code Highspeed did not work correctly. Moonshot AI resolved the outage. The outage lasted 27 minutes.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=moonshot
Slack
/feed subscribe https://outages.live/feed.xml?providers=moonshot

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane