- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-east, us-east
- Regions
- us
- Down Index
- 22of 100
What to do
Check whether you use Stream us-east, 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 1h 34m it lasted.
Anything that failed between 2020-07-28 10:37 UTC and 2020-07-28 12:12 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
- identified
Due to a networking issue on AWS us-east region, we are experiencing increased latency for some of the traffic on our US region. We are mitigating the problem while waiting for a final remediation on AWS infrastructure.
provider
- resolved
AWS Networking issue is now resolved. We are now cleaning up our temporary remediations since they are not needed anymore. Traffic is back to normal for the last hour.
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-54b19b995b
Is Stream still down?
No, this incident was resolved 2020-07-28 12:12 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
1h 34m, from 2020-07-28 10:37 UTC to 2020-07-28 12:12 UTC, by the times Stream posted.
What was affected?
Stream named us-east, 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.