7 major incidents detected for Moonshot AI (Kimi). View live status dashboard →
On 2026-08-12 at 10:15 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 28h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-08-10 at 20:45 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 23h 45m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-08-05 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 6h 15m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-08-02 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-07-30 at 04:15 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 70h 45m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-07-27 at 17:30 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 57h 31m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.
On 2026-07-10 at 20:15 UTC, DownForAI monitoring detected a significant service issue affecting Moonshot AI (Kimi). The incident has been resolved after approximately 33h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.