- Level
- confirmed
- Worst impact
- Degraded
- Components
- ohio
- Down Index
- 9of 100
What to do
Check whether you use Stream ohio. 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 2024-05-29 01:06 UTC and 2024-05-29 01:07 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 2
- investigating
Our monitoring system has detected an incident affecting one of our shard in Ohio. Customers located on that shard have experienced a high error rate.
provider
- resolved
The incident has been resolved, and traffic is now served without any issue.
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-e5ca28749e
Is Stream still down?
No, this incident was resolved 2024-05-29 01:07 UTC. For Stream's live state, see https://down.guide/stream.
How long did it last?
0m, from 2024-05-29 01:06 UTC to 2024-05-29 01:07 UTC, by the times Stream posted.
What was affected?
Stream named ohio.
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.