CompaniesStream (GetStream)Incidents
Stream (GetStream): AWS connectivity issues
AWS us-east-2 outage, Jul 28, 2022 · 25 vendors, 26 incidents
Stream (GetStream)’s incident blames AWS as the cause. (hop 1, posted +1 h 17 min vs the first vendor naming AWS)
“…AWS connectivity issues This incident has been resolved. The issue has been resolved and the service in Ohio region is operating normally. This incident has been resolved. We experience a partial outa…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-2<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Elastic Cloud, Coralogix, Confluent, Aptible +1"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Stream (GetStream)"]:::blames
root --> h4
me["Stream (GetStream) (this incident)<br/>posted +1 h 17 min"]:::me
h4 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: OhioOhio - Chat - Edge
Timeline of updates
- identified
We experience a partial outage due to AWS connectivity issues for selected apps in the Ohio region
- identified
The issue has been resolved and the service in Ohio region is operating normally.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Stream (GetStream) profileRecent Stream (GetStream) incidentsMarkdownJSON