Stream (GetStream): Increased API latency

MinorStatus: resolvedStarted 2020-07-28 10:37 UTCResolved 2020-07-28 12:12 UTC (1.6 h)2 updatesstspg.io

Part of an outage event

AWS outage, Jul 28, 2020 · 18 vendors, 18 incidents

Stream (GetStream)’s incident blames AWS as the cause. (hop 1, posted +2 h 8 min vs the first vendor naming AWS)

“…Increased API latency AWS Networking issue is now resolved. We are now cleaning up our temporary remediations since they are not needed anymore. Traffic is back to normal for the last hour. AWS Networ…”

Swipe sideways to see the whole diagram.

Stream (GetStream) is outlined in red. Groups show up to a few vendors each; the event page lists every incident.

Mermaid source

flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
  root --> h4
  me["Stream (GetStream) (this incident)<br/>posted +2 h 8 min"]:::me
  h4 --- me

Full 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: Chat APIus-eastFeed APIus-east

Timeline of updates

identified2020-07-28 10:37 UTC
Due to a networking issue on AWS us-east region, we are experiencing increased latency for some of the traffic on our US region. We are mitigating the problem while waiting for a final remediation on AWS infrastructure.
resolved2020-07-28 12:12 UTC
AWS Networking issue is now resolved. We are now cleaning up our temporary remediations since they are not needed anymore. Traffic is back to normal for the last hour.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Stream (GetStream) profile Recent Stream (GetStream) incidents Markdown JSON