- Level
- confirmed
- Worst impact
- Degraded
- Components
- Conversations
- Down Index
- 18of 100
What to do
Check whether you use OpenAI Conversations. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 48m it lasted.
Anything that failed between 2026-08-10 07:21 UTC and 2026-08-10 08:09 UTC may need a replay.Subscribe to OpenAI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=openai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from OpenAI 3
- identified
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
provider
- monitoring
We have applied the mitigation and are monitoring the recovery.
provider
- resolved
All impacted services have now fully recovered.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b88a62cb7c
Is OpenAI still down?
No, this incident was resolved 2026-08-10 08:09 UTC. For OpenAI's live state, see https://down.guide/openai.
How long did it last?
48m, from 2026-08-10 07:21 UTC to 2026-08-10 08:09 UTC, by the times OpenAI posted.
What was affected?
OpenAI named Conversations.
What caused it?
OpenAI hasn't published a root cause. If it does, it shows here.
Where does this come from?
OpenAI's official status page, https://status.openai.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.