Moonshot AI lists these components: K2.7 Code Highspeed.

When did the incident start and end?

It started at 2026-11-04 19:24 UTC and ended at 2026-11-04 19:27 UTC. It lasted 3 min.

How do I get alerts for Moonshot AI?

Subscribe to the Moonshot AI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Moonshot AI. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

Moonshot AIIncident ·

Minor Service Outage

Q: What happened?

Moonshot AI reported "Minor Service Outage" on its status page at 2026-11-04 19:24 UTC. The K2.7 Code Highspeed component does not work at full capacity. Moonshot AI reports that the incident is resolved. The outage lasted 3 minutes.

ResolvedOfficial update

The K2.7 Code Highspeed component does not work at full capacity. Moonshot AI reports that the incident is resolved. The outage lasted 3 minutes.

State

Resolved

Started

Lasted

3 min

Worst impact

Degraded

Timeline

2 updates

19:2419:2519:2519:2619:27

DegradedUpdate postedTimes in UTC

Components degraded

3 min 100%

Updates

Times in UTC

As posted by Moonshot AI

Resolved

Components degraded

Affected components

K2.7 Code Highspeed

Moonshot AI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

22 min

This incident

86% 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 fs服务异常

Moonshot AI reports that file uploads failed for Kimi. The provider investigated a high failure rate for kimi fs requests. The incident is resolved and lasted 2 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that the K3 component had degraded performance. Moonshot AI resolved the incident after 12 minutes.

Resolved

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

Moonshot AI reports that some K3 requests had higher TTFT latency. This affected K3 and Kimi Code - K3. Moonshot AI reports that the incident is resolved. It lasted 10 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports degraded service on the K3 component. Moonshot AI says the incident is resolved. The outage lasted 90 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reported degraded service on the K3 component. Moonshot AI later reported that the issue is resolved. The outage lasted 3 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