Stream: Data retrieval issue in US-East

What to do

Check whether you use Stream us-east in us. 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 4h 9m it lasted.
Anything that failed between 2026-08-05 17:05 UTC and 2026-08-05 21:14 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.

investigatingAug 5, 2026, 5:05 PM UTC
We are aware of an issue affecting data retrieval for a subset of Chat customers located in the US-East region. Affected customers may see errors or empty results when retrieving messages from channels. Our engineering team is investigating.
provider
identifiedAug 5, 2026, 9:08 PM UTC
The issue has been identified, and our engineering team is working to restore the data to its original state.
provider
resolvedAug 5, 2026, 9:14 PM UTC
The incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Stream still down?

No, this incident was resolved 2026-08-05 21:14 UTC. For Stream's live state, see https://down.guide/stream.

How long did it last?

4h 9m, from 2026-08-05 17:05 UTC to 2026-08-05 21:14 UTC, by the times Stream posted.

What was affected?

Stream named us-east in us.

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.