Braze: US05 Dashboard latency

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 15m it lasted.
Anything that failed between 2026-03-17 20:49 UTC and 2026-03-17 21:04 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.

investigatingMar 17, 2026, 8:49 PM UTC
Braze Engineers are investigating an issue affecting users' ability to reach the Braze Dashboard for the US05 Cluster, starting around 16:15 EST. At this time, no other services are impacted, and messaging sending is not impacted. Engineers are actively working to restore service.
provider
monitoringMar 17, 2026, 8:57 PM UTC
As of 16:47 ET, Braze engineers have implemented a fix and are continuing to monitor service health for improvement.
provider
resolvedMar 17, 2026, 9:04 PM UTC
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.

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 2026-03-17 21:04 UTC. For Braze's live state, see https://down.guide/braze.

How long did it last?

15m, from 2026-03-17 20:49 UTC to 2026-03-17 21:04 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.