Braze: Increased Latency in US01/US03
AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents
Braze’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +58 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
root --> h4
me["Braze (this incident)<br/>posted +58 min"]:::me
root -.->|"same window"| 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.
Timeline of updates
- resolved
At this time, all delayed messages have been sent, and data processing latency has returned to normal levels. Additionally, Amazon has posted that they have now fully restored power to all instances and devices in the affected data center. We're considering this incident to be resolved. No data or messages were lost.
From Braze’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on braze.statuspage.io (opens in new tab).