- Level
- confirmed
- Worst impact
- Major outage
- Components
- Personalization
- Down Index
- 45of 100
What to do
Check whether you use Stream Personalization. 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 6h 28m it lasted.
Anything that failed between 2021-01-04 16:57 UTC and 2021-01-04 23:25 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 4
- investigating
We are currently investigating an issue with AWS SQS, we are receiving 100% error rate from SQS APIs. Our feeds realtime endpoint is currently unable to push notifications to SQS.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
Millions of requests to the handshake endpoint of our feed realtime system broke the API. This issue has been resolved and a full post mortem will follow.
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-d61ba4c94c
Is Stream still down?
No, this incident was resolved 2021-01-04 23:25 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
6h 28m, from 2021-01-04 16:57 UTC to 2021-01-04 23:25 UTC, by the times Stream posted.
What was affected?
Stream named Personalization.
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.