Braze

Affected: Braze Support Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-16 09:17 UTC

   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...

2. monitoring 2026-09-16 15:40 UTC

   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...

3. resolved 2026-09-16 16:09 UTC

   This issue has been resolved. Our Global Support Service is operating normally, and customers can raise cases via the Braze Support Portal and the Braze AI Operator as usual. We have confirmed stable service following remediation of the underlying Salesforce Service Cloud issue.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-02 11:30 UTC

   We are investigating intermittent errors and latency impacting the US07 Dashboard.

2. resolved 2026-09-02 11:58 UTC

   This was a recurrence of an earlier issue impacting the Dashboard. A permanent fix has been implemented and the Dashboard has remained stable since. We are confident the issue is now fully resolved. We apologize for any impact.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 07:43 UTC

   Our Engineering team are investigating intermittent latency and errors on the US07 Dashboard.

2. identified 2026-09-02 08:58 UTC

   We have identified the issue leading to intermittent dashboard errors and latency and engineers are working to resolve the issue.

3. monitoring 2026-09-02 09:36 UTC

   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.

4. resolved 2026-09-02 10:09 UTC

   The Dashboard has continue to remain stable and the issue is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, REST APIs, REST APIs

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 16:13 UTC

   We are currently investigating an issue with the US 01 and US 03 clusters.

2. resolved 2026-08-05 17:54 UTC

   Between 11:30 ET and 12:55 ET, some customers experienced elevated error rates. Braze engineers identified the issue and resolved it by rolling back a recent change and applying database optimizations. Error rates returned to normal shortly after each fix was applied, and they...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Currents

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 14:09 UTC

   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...

2. identified 2026-07-31 16:14 UTC

   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...

3. identified 2026-07-31 18:04 UTC

   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...

4. resolved 2026-07-31 19:25 UTC

   This incident is resolved. As of 15:18 ET / 19:18 UTC, we have fully processed the backlog of jobs, and our EU02 Currents connectors are all again processing within normal latency ranges. No data was lost, and all Currents events have been sent to their destinations.

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-07-24 19:00 UTC

   At approximately 7:30 AM ET, we became aware of an AWS networking outage in the US-WEST-2 region affecting network connectivity between 6:55 AM ET and 8:00 AM ET. AWS has since resolved the underlying issue. During the impact window, some customers may have experienced...

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 18:43 UTC

   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...

2. monitoring 2026-07-13 20:54 UTC

   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...

3. resolved 2026-07-13 21:31 UTC

   The issue impacting the Braze AI Operator, where users were seeing the error message: "Connection unstable - Check your Wi-Fi or internet signal and try again," has been fully resolved. The fix has been deployed and error rates have returned to normal levels.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: WhatsApp

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-12 14:58 UTC

   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...

2. monitoring 2026-06-12 16:52 UTC

   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.

3. resolved 2026-06-12 18:13 UTC

   Meta has recovered from the earlier issue impacting WhatsApp services, and full service has now been restored. WhatsApp message delivery, Campaign and Canvas creation or modification using WhatsApp templates, and Audience sync to Facebook are all operating normally.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Data Processing, Data Processing, Outbound Messaging, Outbound Messaging

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 17:45 UTC

   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...

2. investigating 2026-05-22 18:17 UTC

   Our engineering team continues to investigate the elevated latency. We will provide another update in 30 min or sooner if there are any changes.

3. monitoring 2026-05-22 18:34 UTC

   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.

4. resolved 2026-05-22 18:41 UTC

   Latency and error rates have remained at normal levels across all services following the implementation of our fix. This incident is resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection, Data Processing, Outbound Messaging

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-08 04:35 UTC

   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...

2. identified 2026-05-08 05:04 UTC

   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...

3. monitoring 2026-05-08 05:32 UTC

   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....

4. resolved 2026-05-08 05:47 UTC

   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...

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-07 16:38 UTC

   We have identified a third party issue causing Agent Console auto models to error. Our engineering team is actively working to remediate the issue.

2. monitoring 2026-05-07 16:53 UTC

   Our engineering team have released a fix and Agent Console auto models are now recovering. We are continuing to monitor the situation.

