Rewindex

CompaniesMoonshot AI (Kimi)Incidents

Moonshot AI (Kimi): 搜索请求出现大量报错

CriticalStatus: resolvedStarted Resolved (1 min)1 updatestatus.moonshot.cn (opens in new tab)
Part of an outage event

Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents

Moonshot AI (Kimi)’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted −40 min vs the first vendor naming Azure)

Swipe sideways to see the whole diagram.

same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstackMoonshot AI (Kimi) (this incident)posted −40 min
same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstackMoonshot AI (Kimi) (thisincident)posted −40 min
Moonshot AI (Kimi) is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure west us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed Azure<br/>JFrog, Optimizely"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Azure<br/>Wiz, Sumo Logic"]:::blames
  root --> h4
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["Moonshot AI (Kimi) (this incident)<br/>posted −40 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    This incident has been resolved.

From Moonshot AI (Kimi)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.moonshot.cn (opens in new tab).

Moonshot AI (Kimi) profileRecent Moonshot AI (Kimi) incidentsMarkdownJSON