- Level
- confirmed
- Worst impact
- Degraded
- Components
- Personalization
- Down Index
- 9of 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 0m it lasted.
Anything that failed between 2018-08-08 01:09 UTC and 2018-08-08 01:09 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 1
- resolved
Our distributed realtime cluster uses Redis (on Elasticache) for state management. A failover of the Elasticache cluster caused realtime to be unavailable for 7 minutes. This issue has been resolved and we're investigating why the failover took 7 minutes. This impacted customers using Stream's websocket, SQS or Webhook firehose systems.
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-fca125622a
Is Stream still down?
No, this incident was resolved 2018-08-08 01:09 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
0m, from 2018-08-08 01:09 UTC to 2018-08-08 01:09 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.