- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard
What to do
Check whether you use Braze Dashboard. 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 1h 5m it lasted.
Anything that failed between 2026-03-20 18:25 UTC and 2026-03-20 19:29 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
- investigating
Braze Engineers are investigating an issue affecting users' ability to reach the Braze Dashboard for the US07 Cluster, starting around 13:41 EST. At this time, no other services are impacted, and messaging sending is not impacted. Engineers are actively working to restore service.
provider
- monitoring
As of 15:12 ET, Braze engineers have implemented a fix and are continuing to monitor service health for improvement.
provider
- resolved
No further issues have been experienced, and all services are operating normally. The incident is now 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-328f32b530
Is Braze still down?
No, this incident was resolved 2026-03-20 19:29 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
1h 5m, from 2026-03-20 18:25 UTC to 2026-03-20 19:29 UTC, by the times Braze posted.
What was affected?
Braze named Dashboard.
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.