rewindex

CompaniesMoonshot AI (Kimi)Monthly reportsDecember 2025

Moonshot AI (Kimi) in December 2025: incidents, uptime and changes

136incidents posted
136labelled major or critical
72.37%free of major/critical
72.37%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 8.6 days, incident time 8.6 days. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.

By vendor label: Critical 136

Major and critical incidents 136

IncidentImpactStartedDurationStatusDay
k2-thinking模型调用报错量异常Critical13 minresolved12-01
agentic模型错误报警Critical1 minresolved12-03
k2-thinking模型调用报错量异常Critical8 minresolved12-09
k2-thinking模型调用报错量异常Critical3 minresolved12-09
k2-thinking模型调用报错量异常Critical5 minresolved12-09
k2-thinking模型调用报错量异常Critical3 minresolved12-11
k2-thinking模型调用报错量异常Critical8 minresolved12-11
k2-thinking模型调用报错量异常Critical3 minresolved12-11
k2调用报错量异常Critical3 minresolved12-12
k2-thinking模型调用报错量异常Critical11 minresolved12-12
k2调用报错量异常Critical4 minresolved12-12
k2调用报错量异常Critical7 minresolved12-12
k2-thinking模型调用报错量异常Critical1 minresolved12-14
k2-thinking模型调用报错量异常Critical1 minresolved12-15
k2-thinking模型调用报错量异常Critical19 hresolved12-15
k2调用报错量异常Critical12 minresolved12-15
k2调用报错量异常Critical8.2 hresolved12-15
k2调用报错量异常Critical5 minresolved12-15
k2调用报错量异常Critical1.4 hresolved12-15
k2调用报错量异常Critical21 minresolved12-15
k2-thinking模型调用报错量异常Critical4 minresolved12-15
k2-thinking模型调用报错量异常Critical1 minresolved12-15
k2-thinking模型调用报错量异常Critical5 minresolved12-15
k2调用报错量异常Critical7 minresolved12-15
k2调用报错量异常Critical4 minresolved12-15
k2-thinking模型调用报错量异常Critical38 minresolved12-15
k2调用报错量异常Critical1 minresolved12-15
k2调用报错量异常Critical1 minresolved12-15
k2调用报错量异常Critical4 minresolved12-15
k2-thinking模型调用报错量异常Critical1 minresolved12-16
k2调用报错量异常Critical23 minresolved12-16
k2-thinking模型调用报错量异常Critical11 minresolved12-16
k2-thinking模型调用报错量异常Critical1.4 hresolved12-16
k2调用报错量异常Critical16 minresolved12-16
k2调用报错量异常Critical20 minresolved12-16
k2调用报错量异常Critical25 minresolved12-16
k2-thinking模型调用报错量异常Critical21 minresolved12-16
k2-thinking模型调用报错量异常Critical19 minresolved12-16
k2调用报错量异常Critical3 minresolved12-16
k2-thinking模型调用报错量异常Critical4 minresolved12-16
k2调用报错量异常Critical16 minresolved12-16
k2-thinking模型调用报错量异常Critical15 minresolved12-16
k2-thinking模型调用报错量异常Critical1 minresolved12-17
k2-thinking模型调用报错量异常Critical5 minresolved12-17
k2-thinking模型调用报错量异常Critical3 minresolved12-17
k2-thinking模型调用报错量异常Critical1 minresolved12-17
k2-thinking模型调用报错量异常Critical3 minresolved12-17
k2-thinking模型调用报错量异常Critical26 minresolved12-17
k2调用报错量异常Critical57 minresolved12-17
k2-thinking模型调用报错量异常Critical5 minresolved12-17
k2-thinking模型调用报错量异常Critical29 minresolved12-17
k2调用报错量异常Critical13 minresolved12-17
k2-thinking模型调用报错量异常Critical51 minresolved12-17
k2调用报错量异常Critical6 minresolved12-17
k2调用报错量异常Critical3 minresolved12-17
k2-thinking模型调用报错量异常Critical1 minresolved12-18
k2-thinking模型调用报错量异常Critical1 minresolved12-18
k2-thinking模型调用报错量异常Critical1 minresolved12-18
k2-thinking模型调用报错量异常Critical1 minresolved12-18
k2-thinking模型调用报错量异常Critical3 minresolved12-18
k2调用报错量异常Critical3 minresolved12-18
k2调用报错量异常Critical8 minresolved12-18
k2调用报错量异常Critical12 minresolved12-18
k2-thinking模型调用报错量异常Critical1 minresolved12-18
k2-thinking模型调用报错量异常Critical3 minresolved12-18
k2调用报错量异常Critical47 minresolved12-18
k2-thinking模型调用报错量异常Critical8 minresolved12-18
k2-thinking模型调用报错量异常Critical4 minresolved12-18
k2-thinking模型调用报错量异常Critical25 minresolved12-18
k2-thinking模型调用报错量异常Critical3 minresolved12-18
k2-thinking模型调用报错量异常Critical4 minresolved12-18
k2调用报错量异常Critical10 minresolved12-19
agentic模型错误报警Critical5 minresolved12-19
agentic模型错误报警Critical19 minresolved12-19
agentic模型错误报警Critical6 minresolved12-19
k2-thinking模型调用报错量异常Critical3 minresolved12-19
k2-thinking模型调用报错量异常Critical5 minresolved12-19
k2-thinking模型调用报错量异常Critical1 minresolved12-19
k2-thinking模型调用报错量异常Critical3 minresolved12-20
k2-thinking模型调用报错量异常Critical1 minresolved12-21
agentic模型错误报警Critical4 minresolved12-22
agentic模型错误报警Critical15 minresolved12-22
k2-thinking模型调用报错量异常Critical7 minresolved12-22
k2-thinking模型调用报错量异常Critical2.4 hresolved12-22
k2调用报错量异常Critical1 minresolved12-22
k2调用报错量异常Critical1.2 hresolved12-22
k2-thinking模型调用报错量异常Critical1.3 hresolved12-22
k2调用报错量异常Critical9 minresolved12-22
k2-thinking模型调用报错量异常Critical18 minresolved12-22
k2-thinking模型调用报错量异常Critical7 minresolved12-23
k2-thinking模型调用报错量异常Critical20 minresolved12-23
k2-thinking模型调用报错量异常Critical2.5 hresolved12-23
k2调用报错量异常Critical9 minresolved12-23
k2调用报错量异常Critical2 minresolved12-23
k2-thinking模型调用报错量异常Critical1.5 hresolved12-23
k2调用报错量异常Critical1 minresolved12-23
k2-thinking模型调用报错量异常Critical30 minresolved12-23
k2-thinking模型调用报错量异常Critical5 minresolved12-24
k2-thinking模型调用报错量异常Critical4 minresolved12-24
k2-thinking模型调用报错量异常Critical1.1 hresolved12-24
k2-thinking模型调用报错量异常Critical7 minresolved12-24
k2-thinking模型调用报错量异常Critical1 minresolved12-24
k2-thinking模型调用报错量异常Critical3.2 hresolved12-24
k2-thinking模型调用报错量异常Critical2.2 hresolved12-24
k2-thinking模型调用报错量异常Critical1.1 hresolved12-24
k2-thinking模型调用报错量异常Critical8 minresolved12-24
agentic模型错误报警Critical35 minresolved12-24
agentic模型错误报警Critical24 minresolved12-25
agentic模型错误报警Critical1.7 hresolved12-25
agentic模型错误报警Critical44 minresolved12-25
agentic模型错误报警Critical14 dresolved12-25
agentic模型错误报警Critical40 minresolved12-25
k2-thinking模型调用报错量异常Critical1 minresolved12-25
k2-thinking模型调用报错量异常Critical4 minresolved12-25
k2-thinking模型调用报错量异常Critical20 minresolved12-25
agentic模型错误报警Critical5 minresolved12-25
k2-thinking模型调用报错量异常Critical2 minresolved12-25
k2-thinking模型调用报错量异常Critical4 minresolved12-25
k2-thinking模型调用报错量异常Critical2.9 hresolved12-25
k2-thinking模型调用报错量异常Critical1.9 hresolved12-25
k2-thinking模型调用报错量异常Critical56 minresolved12-25
k2-thinking模型调用报错量异常Critical1 minresolved12-25
k2-thinking模型调用报错量异常Critical9 minresolved12-26
k2-thinking模型调用报错量异常Critical2 minresolved12-26
k2-thinking模型调用报错量异常Critical1.2 hresolved12-26
k2-thinking模型调用报错量异常Critical12 minresolved12-26
k2-thinking模型调用报错量异常Critical8 minresolved12-26
k2-thinking模型调用报错量异常Critical2 minresolved12-26
k2-thinking模型调用报错量异常Critical1 minresolved12-27
k2-thinking模型调用报错量异常Critical1 minresolved12-28
k2-thinking模型调用报错量异常Critical2 minresolved12-29
k2-thinking模型调用报错量异常Critical4 minresolved12-29
k2-thinking模型调用报错量异常Critical1 minresolved12-29
k2-thinking模型调用报错量异常Critical2 minresolved12-29
k2-thinking模型调用报错量异常Critical2 minresolved12-29
k2调用报错量异常Critical9 minresolved12-29

Cite this

Moonshot AI (Kimi) posted 136 status incidents in December 2025 (136 major or critical); 0 price changes and 0 notable page changes observed.

Title
Moonshot AI (Kimi) in December 2025
Vendor
Moonshot AI (Kimi)
Date
URL
https://rewindex.com/company/moonshot-ai/2025/12

All Moonshot AI (Kimi) monthsRecent incidentsMarkdown