Stream: Elevated API Errors

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 0m it lasted.
Anything that failed between 2018-02-03 18:46 UTC and 2018-02-03 18:46 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.

resolvedFeb 3, 2018, 6:46 PM UTC
A small part of Stream's customers was impacted by an issue that caused notification feeds to be temporarily unavailable. Earlier today at 15:30 GMT a maintenance database migration was initiated; unfortunately the procedure did not clear the cached state of feeds correctly. This lead to reads not showing activities from before that time. At 16:00 UTC we remediated by flushing the stale cache which immediately fixed the problem. The issue did not affect any write operations such as adding/removing activities or following/unfollowing feeds. After some investigation we could find and amended the incorrect part of the maintenance operation. Apologies for the trouble and for bringing this up during the week-end.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Stream still down?

No, this incident was resolved 2018-02-03 18:46 UTC. For Stream's live state, see https://down.guide/stream.

How long did it last?

0m, from 2018-02-03 18:46 UTC to 2018-02-03 18:46 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.