3. resolved 2026-05-07 17:19 UTC

   Following continued monitoring by our engineers, Agent Console auto models have remained stable. This incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: SMS

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-07 13:19 UTC

   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...

2. identified 2026-05-07 17:10 UTC

   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...

3. monitoring 2026-05-08 00:44 UTC

   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...

4. monitoring 2026-05-08 11:46 UTC

   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:...

5. resolved 2026-05-08 12:36 UTC

   Latency has returned to normal operational bounds and this incident is now resolved. Twilio's Statuspage will continue to provide updates on the remaining impact to Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde: https://status.twilio.com/incidents/shhrhbqxflt1

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection, Data Processing, REST APIs, Outbound Messaging

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 16:18 UTC

   We are currently investigating an issue with the EU01 cluster.

2. identified 2026-04-20 16:49 UTC

   Braze engineers are actively investigating the issue and working to restore services.

3. monitoring 2026-04-20 17:13 UTC

   Braze engineers have identified the issue. Services remain degraded but are improving.

4. monitoring 2026-04-20 17:33 UTC

   Braze engineers are processing the remaining backlog of messages. Data processing remains in a degraded state due to backlog and latency issues.

5. monitoring 2026-04-20 18:02 UTC

   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.

6. resolved 2026-04-20 19:24 UTC

   The message backlog has been cleared, and data processing has returned to normal operational bounds. All services continue to remain stable, and this incident is considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-17 20:00 UTC

   Between 16:00 and 18:14 ET, Braze Engineers identified and resolved an issue causing intermittent SDK errors on the US01 cluster. As of 18:19 ET, services remain stable, and any failed SDK requests during the impact window were automatically retried.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Braze Support Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-08 19:05 UTC

   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...

2. identified 2026-04-08 19:44 UTC

   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.

3. identified 2026-04-08 20:34 UTC

   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....

4. monitoring 2026-04-08 21:27 UTC

   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.

5. resolved 2026-04-08 21:49 UTC

   The issue affecting email processing for support cases has been resolved. New cases sent to support@braze.com and replies to existing cases are now being processed as expected. Our Support team is actively working through the backlog of requests created during the disruption....

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-06 21:00 UTC

   Between 17:00 and 18:35 EST, Braze Engineers identified and resolved an issue causing intermittent SDK errors on the US01 cluster. As of 18:40 EST, services remain stable, and any failed SDK requests during the impact window were automatically retried.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-24 17:45 UTC

   Starting around 16:45 UTC, Braze Engineers began observing an issue where EU02 end users may experience errors when accessing or attempting to unsubscribe via the email preference center.

2. monitoring 2026-03-24 17:50 UTC

   As of 17:47 UTC, Braze Engineers have implemented a fix and are monitoring service health for improvement.

3. resolved 2026-03-24 17:58 UTC

   No further issues have been experienced, and all services are operating normally. The incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-20 18:25 UTC

   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...

2. monitoring 2026-03-20 19:19 UTC

   As of 15:12 ET, Braze engineers have implemented a fix and are continuing to monitor service health for improvement.

3. resolved 2026-03-20 19:29 UTC

   No further issues have been experienced, and all services are operating normally. The incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-17 20:49 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...

2. monitoring 2026-03-17 20:57 UTC

   As of 16:47 ET, Braze engineers have implemented a fix and are continuing to monitor service health for improvement.

3. resolved 2026-03-17 21:04 UTC

   No further issues have been experienced, and all services are operating normally. The incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-24 19:34 UTC

   Braze Engineers detected an increase in latency on email outbound messaging for customers on Bird (Sparkpost) non-EU Braze clusters. This latency build up started at 13:53 ET. Braze has engaged Sparkpost, who have declared an incident and are actively investigating, you can...

2. investigating 2026-02-24 19:42 UTC

   As of 14:34 ET, Sparkpost has identified the root cause to be a networking issue on their US cluster. We are monitoring performance for improvement.

3. resolved 2026-02-24 20:00 UTC

   As of 14:41 ET, Sparkpost has declared this incident resolved after implementing a fix. Braze Engineers have confirmed that real time outbound email latency has returned within normal operational bounds as of 14:34 ET. Any messages that failed during this window, were...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-18 12:07 UTC

   We have received reports of errors when navigating the EU01 and EU02 Dashboards. Braze engineers are observing a small increase in errors and are actively investigating the issue.

2. investigating 2026-02-18 12:39 UTC

   We are continuing to investigate the issue.

3. investigating 2026-02-18 15:20 UTC

   We are continuing to investigate this issue with urgency and have escalated to our network service provider.

4. identified 2026-02-18 17:51 UTC

   We've identified an issue isolated impacting our edge network impacting customers accessing the dashboard from Europe. We have escalated the issue to our network provider and are investigating with urgency.

5. monitoring 2026-02-18 18:13 UTC

   The errors have stabilised to normal operating levels. We are continuing to monitor the situation closely and are actively investigating with our networking provider.

6. resolved 2026-02-18 19:22 UTC

   We can confirm services have continued to remain stable and the issue is now considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-03 15:41 UTC

   Starting at 10:25 ET Braze Engineers began observing errors impacting the US02 Dashboard and SDK services. Braze Engineers are currently investigating the issue and SDK service has been restored. We will provide further updates in 15 minutes.

2. monitoring 2026-02-03 15:47 UTC

   Dashboard Service has been restored since 10:43 ET. Braze Engineers are continuing to monitor the stability of services.

3. resolved 2026-02-03 16:02 UTC

   We can confirm service have continued to remain stable and the issue is now considered resolved. Impact: SDK: Engineers observed an increase in SDK errors between 10:25 ET and 10:36 ET. The SDK will automatically retry failed requests and no action is required. Dashboard:...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-01-24 18:27 UTC

   Braze is aware of an active incident with Google that is impacting how emails are delivered and filtered in Gmail. Emails that should normally land in the Promotion Tab are being sent to the Primary Tab. In addition, Gmail users might see banners indicating that spam checks are...

2. resolved 2026-01-25 01:59 UTC

   As of 8:28 PM EST, Google has resolved the issue. We recommend continuing to monitor Gmail’s status page for Google’s final incident analysis and to use Braze’s Deliverability Center while following email-sending best practices.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-23 00:47 UTC

   Braze Engineers have identified elevated email bounce rates for customers sending email via SparkPost (Bird), starting around 17:35 ET. We are working with SparkPost Engineering who are aware and investigating the issue. We'll update in 30 minutes or when we have an update from...

2. investigating 2026-01-23 02:00 UTC

   Braze and Sparkpost engineers continue to investigate this issue. While we have not fully identified the root cause, Sparkpost is reverting a code deployment from this afternoon that we believe could be correlated. Our next update will come in an hour, or when the revert is...

3. monitoring 2026-01-23 02:57 UTC

   SparkPost's revert successfully resolved this issue, and we have seen bounce rates return to normal levels, and no instances of the specific error code as of 9:42 PM ET. Our engineering teams will continue to monitor the situation to ensure the issue does not recur.

4. resolved 2026-01-23 03:42 UTC

   We have not seen any instances of the specific error code in an hour, since 9:42 PM ET. This incident is considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-13 21:00 UTC

   Between 4:05 PM and 4:58 PM ET, some SMS messages experienced a temporary delivery delay. The issue has been fully resolved. All delayed messages were safely queued and are now being delivered. No messages were lost. Our systems are operating normally, and our team is monitoring...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-06 15:41 UTC

   We are investigating an issue impacting users reaching the Braze Dashboard for the US05 Cluster. No other services are impacted and messaging sending is not impacted. Engineers are actively working to restore service.

2. monitoring 2026-01-06 15:46 UTC

   Between 10:26 ET to 10:43 ET users may have experienced errors when trying to access the Braze Dashboard on the US05 Cluster. Service has now been restored and Engineers continue to monitor.

3. resolved 2026-01-06 16:29 UTC

   No further issues have been experienced and all services are operating normally. The incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: SDK Data Collection, REST APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-24 11:26 UTC

   Our Engineering team is investigating elevated REST and SDK Errors on the EU01 Cluster.

2. monitoring 2025-11-24 11:51 UTC

   The REST API and SDK Data Collection has returned to normal operation and engineers are continuing to monitor services. Any SDK API requests that returned an error will have been automatically retired. Any REST API requests that received an error will need to be retried.

3. resolved 2025-11-24 12:09 UTC

   The REST API and SDK Data Collection have continued to remain stable and this incident is considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection, SDK Data Collection, Data Processing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-19 00:34 UTC

   Starting at 19:12 ET Braze Engineers identified an issue impacting the US01 and US03 Dashboard and SDK. Engineers are currently investigating the issue.

2. monitoring 2025-11-19 01:17 UTC

   The Braze Engineering team have implemented a fix and are monitoring the results. Since 19:46 ET errors have dropped and services are operating normally.

3. resolved 2025-11-19 01:33 UTC

   US01 and US03 Dashboard and SDK services have remained stabled. The incident is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-11-18 22:24 UTC

   Starting at 16:55 ET Braze Engineers identified an issue impacting the US02 Dashboard and SDK. At 17:18 ET Engineers implemented a fix and services have returned to normal operation. Engineers are continuing to monitor service stability.

2. resolved 2025-11-18 22:35 UTC

   The US02 Dashboard and SDK have remained stable since 17:18 ET. We can confirm the incident is resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-11-04 21:00 UTC

   Braze Engineers identified a Dashboard configuration error that was deployed at 15:50 ET, preventing navigation and logins on EU02. At 16:04 ET, the errant configuration change was reverted, and a redeploy was executed. During this window, EU02 customers experienced issues...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email, Push Notifications - iOS, Push Notifications - Android

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-10-22 23:19 UTC

   At approximately 5:09 PM EST, a recent change introduced increased latency in outbound messaging. A fix has been deployed, and service performance is rapidly returning to normal operating levels. We will continue to monitor the system to ensure full resolution.

2. resolved 2025-10-22 23:48 UTC

   Braze Engineers have confirmed outbound message latency and service performance is now operating normally and within normal operational bounds. Engineers will continue to monitor service health across all clusters. This incident has been resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SMS, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 09:52 UTC

   Our Engineering team is aware that AWS is experiencing an outage on Monday, October 20, 2025. At the moment, the following services are impacted: Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging...

2. identified 2025-10-20 10:40 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze Data Processing and Outbound messaging is experiencing elevated latency on the US03 and US05...

3. identified 2025-10-20 10:57 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

4. identified 2025-10-20 11:23 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

5. identified 2025-10-20 12:15 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

6. identified 2025-10-20 12:47 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

7. identified 2025-10-20 13:13 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

8. identified 2025-10-20 13:48 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. The SDK Data Collection on the US03 is experiencing a high level of errors. SDK requests will continually retry until SDK collection is back to normal...

9. identified 2025-10-20 14:12 UTC

   Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the...

10. identified 2025-10-20 14:42 UTC

    At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the following clusters due to AWS capacity issues: -US01 -US02 (Data Processing and Outbound Messaging) -US03 -US04 -US05...

11. identified 2025-10-20 15:02 UTC

    Our engineers are continuing to monitor the impact of internal and external services caused by the AWS US East 1 outage. The SDK Data Collection on the US06 is experiencing a high level of errors. SDK requests will continually retry until SDK collection is back to normal...

12. identified 2025-10-20 16:21 UTC

    At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the following clusters due to AWS capacity issues: -US01 -US02 (Data Processing and Outbound Messaging) -US03 -US04 -US05...

13. identified 2025-10-20 17:03 UTC

    At the moment, the following services are impacted: Braze SDK Data Collection, Data Processing and Outbound Messaging is experiencing elevated latency on the following clusters due to AWS capacity issues: -US01 -US02 (Data Processing and Outbound Messaging) -US03 -US04 -US05...

14. identified 2025-10-20 17:33 UTC

    We are starting to see improvements in provisioning capacity from AWS. As we see additional capacity online we are observing small improvements in processing latent jobs. We'll continue to load balance our work to protect system health, as our engineers continue to closely...

