‹ Back to status overview

AI service incident history

Official incidents for AI platforms and APIs over the last 90 days. 928 records include timing, duration, affected components, and vendor updates.

September 2026

Incidents: 30
Wednesday, September 2
[Review Agents] Investigating service degradation — Automations, Cloud Agents, Review AgentsResolved · Duration: Less than 1 minCursor›[Grok Build and Cursor: Review Agents] Investigating service degradation — Automations, Cloud Agents, Review AgentsResolved · Duration: 1 hr 20 minxAI / Grok›开放平台 API 服务异常Resolved · Duration: 22 min · Affected: Open APIMoonshot API›DeepSeek 网页/API 部分中断(DeepSeek Web/API partially unavailable)Resolved · Duration: 31 min · Affected: DeepSeek V4 Pro API服务(API Service), DeepSeek V4.1 Flash API服务(API Service), 对话服务(Chatservice)DeepSeek API›DeepSeek 网页/API 部分中断(DeepSeek Web/API partially unavailable)Resolved · Duration: 31 min · Affected: DeepSeek V4 Pro API服务(API Service), DeepSeek V4.1 Flash API服务(API Service), 对话服务(Chatservice)DeepSeek›[Cursor IDE (iOS)] Investigating service degradationResolved · Duration: Less than 1 minCursor›[Grok Build and Cursor: iOS] Investigating service degradationResolved · Duration: 2 hr 19 minxAI / Grok›Service Degradation for GLM 5.3 FlashResolved · Duration: 14 min · Affected: Serverless / GLM 5.3 FlashFireworks AI›Service Degradation for GLM 5.3 FlashResolved · Duration: 5 hr 37 min · Affected: Serverless / GLM 5.3 FlashFireworks AI›Degraded performance on platform.claude.com and Claude for Microsoft Office 365Resolved · Duration: 1 hr 1 min · Affected: claude.ai, Claude Console (platform.claude.com)Claude (Anthropic)›[Grok Bot] Degraded performance of Grok 4.5Resolved · Duration: Less than 1 minCursor›[Grok Bot] Degraded performance of Grok 4.5Resolved · Duration: 1 hr 58 minxAI / Grok›Degraded performance on Claude for Microsoft Office 365Resolved · Duration: 19 min · Affected: claude.aiClaude (Anthropic)›

About this data

Where does the incident data for AI services come from?

Data comes from official vendor status pages, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview