短信登录异常
Moonshot AI reports that SMS login does not work for Sign In / Sign Up and Kimi - Sign In / Sign Up. Moonshot AI resolved the incident. The outage lasted 11 minutes.
State
Resolved
Started
Lasted
11 min
Worst impact
Major outage
Timeline
2 updatesInvestigating
11 min 100%
Updates
Times in UTCAs posted by Moonshot AI
This incident has been resolved.
短信登录活跃度过低
Affected components
2Moonshot AI in the last 90 days
Full historyIncidents in 90 days
73
Days with an incident
27
Median duration
13 min
This incident
15% shorter than the median
Other Moonshot AI incidents
All incidentsMoonshot AI·Minor Service Outage
Moonshot AI reports that the K3 component does not work correctly. The status is degraded. Moonshot AI continues to investigate this incident, which started at 23:30 UTC.
Moonshot AI·Minor Service Outage
Moonshot AI reports degraded service on the K3 component. Moonshot AI states that this outage is resolved. The outage lasted 24 hours and 12 minutes.
Moonshot AI·Minor Service Outage
Moonshot AI reports a service outage that degraded the K3 component. Moonshot AI reports that the outage is resolved. The outage lasted 30 hours and 27 minutes.
Moonshot AI·Kimi Code K2.8 Preview TTFT 响应延迟升高
Moonshot AI reports that time to first token (TTFT) latency increased for some requests on K2.8 Preview and Kimi Code K2.8 Preview. Moonshot AI investigated the issue. The incident is resolved and lasted 13 minutes.
Moonshot AI·Minor Service Outage
Moonshot AI reports that the K2.8 Preview component had degraded service. Moonshot AI says the incident is resolved. The outage lasted 39 minutes.
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.
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.
https://outages.live/feed.xml?providers=moonshot/feed subscribe https://outages.live/feed.xml?providers=moonshotFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane