New Multi-region uptime checks and custom-domain status pages

Braze Outage History

Daily provider-status observations and published incident history for Braze.

Operational

Braze is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Braze for future changes.

96.2% of 53 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 93.3% 30 2

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Braze Support Services Outage
critical Observed active window 6h 52m

View incident details and source

Started:

Braze Support Services
monitoring
We are observing signs of resolution, and at this time, customers are able to use our Global Support Service normally. We continue to monitor the service while Salesforce continues remediation of the Salesforce Service Cloud issue. Customers can now raise cases via the Braze Support Portal and the Braze AI Operator as usual.
identified
Braze Support Services and Partner Portal are currently experiencing issues due to an incident impacting Salesforce Service Cloud. Customers may experience issues when submitting cases via the Braze Support Portal and Braze AI Operator. During this time, you may also experience delays in response to support cases. For any critical cases, please contact support@braze.com.
Dashboard Latency and Errors on US07
minor Observed active window 29m

View incident details and source

Started:

Dashboard
identified
We are investigating intermittent errors and latency impacting the US07 Dashboard.
Latency and Errors on US07
minor Observed active window 2h 26m

View incident details and source

Started:

Dashboard
monitoring
Engineers have implemented a fix and the Dashboard has been stable for over 30 minutes. We are continuing to monitor the issue to ensure full resolution.
identified
We have identified the issue leading to intermittent dashboard errors and latency and engineers are working to resolve the issue.
investigating
Our Engineering team are investigating intermittent latency and errors on the US07 Dashboard.

Legacy Incident Archive

13 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Issue Impacting US 01 and US 03
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue with the US 01 and US 03 clusters.
July 2026
EU02 Currents Data Latency
minor Source not attested
Last archived state: resolved
View archived record details
identified
We continue to make progress clearing the remaining backlog on EU02, improving our performance, and decreasing overall latency. We expect to be caught up within the next hour, although a small number of events may take slightly longer to fully process. The remaining impact is limited to less than half a percent of our overall traffic. We'll provide another update once we're fully caught up.
identified
We continue to investigate degraded performance in EU02. We have identified the root cause of the underlying latency, which stemmed from multiple Currents connectors failing to gracefully restart after routine maintenance, but appearing in a healthy state in our monitoring system. Those specific servers build significant backlogs while in this state. We have completed a graceful restart, and have spun up additional resources to process through the backlogged items more rapidly. At this poi...
investigating
We are currently investigating degraded performance in our EU02 cluster, which is causing delays in Currents processing for a small subset of customers. No data has been lost, and the majority of Currents data continues to flow normally. Our team is actively working toward a resolution and will provide updates as they become available.
Braze AI Operator Errors
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix is being deployed for the issue affecting the Braze AI Operator, where users were seeing the error message: "Connection unstable - Check your Wi-Fi or internet signal and try again." We are seeing error rates improve and are continuing to monitor closely to confirm full resolution. We will provide a further update once we can confirm the issue is fully resolved.
investigating
Braze engineers have identified an issue affecting the Braze AI Operator, where users may see the following error message: "Connection unstable - Check your Wi-Fi or internet signal and try again". We are actively investigating the issue and will provide updates as more information becomes available.
June 2026
WhatsApp Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Meta's services appear to be stabilizing. We are continuing to monitor the situation and will provide a further update once full service has been restored.
identified
Meta, a third-party, is currently experiencing an issue impacting WhatsApp services. During this time, WhatsApp messages may experience latency. Campaign and Canvas creation or modification may experience errors and latency when utilizing WhatsApp templates. Audience sync to Facebook may also experience errors and latency during this period.
May 2026
US01 and EU01 Processing Latency
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering team has implemented a change, and we are beginning to see improvements in latency across campaign and Canvas processing, data ingestion, and message sending on US-01 and EU-01. We are monitoring the situation closely.
investigating
Our engineering team continues to investigate the elevated latency. We will provide another update in 30 min or sooner if there are any changes.
investigating
Starting at 1:00 PM ET, customers on our US-01 and EU-01 clusters are experiencing elevated latency affecting campaign and Canvas processing, data ingestion, and message sending. Our engineering team is actively investigating, and we will provide updates as the situation develops.
US05 Processing Latency
minor Source not attested
Last archived state: resolved
View archived record details
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.
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.
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.
Agent Console auto model errors
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering team have released a fix and Agent Console auto models are now recovering. We are continuing to monitor the situation.
identified
We have identified a third party issue causing Agent Console auto models to error. Our engineering team is actively working to remediate the issue.
SMS Delivery Delays to Multiple Countries in Europe
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
SMS sending delays have been resolved for the majority of countries and sending has returned to normal. SMS delivery delays continue to impact Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde. For real-time updates from Twilio, please refer to: https://status.twilio.com/incidents/shhrhbqxflt1
monitoring
Braze Engineers continue to monitor the ongoing SMS delivery delays affecting multiple networks across European countries. This remains an active Twilio incident, and our team is closely tracking their progress. Twilio has identified the cause and is actively working to resolve the issue. They state that delivery delays to multiple networks continue in Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde. The incident has been resolved, and latency has returned to normal in all o...
identified
Braze Engineers continue to monitor the ongoing SMS delivery delays affecting multiple networks across European countries. This remains related to an active Twilio incident, and our team is closely tracking their progress. Twilio has identified the cause and is actively working to resolve the issue. We will provide another update as soon as the situation changes. For real-time updates from Twilio, please refer to: https://status.twilio.com/incidents/shhrhbqxflt1
identified
Braze Engineers have identified an issue causing SMS delivery delays across networks in multiple European countries. Braze Engineers confirmed this is related to an ongoing Twilio incident: https://status.twilio.com/incidents/shhrhbqxflt1 We expect to provide another update as soon as more information becomes available.
April 2026
Issue impacting EU01
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Braze engineers are continuing to work through the remaining messages in the backlog. We are now seeing improvements in processing speeds, though data processing remains in a degraded performance state while the backlog is fully cleared.
monitoring
Braze engineers are processing the remaining backlog of messages. Data processing remains in a degraded state due to backlog and latency issues.
monitoring
Braze engineers have identified the issue. Services remain degraded but are improving.
identified
Braze engineers are actively investigating the issue and working to restore services.
investigating
We are currently investigating an issue with the EU01 cluster.
Delays in Support Case Creation via Email
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We have begun receiving responses in cases that were delayed by this incident. Case creation via email is now being processed. Support is actively working through the backlog of requests and follow-ups created during the disruption.
identified
We are continuing to investigate this incident. Both Google Workspace and Salesforce's Email-to-Case functionality are reporting issues related to the processing of email. New cases created by emailing support@braze as well as responses on existing cases are not being processed. In the meantime please submit your request by clicking "Get Help" in the top-right corner of your Braze workspace. Alternatively, your CSM may also be able to support.
identified
We have identified the root cause of the issue is Google Workspace incident (https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT). This is causing delays in emails being sent and received.
investigating
We are currently experiencing an issue where cases sent to support@braze.com may not be created as expected. Our team is actively investigating the issue. In the meantime, if you require assistance, please submit your request via the Braze Support Portal or reach out to your Customer Success Manager. We will provide an update as soon as more information becomes available.