15. identified 2025-10-20 17:50 UTC

    We are starting to see improvements in Twilio's service. As Twilio continues to stabilize, we are observing improvements in SMS sending. Customers using SMS authentication are now able to login to the Braze dashboard without issue. Our engineers continue to monitor the situation.

16. identified 2025-10-20 19:06 UTC

    We are continuing to see improvements processing the backlog of latent jobs across clusters. The US04 and US02 are now fully operational and the backlog has completed processing. SDK Data Collection on the US03 cluster has now stabilised and is returning to normal operation....

17. identified 2025-10-20 19:59 UTC

    We are continuing to see improvements processing the backlog of latent jobs across clusters. The following services are now fully operational: US01 - Data Processing, SDK Data Processing US03 - Data Processing, SDK Data Processing US06 - Data Processing, SDK Data Processing...

18. identified 2025-10-20 20:18 UTC

    We are continuing to see improvements processing the backlog of latent jobs across clusters. The following clusters are now fully operational: -US06 -US01 We'll continue to load balance our work to protect system health, as our engineers continue to closely monitor and manage...

19. identified 2025-10-20 20:47 UTC

    We can confirm the US05 Cluster is now fully operational. The US03 Cluster backlog is continuing to process and engineering team is working to return the cluster to full operation.

20. monitoring 2025-10-20 21:44 UTC

    The US03 cluster has completed processing the back and is now fully operational. All other clusters are operating within normally operational bounds. Engineers to monitor the stability of Twilio services as they work to recover from the US East 1 outage. We will update further...

21. resolved 2025-10-20 23:41 UTC

    This incident has been resolved. Twilio services have recovered from the AWS US East 1 outage. Customers can now login to the Braze dashboard via SMS authentication, send SMS messages through the Braze platform, and receive SMS responses from end users without issues. All Braze...

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-10-08 10:00 UTC

   Between 11:00 AM and 12:43 PM ET on October 8, 2025, Dashboard users on the US-10 cluster experienced errors accessing the Braze Dashboard. This service disruption occurred during remediation work for a misconfiguration issue, whereby Braze Engineering teams restarted services...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-09-09 19:07 UTC

   We are currently investigating elevated error rates affecting our REST API and SDK services across all US clusters. The issue began at approximately 2:26 PM ET. Our engineering team has identified that this incident is related to an ongoing Cloudflare outage that is impacting...

2. monitoring 2025-09-09 19:20 UTC

   As of 3:13PM ET, Cloudflare has implemented a fix and is monitoring the results. Braze Engineers will continue monitor service health.

3. resolved 2025-09-09 19:30 UTC

   Braze Engineers have confirmed US clusters continue to operate within normal operational bounds since 3:04PM ET. Engineers will continue to monitor service health across all US clusters. This incident has been resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-09-05 17:54 UTC

   Braze Engineers are investigating an issue where customers might have experienced issues within the Dashboard and time series data not updating properly. Message sending and data processing were not impacted. A fix has been implemented and we are monitoring the results. Some...

2. resolved 2025-09-05 18:01 UTC

   Braze Engineers have confirmed US05 cluster services continue to operate within normal operational bounds. Engineers will continue to monitor service health. This incident has been resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, SDK Data Collection, SDK Data Collection, Data Processing, Data Processing, REST APIs, REST APIs, Outbound Messaging, Outbound Messaging, Currents, Currents, Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-02 17:20 UTC

   We're investigating an issue impacting services on the US01 and US05 clusters. A further update will be provided shortly.

2. monitoring 2025-09-02 17:30 UTC

   Between 13:08 ET to 13:21 users may have experienced an increase in latency and dashboard errors. We can confirm other services were not impacted by the issue.

3. resolved 2025-09-02 17:45 UTC

   We can confirm this incident is resolved and no further issues have been experienced since 13:21 ET.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: SMS

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-08-28 19:06 UTC

   Braze Engineers have identified an issue with SMS delivery Delays and failures to multiple networks in US for a subset of short codes. Braze Engineers have confirmed this appears to be related to an ongoing Twilio incident: https://status.twilio.com/incidents/rh2bywf4s0nv We...

