Is Braze Down?

Between 11:30 ET and 12:55 ET, some customers experienced elevated error rates. Braze engineers identified the issue and resolved it by rolling back a recent change and applying database optimizations. Error rates returned to normal shortly after each fix was applied, and they have remained stable for the past hour. This incident is now resolved. --- [2026-08-05T12:13:03.391-04:00] (investigating) We are currently investigating an issue with the US 01 and US 03 clusters.

This incident is resolved. As of 15:18 ET / 19:18 UTC, we have fully processed the backlog of jobs, and our EU02 Currents connectors are all again processing within normal latency ranges. No data was lost, and all Currents events have been sent to their destinations. --- [2026-07-31T14:13:06.942-04:00] (identified) We continue to make progress clearing the remaining backlog on EU02, improving our performance, and decreasing overall latency. We expect to be caught up within the next hour, although a small number of events may take slightly longer to fully process. The remaining impact is limited to less than half a percent of our overall traffic. We'll provide another update once we're fully caught up. --- [2026-07-31T12:14:39.181-04:00] (identified) We continue to investigate degraded performance in EU02. We have identified the root cause of the underlying latency, which stemmed from multiple Currents connectors failing to gracefully restart after routine maintenance, but appearing in a healthy state in our monitoring system. Those specific servers build significant backlogs while in this state. We have completed a graceful restart, and have spun up additional resources to process through the backlogged items more rapidly. At this point ~95% of data is flowing normally, while up to ~5% of our connectors, impacting a subset of customers, continue to experience latency. We see throughput significantly improved due to config changes, and will provide an update in 1 hour or when we have an updated timeline. --- [2026-07-31T10:09:58.097-04:00] (investigating) We are currently investigating degraded performance in our EU02 cluster, which is causing delays in Currents processing for a small subset of customers. No data has been lost, and the majority of Currents data continues to flow normally. Our team is actively working toward a resolution and will provide updates as they become available.

At approximately 7:30 AM ET, we became aware of an AWS networking outage in the US-WEST-2 region affecting network connectivity between 6:55 AM ET and 8:00 AM ET. AWS has since resolved the underlying issue. During the impact window, some customers may have experienced intermittent delays and latency in email delivery. Mail is now being delivered normally. As queue depth increased, some customers may have experienced residual delays in message delivery. These delays have been resolved as of 2:40 PM ET today. This disruption originated within AWS infrastructure and was not caused by any component of the Braze platform. For further details on the AWS incident, please refer to the AWS status page: https://health.aws.amazon.com/health/status