- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Stream. 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 44m it lasted.
Anything that failed between 2018-03-14 15:07 UTC and 2018-03-14 15:51 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're currently investigating problems with loading the Dashboard.
provider
- monitoring
The CDN (IMGIX) is not serving static files from our origin correctly (https://status.imgix.com/incidents/5plz9dqxxhns). We have temporarily mitigated the problem by rolling back to a previous release (the statics for that release are available at CDN edge nodes and are returned correctly). We are now working to switch to the backup CDN (AWS Cloudfront).
provider
- resolved
We switched to our back-up CDN a few minutes ago. Dashboard is fully operation again.
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-5734862e4d
Is Stream still down?
No, this incident was resolved 2018-03-14 15:51 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
44m, from 2018-03-14 15:07 UTC to 2018-03-14 15:51 UTC, by the times Stream posted.
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.