Chinese AI lab founded by Yang Zhilin (ex-Meta / Tsinghua / Recurrent AI). Builds Kimi, a long-context assistant pitched on multi-hundred-thousand-token windows and strong Chinese-language performance. Distributes through kimi.com (chat) and platform.moonshot.cn (API).
Components ranked by incident count. Click a row for the incident list. Down-time is attributed proportionally for multi-component incidents.
Component
Incidents
Down (attr.)
Median MTTR
Last
No incidents touched any Kimi component in this window.
Score Breakdown
Uptime50%
100.0
Frequency20%
100.0
Severity20%
100.0
MTTR10%
100.0
SLA Compliance
How often does this provider clear their stated availability target?
Industry default (99.9%) · 99.90%
✓ right now (last 1 minute)100.00%+0.10%
Met SLA in 10 of 13 weeks (77%)
13 weeks on record
Method: a rolling quarter (13 weeks ≈ 91 days). Each cell is one 7-day slice of Statuspage-standard uptime (1 − (critical + 0.3 × major) / window; minors and maintenance excluded; red when the slice dips below the stated SLA).
Kimi — Incidents by Day last 30d
MinorMajorCritical
Total 0 incidents
0
0
1
1
1
04-0704-1104-1504-1904-2304-2705-0105-05
Worst Incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
No notable incidents in this window.
Type of Failure
Categorised from the public incident headlines (outage / latency / auth / etc.).
No incidents to categorise in this window.
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
No incidents to plot in this window.
How fast they fix things
Distribution of resolution times alongside the 12-week trend so you can see whether they're getting faster or slower.
Typical fix
—
half of incidents resolve faster
On a bad day
—
9 in 10 resolve faster than this
Distribution
<15m
0
15m–1h
0
1–4h
0
4–24h
0
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.