- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Outbound Messaging, Outbound Messaging, Currents, Currents, Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI)
- Regions
- eu
What to do
Check whether you use Braze Outbound Messaging, Outbound Messaging, Currents, Currents and 2 more in eu. 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 6h 34m it lasted.
Anything that failed between 2025-03-10 15:47 UTC and 2025-03-10 22:21 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 12
- identified
We are currently experiencing latency issues with Currents and CDI due to an infrastructure problem. Our engineering team is actively working to resolve this and restore normal functionality as quickly as possible.
provider
- identified
We continue to observe elevated latency impacting Currents and CDI. Our engineering teams are actively working to resolve this and restore normal functionality as quickly as possible.
provider
- identified
We continue to observe elevated latency impacting Currents and CDI. Our engineering teams are actively working to resolve this and restore normal functionality as quickly as possible.
provider
- identified
Engineers continue to work to resolve the issue impacting Currents and CDI. Latency is currently highly elevated for Currents. Additionally, some customers may experience latency with CDI integrations.
provider
- identified
Braze Engineers are actively working to resolve the ongoing issue impacting Currents and CDI. We are now observing elevated messaging latency as a result of this issue. Currently, latency remains highly elevated for Currents, and some customers may also experience latency with CDI integrations. We appreciate your patience as we work to resolve these issues.
provider
- identified
The Braze Engineers have deployed changes to decrease Messaging latency and most messages are sent within normal operational bounds. Our Engineers continue to work on restoring the Currents and CDI Services. At this time Currents and CDI Services latency remains very high.
provider
- identified
Outbound Messaging is operating within normal bounds following the changes deployed by The Braze Engineers. At this time Currents and CDI Services latency remains very high and our Engineers are continuing to work to restore the Currents and CDI Services.
provider
- identified
Outbound Messaging is continuing to operate within normal bounds. The Braze CDI is now fully operational, and all new events are being processed within normal operational bounds. If you do not regularly sync the CDI integration, you will need to replay any syncs that failed to fully complete. This step is necessary to prevent old data from overwriting new data that was successfully synced during the incident. You can check the status of your jobs in the dashboard under the Sync log tab within the Cloud Data Ingestion page. Our Braze Engineers are actively working to restore the Currents service. We will provide further updates as the restoration progresses.
provider
- identified
Outbound messaging continues to operate within normal bounds. The Braze CDI continues to be fully operational, and all new events are being processed within normal operational bounds. The Currents Service has been restored, and new events are being processed within normal operational bounds. Braze Engineers continue to work on processing the backlog of events impacted by the incident.
provider
- monitoring
Currents is functioning normally, with all new events processing within normal operational bounds. Our Braze Engineering team is actively working to clear the backlog of Currents events.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
As of 11:20am ET, both the Currents and Braze CDI services have been fully restored to normal operational performance. Since that time, all CDI syncs and new Currents events have been processing within standard parameters. The Braze Engineering team has completed the immediate restoration work and is continuing to process the backlog of Currents events produced during the incident's impact window. Depending on the volume of events and the downstream destination for your integration, the backlog processing may take some time and will be different for each integration. As such, with systems operating normally for new incoming events, we are marking this issue as resolved at this time. Should you have questions, please reach out to Braze Support.
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-208cfa6a4d
Is Braze still down?
No, this incident was resolved 2025-03-10 22:21 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
6h 34m, from 2025-03-10 15:47 UTC to 2025-03-10 22:21 UTC, by the times Braze posted.
What was affected?
Braze named Outbound Messaging, Outbound Messaging, Currents, Currents and 2 more in eu.
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.