Kimi Code K3 TTFT 响应延迟升高
ResolvedOfficial update
0
Moonshot AI reports that some requests to K3 and Kimi Code - K3 had higher TTFT latency. The incident is resolved and lasted 22 minutes.
State
Resolved
Started
1 h ago
2026-11-02 15:30 UTC
Lasted
22 min
until 2026-11-02 15:52 UTC
Worst impact
Major outage
Timeline
2 updates15:3015:3615:4115:4715:52
Major outageUpdate postedTimes in UTC
Investigating
22 min 100%
Updates
Times in UTCAs 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
2K3Kimi Code - K3
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=moonshotSlack
/feed subscribe https://outages.cc/feed.xml?providers=moonshotFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane