- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Braze in us. 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 0m it lasted.
Anything that failed between 2025-05-21 18:11 UTC and 2025-05-21 15:30 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 1
- resolved
We experienced a service degradation on the US-01 cluster between 11:46 ET and 11:58 ET. During this 12-minute period, SDK API and Dashboard services hosted on the US-01 cluster were impacted by increased errors. SDK API errors were successfully retried. Our engineering team responded immediately when the issue was detected and restored full service functionality at 11:58 ET. All systems are now operating normally.
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-de6783dbf1
Is Braze still down?
No, this incident was resolved 2025-05-21 15:30 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
0m, from 2025-05-21 18:11 UTC to 2025-05-21 15:30 UTC, by the times Braze posted.
What was affected?
Braze named in us.
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.