Moonshot AI lists these components: Open API.

When did the incident start and end?

It started at 2026-11-09 12:33 UTC and ended at 2026-11-09 12:39 UTC. It lasted 6 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 ·

Partial System Outage

Q: What happened?

Moonshot AI reported "Partial System Outage" on its status page at 2026-11-09 12:33 UTC. Moonshot AI reports a partial outage that affects the Open API. Moonshot AI states that the incident is resolved. The outage lasted 6 minutes.

ResolvedOfficial update

Moonshot AI reports a partial outage that affects the Open API. Moonshot AI states that the incident is resolved. The outage lasted 6 minutes.

State

Resolved

Started

Lasted

6 min

Worst impact

Partial outage

Timeline

2 updates

12:3312:3412:3612:3712:39

Partial outageUpdate postedTimes in UTC

Components degraded

6 min 100%

Updates

Times in UTC

As posted by Moonshot AI

Resolved

Components degraded

Affected components

Open API

Moonshot AI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

18 min

This incident

67% 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 18 min

90 days agoToday

Other Moonshot AI incidents

All incidents

Moonshot AI·Kimi Code K2.8 Preview TTFT 响应延迟升高

Kimi Code K2.8 Preview responses had higher TTFT latency for some requests. Moonshot AI reported the incident as resolved. The incident lasted about 13 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that the K2.8 Preview component had degraded performance. Moonshot AI reports that the incident is resolved. The incident lasted 42 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports a minor service outage. The K2.8 Preview component was degraded. The incident is resolved and lasted 18 minutes.

Resolved

Moonshot AI·搜索请求出现大量报错

This incident has been resolved.

Resolved

Moonshot AI·搜索请求出现大量报错

Moonshot AI reports that search requests fail on the Search and Kimi - Search components. Moonshot AI investigated the errors. The incident is resolved and 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