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
Score Breakdown
Uptime50%
52.5
Frequency20%
76.5
Severity20%
0.5
MTTR10%
85.8
SLA Compliance
How often does this provider clear their stated availability target?
Industry default (99.9%) · 99.90%
✕ last 90d98.51%-1.39%
Met SLA in 3 of 13 weeks (23%)
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 90d
MinorMajorCritical
Total 67 incidents
0
6
12
18
24
07-2108-0208-1408-2609-0709-1910-0110-13
Worst Incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
Type of Failure
Categorised from the public incident headlines (outage / latency / auth / etc.).
Other
67
100%
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
S
Sunday19:00–20:00 UTC
1incident
1 critical
搜索请求出现大量报错Sep 13
1
M
Monday11:00–12:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 3
Monday12:00–13:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 3
Monday13:00–14:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 3
Monday14:00–15:00 UTC
2incidents
2 critical
开放平台 API 服务异常Aug 31
搜索请求出现大量报错Aug 3
Monday15:00–16:00 UTC
4incidents
4 critical
开放平台 API 服务异常Aug 31
开放平台 API 服务异常Aug 31
搜索请求出现大量报错Aug 3
+ 1 more
Monday19:00–20:00 UTC
1incident
1 critical
二维码登录异常Aug 10
Monday20:00–21:00 UTC
1incident
1 critical
二维码登录异常Aug 10
Monday21:00–22:00 UTC
1incident
1 critical
二维码登录异常Aug 10
Monday22:00–23:00 UTC
1incident
1 critical
二维码登录异常Aug 10
Monday23:00–00:00 UTC
2incidents
2 critical
kimi fs服务异常Sep 28
二维码登录异常Aug 10
15
T
Tuesday18:00–19:00 UTC
1incident
1 critical
二维码登录异常Aug 11
Tuesday19:00–20:00 UTC
1incident
1 critical
二维码登录异常Aug 11
2
W
Wednesday06:00–07:00 UTC
2incidents
2 critical
搜索请求出现大量报错Sep 9
搜索请求出现大量报错Sep 9
Wednesday08:00–09:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday09:00–10:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday10:00–11:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday11:00–12:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday12:00–13:00 UTC
2incidents
2 critical
开放平台 API 服务异常Sep 2
搜索请求出现大量报错Aug 12
Wednesday13:00–14:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday14:00–15:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday15:00–16:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday16:00–17:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday17:00–18:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday18:00–19:00 UTC
3incidents
3 critical
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
Wednesday19:00–20:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday20:00–21:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 12
Wednesday21:00–22:00 UTC
4incidents
4 critical
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
+ 1 more
Wednesday22:00–23:00 UTC
4incidents
4 critical
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Aug 12
+ 1 more
Wednesday23:00–00:00 UTC
2incidents
2 critical
搜索请求出现大量报错Aug 12
搜索请求出现大量报错Jul 22
28
T
Thursday00:00–01:00 UTC
2incidents
2 critical
搜索请求出现大量报错Aug 13
搜索请求出现大量报错Jul 23
Thursday01:00–02:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 13
Thursday02:00–03:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 13
Thursday03:00–04:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 13
Thursday04:00–05:00 UTC
1incident
1 critical
搜索请求出现大量报错Aug 13
Thursday05:00–06:00 UTC
1incident
1 critical
kimi fs服务异常Oct 1
Thursday08:00–09:00 UTC
1incident
1 critical
搜索请求出现大量报错Jul 30
Thursday11:00–12:00 UTC
5incidents
5 critical
搜索请求出现大量报错Sep 10
搜索请求出现大量报错Sep 10
搜索请求出现大量报错Sep 10
+ 2 more
Thursday17:00–18:00 UTC
1incident
1 critical
搜索请求出现大量报错Oct 1
Thursday21:00–22:00 UTC
1incident
1 critical
搜索请求出现大量报错Sep 10
15
F
Friday00:00–01:00 UTC
1incident
1 critical
搜索请求出现大量报错Oct 9
Friday22:00–23:00 UTC
3incidents
3 critical
搜索请求出现大量报错Oct 2
搜索请求出现大量报错Oct 2
搜索请求出现大量报错Oct 2
4
S
Saturday07:00–08:00 UTC
1incident
1 critical
搜索请求出现大量报错Sep 12
Saturday10:00–11:00 UTC
1incident
1 critical
搜索请求出现大量报错Sep 19
2
00
06
12
18
HOUR OF DAY · UTC67 incident starts · hover any cell for detail
Hottest hour
Thursday 11:00 5
Worst day
Wednesday 28
Worst time of day
22:00–23:00 8
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
17m
half of incidents resolve faster
On a bad day
4h 49m
9 in 10 resolve faster than this
Distribution
<15m
31
15m–1h
13
1–4h
13
4–24h
10
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.