Widespread feature degradation
A record of the OpenAI incident on October 15, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
1 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.
- GitHubCCA Automations are delayed when starting an Automation
Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.
How big was this outage?
This outage lasted 147 minutes. Across 23 major incidents recorded for OpenAI, the median duration is 81 minutes, making this the 8th longest.
Longer than a typical outage.
Only incidents recorded as major-or-worse and already resolved are counted.
Current status
OpenAI is operating normally now. This incident has been resolved.
See current OpenAI status →What you can do during an outage
Source: OpenAI's official status page.
Other OpenAI incidents
- Delayed Costs data in the Compliance APIOctober 14, 2026
- Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburstOctober 14, 2026
- Degraded performance in Codex and ChatGPT WorkOctober 14, 2026
- Degraded performance in GPT-6.1 Sol Codex and Work modeOctober 13, 2026
- Workspace admins may be unable to manage pluginsOctober 9, 2026