2. identified 2025-08-28 19:46 UTC

   Braze Engineers are working with Twilio to determine the complete scope of impact to Braze services and US customers. We will continue monitoring the situation and provide an update when more information becomes available.

3. monitoring 2025-08-28 21:12 UTC

   We are experiencing recovery in SMS delivery delays and failures due to an external Twilio issue, impacting our downstream services for some US short codes. Braze Engineers will continue to monitor the situation and provide an update when more information becomes available.

4. resolved 2025-08-28 22:58 UTC

   SMS functionality has been restored to normal operations for all affected short codes on US carrier networks. The service disruption, caused by a Twilio incident, has been fully resolved. We continue monitoring to ensure optimal performance.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, Dashboard, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-08-21 19:15 UTC

   Braze Engineers are currently investigating increased latency in the REST APIs.

2. investigating 2025-08-21 19:16 UTC

   We are continuing to investigate this issue.

3. investigating 2025-08-21 19:23 UTC

   Braze Engineers continue to investigate increased latency in the REST APIs and SDK Data Collection across all US clusters.

4. monitoring 2025-08-21 19:50 UTC

   Braze REST and SDK services in the US were affected by a Cloudflare incident, for which Cloudflare has recently implemented a fix: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2. We can confirm resolution and are no longer seeing latency issues. Customers may have...

5. monitoring 2025-08-21 19:54 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-08-21 20:05 UTC

   Braze Engineers have confirmed US clusters are operating within normal operational bounds. Engineers will continue to monitor service health across all US clusters. This incident has been resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, SDK Data Collection, SDK Data Collection, REST APIs, REST APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-19 14:00 UTC

   Braze Engineers are currently investigating an issue impacting US06 AND EU02 services.

2. identified 2025-08-19 14:23 UTC

   Braze Engineers have identified the root cause of the issue and are implementing a fix.

3. identified 2025-08-19 14:40 UTC

   Issue Resolved - EU02 Cluster We have confirmed that the implemented fix has successfully resolved the service disruption affecting the EU02 cluster. All services including REST API, SDK, and Dashboard access have been restored and are operating normally. US06 Cluster remains...

4. monitoring 2025-08-19 15:01 UTC

   US06 Cluster The fixes have been implemented for both EU02 and US06 clusters. All services (REST API, SDK, and Dashboard access) currently function normally. We will continue to monitor.

5. resolved 2025-08-19 15:41 UTC

   Braze Engineers continue to monitor service health. Both US06 and EU02 services are operating within normal operational bounds. This incident has been resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Data Processing, Outbound Messaging

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-30 14:49 UTC

   We have identified degraded performance between 2:05 PM and 2:28 PM UTC, which impacted Outbound Messaging and Data Processing on the EU01 cluster. This issue is now resolved, and Engineers are continuing to monitor services.

2. monitoring 2025-07-30 15:18 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-07-30 15:19 UTC

   Engineers have continuously been monitoring services, and they have remained stable. This issue is now considered fully resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: SMS, WhatsApp

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-07-17 20:22 UTC

   Braze Engineers have identified an issue impacting the SMS Link Shortening service. During this time SMS messages containing shorted URL's may experience sending delays. End-users may experience a http 500 error when clicking a shortened URL.

2. identified 2025-07-17 20:31 UTC

   Following our previous communication, Braze Engineers have identified that the Link Shortening service issue also impacts WhatsApp. During this time, SMS and WhatsApp messages containing shortened and tracked URLs may experience sending delays. End-users may experience a HTTP...

3. monitoring 2025-07-17 20:59 UTC

   The Link-Shortening service has been restored. The SMS and WhatsApp message backlog has cleared and is now sending in real-time. End-users are able to click shortened and tracked links, redirecting to URLs as expected.

4. resolved 2025-07-17 21:12 UTC

   Services have remained stable, and this incident is now considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Data Processing, Outbound Messaging

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-11 07:43 UTC

   Our engineering team is investigating elevated Messaging Sending and Data Processing latency affecting the US01 cluster. We are actively working to identify the root cause and implement a resolution as quickly as possible.

2. monitoring 2025-07-11 07:57 UTC

   Braze Engineers have implemented a fix for the issue, and we are observing improvements in processing speed. Engineers are now working to process the backlog of messages.

