- Level
- confirmed
- Worst impact
- Partial outage
- Components
- us-east
- Regions
- us
- Down Index
- 31of 100
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 47m it lasted.
Anything that failed between 2024-05-09 13:51 UTC and 2024-05-09 14:38 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
- investigating
We are currently experiencing a high error rate on one of our Feed shards in the us-east region. Our team is actively working to resolve the situation.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
The shard has been recovered and the incident has been resolved. Our team is currently conducting an internal investigation to determine the root cause of the issue.
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-d67f4fdacf
Is Stream still down?
No, this incident was resolved 2024-05-09 14:38 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
47m, from 2024-05-09 13:51 UTC to 2024-05-09 14:38 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.