outages.live
Live
Moonshot AIIncident ·

Kimi Code K3 TTFT 响应延迟升高

Major outageOfficial update
0

Kimi Code K3 has slow time to first token (TTFT) on some requests. The K3 components are affected. Moonshot AI reports that it is investigating the problem.

State

Investigating

Started

Ongoing for

12 min

Worst impact

Major outage

Timeline

3 updates
08:5809:0109:0409:0709:10
Major outageNoticeUpdate postedTimes in UTC

Investigating

9 min 75%

Resolved

3 min 25%

Updates

Times in UTC

As posted by Moonshot AI

Investigating

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

Resolved
Investigating

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

Affected components

2
K3Kimi Code - K3

Moonshot AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

63

Days with an incident

23

Median duration

25 min

This incident

52% 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 25 min
90 days agoToday

Other Moonshot AI incidents

All incidents

Moonshot AI·Minor Service Outage

Moonshot AI reports that K3 had degraded service. Moonshot AI says the outage is resolved. The outage lasted 3 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that the K3 component had degraded performance. Moonshot AI reports that the outage is resolved. The outage lasted 60 minutes.

Resolved

Moonshot AI·Minor Service Outage

Moonshot AI reports that K2.7 Code Highspeed did not work correctly. The problem is resolved. It lasted 27 minutes.

Resolved

Moonshot AI·Minor Service Outage

K2.7 Code Highspeed had degraded service. Moonshot AI reports that the outage is resolved. It lasted 3 minutes.

Resolved

Moonshot AI·kimi fs服务异常

Moonshot AI reports that Kimi file uploads did not work. The provider investigated a high failure rate for kimi fs requests. Moonshot AI resolved the incident after 2 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.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