- Level
- confirmed
- Worst impact
- Degraded
- Components
- Conversations
- Down Index
- 23of 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 8h 39m it lasted.
Anything that failed between 2026-08-13 15:19 UTC and 2026-08-13 23:58 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 5
- investigating
We are investigating the issue for the listed services.
provider
- identified
We are still implementing the mitigation.
provider
- monitoring
We have applied the mitigation and are monitoring the recovery.
provider
- monitoring
We’ve applied a mitigation and are monitoring recovery following an issue with a downstream provider.
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-328d65dff8
Is OpenAI still down?
No, this incident was resolved 2026-08-13 23:58 UTC. For OpenAI's live state, see https://down.guide/openai.
How long did it last?
8h 39m, from 2026-08-13 15:19 UTC to 2026-08-13 23:58 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.