- Level
- confirmed
- Worst impact
- Operational
- Stream says
- 2025-03-31 12:35 to 12:51 UTC (16m)
- Components
- Joining Calls
- Regions
- apac
What to do
Check whether you use Stream Joining Calls 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 4h 9m it lasted.
Anything that failed between 2025-03-31 13:39 UTC and 2025-03-31 17:48 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
Between 12:35 and 12:51 UTC, our API layer experienced a downtime in the Mumbai region due to increased system load. We are currently investigating the incident and implementing a patch. During this time API requests to join calls returned a 5xx response.
provider
- resolved
Our team deployed a patch to the affected system and the 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-78da14a06e
Is Stream still down?
No, this incident was resolved 2025-03-31 17:48 UTC. For Stream's live state, see https://down.guide/providers/stream.
How long did it last?
4h 9m, from 2025-03-31 13:39 UTC to 2025-03-31 17:48 UTC, by the times Stream posted.
What was affected?
Stream named Joining Calls 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.