- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing, Outbound Messaging
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 31m it lasted.
Anything that failed between 2025-07-30 14:49 UTC and 2025-07-30 15: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.
Updates from Braze 3
- monitoring
We have identified degraded performance between 2:05 PM and 2:28 PM UTC, which impacted Outbound Messaging and Data Processing on the EU01 cluster. This issue is now resolved, and Engineers are continuing to monitor services.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
Engineers have continuously been monitoring services, and they have remained stable. This issue is now considered fully resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a1599e8853
Is Braze still down?
No, this incident was resolved 2025-07-30 15:19 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
31m, from 2025-07-30 14:49 UTC to 2025-07-30 15: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.