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

Kimi Code K3 TTFT 响应延迟升高

ResolvedOfficial update
0

Moonshot AI reports that the time to first token increased for some requests on the K3 component and Kimi Code - K3. Moonshot AI resolved the incident after 22 minutes.

State

Resolved

Started

2 h ago

2026-11-02 15:30 UTC

Lasted

22 min

until 2026-11-02 15:52 UTC

Worst impact

Major outage

Timeline

2 updates
15:3015:3615:4115:4715:52
Major outageUpdate postedTimes in UTC

Investigating

22 min 100%

Updates

Times in UTC

As posted by Moonshot AI

Resolved2026-11-02 15:52 UTC

This incident has been resolved.

Investigating2026-11-02 15:33 UTC

K3 部分请求的 TTFT 延迟可能升高

Affected components

2
K3Kimi Code - 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

18% 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·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.

Resolvedresolved 1 h ago

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

Moonshot AI reports higher TTFT latency for some requests on the K3 component and the Kimi Code - K3 component. The incident is resolved. It lasted 82 minutes.

Resolvedresolved 1 h ago

Moonshot AI·Minor Service Outage

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

Resolvedresolved 3 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.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