- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Personalization
- Down Index
- 34of 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 10h 35m it lasted.
Anything that failed between 2021-01-06 05:00 UTC and 2021-01-06 15:35 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
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
Realtime updates for feeds are back to normal, we are still monitoring the traffic. The previous patch unfortunately did not resolve the problem and was causing realtime clients to retry the connection via the `Client not found, please reconnect` response.
provider
- resolved
This 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-a67ffa2251
Is Stream still down?
No, this incident was resolved 2021-01-06 15:35 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
10h 35m, from 2021-01-06 05:00 UTC to 2021-01-06 15:35 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.