- Level
- confirmed
- Worst impact
- Operational
- Components
- singapore
- Regions
- apac
What to do
Check whether you use Stream singapore in apac. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 34m it lasted.
Anything that failed between 2025-07-30 04:47 UTC and 2025-07-30 08:21 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 2
- 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-8f7f1f980d
Is Stream still down?
No, this incident was resolved 2025-07-30 08:21 UTC. For Stream's live state, see https://down.guide/providers/stream.
How long did it last?
3h 34m, from 2025-07-30 04:47 UTC to 2025-07-30 08:21 UTC, by the times Stream posted.
What was affected?
Stream named singapore in apac.
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.