- Level
- confirmed
- Worst impact
- Degraded
- Components
- ohio, Joining Calls, Recordings, Transcriptions
- Down Index
- 15of 100
What to do
Check whether you use Stream ohio, Joining Calls, Recordings, Transcriptions. 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 9m it lasted.
Anything that failed between 2025-09-23 19:38 UTC and 2025-09-23 19:47 UTC may need a replay.Subscribe to Stream's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=stream works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Stream 3
- identified
One of our shards in the ohio region is experiencing an issue with the underlying database storage. Our team is actively working to restore the service.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-74f89e2547
Is Stream still down?
No, this incident was resolved 2025-09-23 19:47 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
9m, from 2025-09-23 19:38 UTC to 2025-09-23 19:47 UTC, by the times Stream posted.
What was affected?
Stream named ohio, Joining Calls, Recordings, Transcriptions.
What caused it?
Stream hasn't published a root cause. If it does, it shows here.
Where does this come from?
Stream's official status page, https://status.getstream.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.