rewindex

ChangesMoonshot AI (Kimi)Kimi Code K3 TTFT 响应延迟升高

Moonshot AI (Kimi): Critical incident: Kimi Code K3 TTFT 响应延迟升高

Major incidentdegradation (model (Jev), 100%)Changed Detected status.moonshot.cn (opens in new tab)
Summary

Moonshot AI reported elevated time-to-first-token (TTFT) latency for some K3 requests, affecting K3 and Kimi Code - K3, with critical impact. The incident started at 2026-10-28 09:06 UTC and remained open and under investigation when archived, open for 0 min at the last update.

Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.

Incident page: the full timeline of updates

What changed

Struck in red is what Moonshot AI (Kimi) removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Kimi Code K3 TTFT 响应延迟升高
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: investigating
AddedStart time#4
Before: not present
After: 2026-10-28 09:06 UTC
AddedAffected components#5
Before: not present
After: K3, Kimi Code - K3
AddedUpdateinvestigating#6
Before: not present
After: K3 部分请求的 TTFT 延迟可能升高

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

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

History of this incident

Wednesday, October 28

2 incident changes

Cite this

Critical incident: Kimi Code K3 TTFT 响应延迟升高 on Moonshot AI (Kimi)’s status page, changed 2026-10-28 09:06 UTC (change 1 of 2).

Title
Critical incident: Kimi Code K3 TTFT 响应延迟升高
Vendor
Moonshot AI (Kimi)
Date
URL
https://rewindex.com/change/i4c79544ce38038

All Moonshot AI (Kimi) changesMoonshot AI (Kimi) profileMarkdownJSON