Braze: Increased latency in Outbound Messaging for all clusters

What to do

Check whether you use Braze Email, Push Notifications - iOS, Push Notifications - Android. 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 28m it lasted.
Anything that failed between 2025-10-22 23:19 UTC and 2025-10-22 23:48 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.

monitoringOct 22, 2025, 11:19 PM UTC
At approximately 5:09 PM EST, a recent change introduced increased latency in outbound messaging. A fix has been deployed, and service performance is rapidly returning to normal operating levels. We will continue to monitor the system to ensure full resolution.
provider
resolvedOct 22, 2025, 11:48 PM UTC
Braze Engineers have confirmed outbound message latency and service performance is now operating normally and within normal operational bounds. Engineers will continue to monitor service health across all clusters. This incident has been 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-10-22 23:48 UTC. For Braze's live state, see https://down.guide/braze.

How long did it last?

28m, from 2025-10-22 23:19 UTC to 2025-10-22 23:48 UTC, by the times Braze posted.

What was affected?

Braze named Email, Push Notifications - iOS, Push Notifications - Android.

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.