3. resolved 2025-07-11 08:19 UTC

   The backlog of messages has now been processed. The incident is now considered resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, SDK Data Collection, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, Data Processing, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, REST APIs, Outbound Messaging, Outbound Messaging, Outbound Messaging, REST APIs, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Outbound Messaging, Push Notifications - Android

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS, Cloudflare, Google Cloud.

1. investigating 2025-06-12 19:01 UTC

   There appears to be a widespread internet issue affecting multiple services around the internet. Cloudflare, a Braze sub-processor, is having an incident (https://www.cloudflarestatus.com/incidents/25r9t0vz99rp) and Google Cloud is having a major outage...

2. identified 2025-06-12 19:52 UTC

   The Google Cloud outage is preventing our ability to scale up our kubernetes clusters. As a result, customers will experience message sending and data processing latency until this recovers. We are also seeing SDK API errors across multiple clusters.

3. identified 2025-06-12 20:30 UTC

   Multiple Braze Services are experiencing degradation due to the aforementioned incident with Cloudflare and Google Cloud Platform. While all services are available and operating correctly, we are unable to scale up our infrastructure and have taken some precautions to prevent a...

4. identified 2025-06-12 20:38 UTC

   Our SDK API has resumed normal processing. Events and attribute updates will not be lost; we now are automatically retrying and processing those events. Dashboard login services have now recovered, and users can log in through https://dashboard.braze.com.

5. identified 2025-06-12 20:43 UTC

   We are now actively scaling up our infrastructure and expect to return to normal performance soon. As this happens, the Outbound Messaging and Data Processing backlog is being worked on. We expect latency to dissipate as we process through the queue.

6. identified 2025-06-12 20:46 UTC

   We continue to see signs of recovery and are ramping services back to normal as we are able to. Our REST APIs are operational; however, as some inbound internet traffic remains challenged, some requests may have timed out before they get to Braze. Per standard practice, any REST...

7. identified 2025-06-12 20:58 UTC

   Our infrastructure has fully scaled up, so we are processing well above our typical speeds to work through the backlogs. Several of our clusters are now fully operational, as the Data Processing and Outbound Messaging backlogs have been fully processed. US-01, US-02, US-03,...

8. identified 2025-06-12 21:07 UTC

   Google has confirmed that Android Push / Firebase messaging is fully operational, and backlogs have been processed.

9. identified 2025-06-12 21:13 UTC

   US-06 is now fully recovered. Data Processing and Outbound Messaging backlogs have been fully processed.

10. resolved 2025-06-12 21:30 UTC

    EU-01 is now fully recovered. Data Processing and Outbound Messaging backlogs have been fully processed. With that, Braze is fully operational.

Excerpts are shortened. Read the full incident on Braze's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-21 15:30 UTC

   We experienced a service degradation on the US-01 cluster between 11:46 ET and 11:58 ET. During this 12-minute period, SDK API and Dashboard services hosted on the US-01 cluster were impacted by increased errors. SDK API errors were successfully retried. Our engineering team...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-04-23 22:09 UTC

   Braze has identified an issue impacting email latency for customers utilising Sendgrid as an Email Service Provider (ESP). Sendgrid has updated their Statuspage, communicating the issue here: https://status.sendgrid.com/incidents/6fj45kvpw8n3. Braze is actively monitoring the...

2. monitoring 2025-04-23 22:44 UTC

   Our internal monitoring shows that latency has returned to normal levels as of ~6:30 pm ET. Emails previously delayed have been processed, and no customers have queued messages. No messages were lost. Twilio Sendgrid confirmed to Braze at 6:42 ET that this is what they are...

3. resolved 2025-04-23 23:14 UTC

   Twilio SendGrid has confirmed that it understands the root cause. They have mitigated that and are confident that this issue will not recur. Their engineers are working toward a long-term fix. Please refer to SendGrid's Statuspage for additional details:...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Email, SMS, In-App Messaging, WhatsApp, Push Notifications - iOS, Push Notifications - Android, Content Cards

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-04-15 22:45 UTC

   Issue Overview On April 11th, 2025, we released an update that inadvertently introduced a bug affecting Canvas configurations. Unfortunately, this update erroneously added Exit Criteria filters to Canvas Entry Criteria filters for active Canvases with Exit Criteria. This...

2. monitoring 2025-04-16 02:39 UTC

   Earlier this evening, our engineering team completed the impact analysis from this issue, which caused some Canvases that had Exit Criteria to not enter new users. As of approximately 7:30pm ET, we had restored more than 99% of the impacted Canvases to their original and correct...

3. resolved 2025-04-16 16:23 UTC

   Our engineering team has completed all necessary restorations for the Canvases affected by the Exit Criteria issue. As of 7:30pm ET yesterday, we had successfully restored more than 99% of impacted Canvases to their correct state. We are now working directly with the remaining...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, SDK Data Collection, Data Processing, REST APIs, Outbound Messaging, Currents, Cloud Data-Ingestion (CDI)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-04-03 17:12 UTC

   Braze Engineers are currently investigating an issue impacting US01 services.

2. monitoring 2025-04-03 17:26 UTC

   Braze Engineers are investigating an issue impacting Data Processing of the US01 cluster starting at 12:45 ET. Customers may have experienced errors and latency impacting the Dashboard, SDK Data Collection, REST APIs, Outbound Messaging, and Currents. At this time services have...

3. monitoring 2025-04-03 17:52 UTC

   All Braze services are stable. Engineering is focused on processing the backlog of Outbound Messages. Following further triage of the issue, we can confirm during the incident windows, the following services were NOT impacted: - Dashboard - REST API's - Currents - CDI We can...

4. resolved 2025-04-03 18:12 UTC

   We apologize for mischaracterizing the impact of the outage in the original updates. We confirm that the incident is now resolved and that the impact was minor. During the incident window (12:45 to 14:00 ET) customers may have experienced the following: SDK Data Collection...

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Currents, Currents, Currents, Currents, Currents, Currents, Currents, Currents, Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-19 18:53 UTC

   Third-party Snowflake is currently experiencing an issue. As a result of this outage, customers may experience an impact on various functionalities within the Braze dashboard, including Query Builder, SQL Segments, Segment Extensions, Data Sharing configuration, and certain...

2. resolved 2025-03-19 21:49 UTC

   Snowflake has confirmed the incident they were experiencing is resolved. Braze can confirm all services are now healthy and working within normal operational bounds.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard, Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-10 15:10 UTC

   Users may experience errors when accessing the Drag & Drop editor from the Braze dashboard. This is due to an issue impacting our partner Beefree. We are working with Beefree to restore normal service as quickly as possible. Please refer to the Beefree status page for...

2. monitoring 2025-03-10 16:37 UTC

   Beefree identified the root cause of the issue and implemented a solution to address the intermittent issues affecting the Drag & Drop editor. Currently, the Drag & Drop editor is working as expected. Please refer to the Beefree status page for more information:...

3. resolved 2025-03-10 17:31 UTC

   We have confirmed with our partner Beefree, that the Drag & Drop editors are functioning as expected. This issue is now resolved.

Excerpts are shortened. Read the full incident on Braze's status page.

Affected: Outbound Messaging, Outbound Messaging, Currents, Currents, Cloud Data-Ingestion (CDI), Cloud Data-Ingestion (CDI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-03-10 04:27 UTC

   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.

2. identified 2025-03-10 05:06 UTC

   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.

3. identified 2025-03-10 06:17 UTC

   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.

4. identified 2025-03-10 07:11 UTC

   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.

5. identified 2025-03-10 08:16 UTC

   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...

6. identified 2025-03-10 11:15 UTC

   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.

7. identified 2025-03-10 12:56 UTC

   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.

8. identified 2025-03-10 15:47 UTC

   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...

9. identified 2025-03-10 16:35 UTC

   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...

10. monitoring 2025-03-10 18:48 UTC

    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.

11. monitoring 2025-03-10 19:01 UTC

    We are continuing to monitor for any further issues.

12. resolved 2025-03-10 22:21 UTC

    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...

Excerpts are shortened. Read the full incident on Braze's status page.