‹ 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
Wednesday, October 21
Investigating service degradationResolved · Duration: 1 hr 54 min · Affected: Grok Build and Cursor: cursor.com, Grok BotCursor›[Grok Bot] Investigating service degradationResolved · Duration: 1 hr 54 minxAI / Grok›Elevated error rates for gpt-5.6-luna API requestsResolved · Duration: 1 hr 9 min · Affected: APIs / Responses, APIs / Chat CompletionsOpenAI API›Delays for Pull Requests and Webhook deliveriesResolved · Duration: 4 hr 30 min · Affected: Webhooks, Pull Requests, ActionsGitHub›Elevated FedRAMP API error rates for Astra and SolResolved · Duration: 3 hr 13 min · Affected: FedRAMP / FedRAMPOpenAI API›Investigating service degradationResolved · Duration: Less than 1 min · Affected: Third-party Model ProvidersCursor›Service Degradation for DeepSeek V4.1 Flash 1017Resolved · Duration: 1 hr 1 min · Affected: Serverless / DeepSeek V4.1 Flash 1017Fireworks AI›Service Degradation for Deepseek V4.1 FlashResolved · Duration: 29 min · Affected: Serverless / Deepseek V4.1 FlashFireworks AI›Kimi Code K3 TTFT 响应延迟升高Resolved · Duration: 8 min · Affected: K3Kimi / Moonshot›Degraded performance in ChatGPT, Codex, and APIsResolved · Duration: 21 min · Affected: APIs / Moderations, APIs / Decisions, ChatGPT / Compliance API and 30 moreOpenAI / ChatGPT›Degraded performance in ChatGPT, Codex, and APIsResolved · Duration: 21 min · Affected: APIs / Moderations, APIs / Decisions, ChatGPT / Compliance API and 30 moreOpenAI API›Service Degradation for GLM 5.3 FlashResolved · Duration: 6 min · Affected: Serverless / GLM 5.3 FlashFireworks AI›Service Degradation for GLM 5.3Resolved · Duration: 10 min · Affected: Serverless / GLM 5.3 Fireworks AI›Service Degradation for Deepseek V4.1 FlashResolved · Duration: 32 min · Affected: Serverless / Deepseek V4.1 FlashFireworks AI›Service Degradation for Kimi K3Resolved · Duration: 27 min · Affected: Serverless / Kimi K3Fireworks AI›Authentication errors for some usersResolved · Duration: 1 hr · Affected: APIs / Login, Codex / Codex API, Codex / CLI and 3 moreOpenAI API›Authentication errors for some usersResolved · Duration: 1 hr · Affected: APIs / Login, Codex / Codex API, Codex / CLI and 3 moreOpenAI / ChatGPT›

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