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%
60.0
Frequency20%
68.5
Severity20%
14.6
MTTR10%
97.5
SLA Compliance
How often does this provider clear their stated availability target?
Industry default (99.9%) · 99.90%
✕ last 60d99.17%-0.73%
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 60d
MinorMajorCritical
Total 68 incidents
0
3
6
9
12
03-1003-1803-2604-0304-1104-1904-2705-05
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
68
100%
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
S
Sunday07:00–08:00 UTC
2incidents
2 critical
deep research workflow错误率异常Apr 19
deep research workflow错误率异常Apr 19
2
M
Monday01:00–02:00 UTC
3incidents
3 critical
API 服务可用性低Apr 20
API 服务可用性低Apr 20
API 服务可用性低Apr 20
Monday03:00–04:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 20
Monday06:00–07:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 20
Monday07:00–08:00 UTC
2incidents
2 critical
搜索请求出现大量报错Apr 20
搜索请求出现大量报错Apr 20
Monday08:00–09:00 UTC
5incidents
5 critical
搜索请求出现大量报错Apr 20
搜索请求出现大量报错Apr 20
搜索请求出现大量报错Apr 20
+ 2 more
Monday09:00–10:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 20
Monday11:00–12:00 UTC
1incident
1 critical
agentic模型错误报警Mar 9
Monday12:00–13:00 UTC
1incident
1 critical
agentic模型错误报警Mar 9
Monday13:00–14:00 UTC
1incident
1 critical
agentic模型错误报警Mar 9
Monday14:00–15:00 UTC
1incident
1 critical
agentic模型错误报警Mar 9
17
T
Tuesday04:00–05:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 21
Tuesday08:00–09:00 UTC
1incident
1 critical
agentic模型错误报警Apr 21
Tuesday09:00–10:00 UTC
1incident
1 critical
agentic模型错误报警Apr 21
Tuesday12:00–13:00 UTC
2incidents
2 critical
agentic模型错误报警Mar 17
agentic模型错误报警Mar 17
Tuesday13:00–14:00 UTC
2incidents
2 critical
agentic模型错误报警Mar 17
agentic模型错误报警Mar 17
Tuesday15:00–16:00 UTC
3incidents
3 critical
deep research workflow错误率异常Apr 14
deep research workflow错误率异常Apr 14
deep research workflow错误率异常Apr 14
Tuesday16:00–17:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 14
11
W
Wednesday06:00–07:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 15
Wednesday07:00–08:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 15
Wednesday09:00–10:00 UTC
3incidents
3 critical
deep research workflow错误率异常Apr 15
deep research workflow错误率异常Apr 15
deep research workflow错误率异常Apr 15
Wednesday10:00–11:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 15
6
T
Thursday01:00–02:00 UTC
2incidents
2 critical
搜索功能报错Apr 23
搜索功能报错Apr 23
Thursday02:00–03:00 UTC
3incidents
3 critical
搜索功能报错Apr 23
搜索功能报错Apr 23
搜索功能报错Apr 23
Thursday03:00–04:00 UTC
4incidents
4 critical
搜索功能报错Apr 23
搜索功能报错Apr 23
搜索功能报错Apr 23
+ 1 more
Thursday04:00–05:00 UTC
1incident
1 critical
搜索功能报错Apr 23
Thursday05:00–06:00 UTC
1incident
1 critical
搜索功能报错Apr 23
Thursday06:00–07:00 UTC
1incident
1 critical
搜索功能报错Apr 23
Thursday07:00–08:00 UTC
1incident
1 critical
搜索功能报错Apr 23
Thursday16:00–17:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 16
Thursday18:00–19:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 30
15
F
Friday04:00–05:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 10
Friday06:00–07:00 UTC
1incident
1 critical
搜索请求出现大量报错May 1
Friday07:00–08:00 UTC
1incident
1 critical
搜索请求出现大量报错May 1
Friday14:00–15:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 17
Friday15:00–16:00 UTC
2incidents
2 critical
deep research workflow错误率异常Apr 17
deep research workflow错误率异常Apr 17
Friday17:00–18:00 UTC
3incidents
3 critical
deep research workflow错误率异常Apr 17
deep research workflow错误率异常Apr 17
deep research workflow错误率异常Apr 17
9
S
Saturday01:00–02:00 UTC
1incident
1 critical
搜索请求出现大量报错Apr 18
Saturday08:00–09:00 UTC
2incidents
2 critical
deep research workflow错误率异常Apr 18
deep research workflow错误率异常Apr 18
Saturday09:00–10:00 UTC
2incidents
2 critical
deep research workflow错误率异常Apr 18
deep research workflow错误率异常Apr 18
Saturday10:00–11:00 UTC
2incidents
2 critical
deep research workflow错误率异常Apr 18
deep research workflow错误率异常Apr 18
Saturday12:00–13:00 UTC
1incident
1 critical
deep research workflow错误率异常Apr 18
8
00
06
12
18
HOUR OF DAY · UTC68 incident starts · hover any cell for detail
Hottest hour
Monday 08:00 5
Worst day
Monday 17
Worst time of day
08:00–09: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
3m
half of incidents resolve faster
On a bad day
1h 36m
9 in 10 resolve faster than this
Distribution
<15m
58
15m–1h
3
1–4h
6
4–24h
1
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.