Braze: Delayed data processing and message sending in EU 01

AWS outage, Nov 12, 2019 · 11 vendors, 12 incidents

Braze’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +40 min vs the first vendor naming AWS)

“…01 All systems have remained fully operational the past 20 minutes since the last update. AWS has not yet formally marked the issue as resolved, but we will update this page again if issues recur.…”

flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 4 blamed AWS<br/>Opsgenie, Elastic Cloud, Wise, JFrog +1"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Confluent"]:::blames
  root --> h4
  later["Later<br/>1 vendor<br/>JFrog"]:::names
  root --> later
  me["Braze (this incident)<br/>posted +40 min"]:::me
  root -.->|"same window"| 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.