‹ Back to status overview

AI service incident history

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

October 2026

Incidents: 30
Thursday, October 22
Project updates delayedResolved · Duration: 11 hr 2 min · Affected: API Requests, Issues, Pull Requests and 2 moreGitHub›Incident with ActionsResolved · Duration: 1 hr · Affected: ActionsGitHub›大语言模型 LLM 错误率升高Resolved · Duration: Less than 1 min · Affected: 大语言模型LLMMiniMax›Elevated errors affecting ConnectorsResolved · Duration: 4 hr 16 min · Affected: claude.ai, Claude CoworkClaude (Anthropic)›Elevated ChatGPT conversation and Responses API errorsResolved · Duration: 6 hr 32 min · Affected: ChatGPT / Conversations, APIs / ResponsesOpenAI API›Elevated ChatGPT conversation and Responses API errorsResolved · Duration: 6 hr 32 min · Affected: ChatGPT / Conversations, APIs / ResponsesOpenAI / ChatGPT›Service Degradation for Deepseek V4.1 FlashResolved · Duration: Less than 1 min · Affected: Serverless / Deepseek V4.1 FlashFireworks AI›Service Degradation for Deepseek V4.1 FlashResolved · Duration: 55 min · Affected: Serverless / Deepseek V4.1 FlashFireworks AI›Service Degradation for Deepseek V4.1 FlashResolved · Duration: 1 min · Affected: Serverless / Deepseek V4.1 FlashFireworks AI›Degraded performance for Claude Fable 5Resolved · Duration: 40 min · Affected: claude.ai, Claude API (api.anthropic.com), Claude Code and 1 moreClaude (Anthropic)›Degraded performance for Claude Fable 5Resolved · Duration: 40 min · Affected: claude.ai, Claude API (api.anthropic.com), Claude Code and 1 moreAnthropic API›Elevated errors for Bitbucket Cloud integrationsResolved · Duration: 13 min · Affected: Grok Build and Cursor: Cloud Agents, Grok Build and Cursor: Review AgentsCursor›

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