outages.live
Live
Moonshot AIIncident · 2026-11-02 15:54 UTC

Minor Service Outage

ResolvedOfficial update
0

Moonshot AI reports a minor service outage that degraded the K3 component. Moonshot AI reports that the incident is resolved. The outage lasted 3 minutes.

State

Resolved

Started

3 h ago

2026-11-02 15:54 UTC

Lasted

3 min

until 2026-11-02 15:57 UTC

Worst impact

Degraded

Timeline

2 updates
15:5415:5415:5515:5615:57
DegradedUpdate postedTimes in UTC

Components degraded

3 min 100%

Updates

Times in UTC

As posted by Moonshot AI

Resolved2026-11-02 15:57 UTC
Components degraded2026-11-02 15:54 UTC

Affected components

1
K3

Moonshot AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

54

Days with an incident

21

Median duration

27 min

This incident

89% 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 27 min
90 days agoToday

Other Moonshot AI incidents

All incidents

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

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

Resolvedresolved 3 h ago

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

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

Resolvedresolved 3 h ago

Moonshot AI·Minor Service Outage

The K3 component had degraded service. Moonshot AI reports that the incident is resolved. The outage lasted about 66 minutes.

Resolvedresolved 4 h ago

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

This incident has been resolved.

Resolvedresolved 1 d ago

Moonshot AI·Kimi Code K3 OTPS 响应生成速度下降

This incident has been resolved.

Resolvedresolved 1 d ago

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.cc/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.cc/feed.xml?providers=moonshot
Slack
/feed subscribe https://outages.cc/feed.xml?providers=moonshot

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane