EU02 Currents Data Latency

What to do

• Check whether you use Braze Currents. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 15m it lasted.

  Anything that failed between 2026-07-31 14:09 UTC and 2026-07-31 19:25 UTC may need a replay.

• Subscribe to Braze's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=braze works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Braze 4

1. investigatingJul 31, 2026, 2:09 PM UTC

   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.

   provider

2. identifiedJul 31, 2026, 4:14 PM UTC

   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.

   provider

3. identifiedJul 31, 2026, 6:04 PM UTC

   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.

   provider

4. resolvedJul 31, 2026, 7:25 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.