Braze: Degraded data processing and message sending in US AWS Clusters
Timeline of updates
- resolved
AWS updated us at 1:17 ET to report this issue as resolved, and that the service is operating normally: "Between 8:20 AM and 9:57 AM PDT, we experienced elevated packet loss, impacting AWS Direct Connect connectivity to a single Availability Zone (use1-az6) in the US-EAST-1 Region." We have now re-enabled our servers in the affected AZ and are no longer seeing any errors. Lastly, our job processing latency has returned to normal, and we are considering this incident resolved.
From Braze’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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 braze.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Braze, started 2020-08-22 16:27 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Degraded data processing and message sending in US AWS Clusters
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/pn12qxp6l089
Braze profileRecent Braze incidentsAll outages on August 22, 2020Braze in August 2020MarkdownJSON