- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard, SDK Data Collection, Data Processing, Outbound Messaging
- Regions
- us, us-east-1
What to do
Check whether you use Braze Dashboard, SDK Data Collection, Data Processing, Outbound Messaging in us, us-east-1. 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 12m it lasted.
Anything that failed between 2026-05-08 04:35 UTC and 2026-05-08 05:47 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 4
- identified
Starting at 11:45 PM ET, Braze customers on our US05 have been experiencing latency across campaign/canvas processing, data processing, and message sending due to an ongoing issue with an upstream provider (AWS). We are working on a fix. Please see https://health.aws.amazon.com/health/status for more details.
provider
- identified
We are continuing to experience delays in Campaign & Canvas Processing, Data Processing, and Message Sending. Additionally, Dashboard navigation is intermittently erroring. We are continuing to work on a fix while we await updates from AWS. Please see https://health.aws.amazon.com/health/status for more details.
provider
- monitoring
We have implemented a fix to mitigate the impact of the ongoing AWS incident in Availability Zone (use1-az4) in the US-EAST-1 region. At this point, latency and error rates have returned to normal levels for all services. Additionally, AWS is reporting early signs of recovery. Please see https://health.aws.amazon.com/health/status for more details.
provider
- resolved
Latency and error rates have remained at normal levels for all services, post-implementation of our fix, and this incident is resolved. We will continue to monitor the overall system health until AWS reports full recovery. Please see https://health.aws.amazon.com/health/status for more details.
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-1151e9ab55
Is Braze still down?
No, this incident was resolved 2026-05-08 05:47 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
1h 12m, from 2026-05-08 04:35 UTC to 2026-05-08 05:47 UTC, by the times Braze posted.
What was affected?
Braze named Dashboard, SDK Data Collection, Data Processing, Outbound Messaging in us, us-east-1.
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.