Braze: Data Processing and Messaging Sending latency impacting US01

What to do

Check whether you use Braze Data Processing, Outbound Messaging. 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 36m it lasted.
Anything that failed between 2025-07-11 07:43 UTC and 2025-07-11 08:19 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.

investigatingJul 11, 2025, 7:43 AM UTC
Our engineering team is investigating elevated Messaging Sending and Data Processing latency affecting the US01 cluster. We are actively working to identify the root cause and implement a resolution as quickly as possible.
provider
monitoringJul 11, 2025, 7:57 AM UTC
Braze Engineers have implemented a fix for the issue, and we are observing improvements in processing speed. Engineers are now working to process the backlog of messages.
provider
resolvedJul 11, 2025, 8:19 AM UTC
The backlog of messages has now been processed. The incident is now considered resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Braze still down?

No, this incident was resolved 2025-07-11 08:19 UTC. For Braze's live state, see https://down.guide/braze.

How long did it last?

36m, from 2025-07-11 07:43 UTC to 2025-07-11 08:19 UTC, by the times Braze posted.

What was affected?

Braze named Data Processing, Outbound Messaging.

What caused it?

Braze hasn't published a root cause. If it does, it shows here.

Where does this come from?

Braze's official status page, https://braze.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.