Braze Outage History

Started Nov 24, 2025, 11:26 AM UTC· resolved Nov 24, 2025, 12:09 PM UTC

1. investigating Nov 24, 2025, 11:26 AM UTC

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

2. monitoring Nov 24, 2025, 11:51 AM 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 Nov 24, 2025, 12:09 PM UTC

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

Read the full incident report →

Started Nov 19, 2025, 12:34 AM UTC· resolved Nov 19, 2025, 01:33 AM UTC

1. identified Nov 19, 2025, 12:34 AM 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 Nov 19, 2025, 01:17 AM 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 Nov 19, 2025, 01:33 AM UTC

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

Read the full incident report →

Started Nov 18, 2025, 10:24 PM UTC· resolved Nov 18, 2025, 10:35 PM UTC

1. monitoring Nov 18, 2025, 10:24 PM 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 Nov 18, 2025, 10:35 PM UTC

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

Read the full incident report →

Started Nov 04, 2025, 09:00 PM UTC· resolved Nov 04, 2025, 09:00 PM UTC

1. resolved Nov 04, 2025, 09:47 PM 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 navigating and accessing the Dashboard. All other services remained functional, all REST and SDK API requests were processed, campaign and canvas execution continued to function. No messages were dropped.

Read the full incident report →

Started Oct 22, 2025, 11:19 PM UTC· resolved Oct 22, 2025, 11:48 PM UTC

1. monitoring Oct 22, 2025, 11:19 PM 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 Oct 22, 2025, 11:48 PM 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.

Read the full incident report →

Started Oct 20, 2025, 09:52 AM UTC· resolved Oct 20, 2025, 11:41 PM UTC

1. identified Oct 20, 2025, 09:52 AM 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 into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users Additionally, some customers may experience issues with SSO login due their SSO provider experiencing issues. We are continuing to monitor internal and external services. We apologise for the delay in updating the StatusPage, this was due to the outage also impacting the StatusPage service.

2. identified Oct 20, 2025, 10:40 AM 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 clusters. This is due to AWS being unable to provide enough capacity. Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users Additionally, some customers may experience issues with SSO login due their SSO provider experiencing issues.

3. identified Oct 20, 2025, 10:57 AM 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 following clusters due to AWS capacity issues: - US01 -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users Additionally, some customers may experience issues with SSO login due their SSO provider experiencing issues.

4. identified Oct 20, 2025, 11:23 AM 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 following clusters due to AWS capacity issues: - US01 - US02 (Outbound Messaging only) -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users Additionally, some customers may experience issues with SSO login due their SSO provider experiencing issues.

5. identified Oct 20, 2025, 12:15 PM 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 following clusters due to AWS capacity issues: - US01 - US02 (Outbound Messaging only) -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

6. identified Oct 20, 2025, 12:47 PM 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 following clusters due to AWS capacity issues: -US01 -US02 (Outbound Messaging only) -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

7. identified Oct 20, 2025, 01:13 PM 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 following clusters due to AWS capacity issues: -US01 -US02 (Data Processing and Outbound Messaging) -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

8. identified Oct 20, 2025, 01:48 PM 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 operation.

9. identified Oct 20, 2025, 02:12 PM 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 following clusters due to AWS capacity issues: -US01 -US02 (Data Processing and Outbound Messaging) -US03 -US04 -US05 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

10. identified Oct 20, 2025, 02:42 PM 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 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

11. identified Oct 20, 2025, 03:02 PM 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 operation.

12. identified Oct 20, 2025, 04:21 PM 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 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

13. identified Oct 20, 2025, 05:03 PM 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 -US06 Third-party SMS provider Twilio is affected by this outage. Braze customers may experience the following issues: - Difficulty logging into the Braze dashboard via SMS authentication - Issues sending SMS messages through the Braze platform - Issue receiving SMS responses from end users

14. identified Oct 20, 2025, 05:33 PM 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 monitor and manage the situation. As more capacity becomes available, when we see a change in our processing latency we'll provide another update.

15. identified Oct 20, 2025, 05:50 PM 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 Oct 20, 2025, 07:06 PM 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. We'll continue to load balance our work to protect system health, as our engineers continue to closely monitor and manage the situation

17. identified Oct 20, 2025, 07:59 PM 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 We'll continue to load balance our work to protect system health, as our engineers continue to closely monitor and manage the situation.

18. identified Oct 20, 2025, 08:18 PM 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 the situation.

19. identified Oct 20, 2025, 08:47 PM 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 Oct 20, 2025, 09:44 PM 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 when we have a material update.

21. resolved Oct 20, 2025, 11:41 PM 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 systems are operating normally. Our engineering teams will continue standard monitoring.

Read the full incident report →

Started Oct 08, 2025, 10:00 AM UTC· resolved Oct 08, 2025, 10:00 AM UTC

1. resolved Nov 05, 2025, 09:34 PM 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 to implement the fix. Dashboard access was fully restored as of 12:43 PM ET.

Read the full incident report →

Started Sep 09, 2025, 07:07 PM UTC· resolved Sep 09, 2025, 07:30 PM UTC

1. identified Sep 09, 2025, 07:07 PM 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 Braze services downstream. We are actively monitoring the situation and working to mitigate the impact on our customers. We will provide updates as more information becomes available. https://www.cloudflarestatus.com/incidents/9pvscr0vmsy6

2. monitoring Sep 09, 2025, 07:20 PM 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 Sep 09, 2025, 07:30 PM 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.

Read the full incident report →

Started Sep 05, 2025, 05:54 PM UTC· resolved Sep 05, 2025, 06:01 PM UTC

1. monitoring Sep 05, 2025, 05:54 PM 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 customers may have experienced intermittent errors accessing the dashboard between approximately 12:15PM to 1:15PM EST. In addition, some time series graphs may have experienced latency updating between approximately 1:00PM to 1:24PM.

2. resolved Sep 05, 2025, 06:01 PM 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.

Read the full incident report →

Started Sep 02, 2025, 05:20 PM UTC· resolved Sep 02, 2025, 05:45 PM UTC

1. identified Sep 02, 2025, 05:20 PM UTC

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

2. monitoring Sep 02, 2025, 05:30 PM 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 Sep 02, 2025, 05:45 PM UTC

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

Read the full incident report →

Started Aug 28, 2025, 07:06 PM UTC· resolved Aug 28, 2025, 10:58 PM UTC

1. identified Aug 28, 2025, 07:06 PM 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 expect to provide another update in 30 minutes or as soon as more information becomes available.

2. identified Aug 28, 2025, 07:46 PM 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 Aug 28, 2025, 09:12 PM 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 Aug 28, 2025, 10:58 PM 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.

Read the full incident report →

Started Aug 21, 2025, 07:15 PM UTC· resolved Aug 21, 2025, 08:05 PM UTC

1. investigating Aug 21, 2025, 07:15 PM UTC

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

2. investigating Aug 21, 2025, 07:16 PM UTC

   We are continuing to investigate this issue.

3. investigating Aug 21, 2025, 07:23 PM UTC

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

4. monitoring Aug 21, 2025, 07:50 PM 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 experienced increased latency when making API calls. Error rates for these API services remained low despite the increased latency, with less than 0.02% failing due to a timeout. As our documented best practices note, customers should retry REST API calls that returned a 50x error code. Our SDK API will automatically retry and process all events; no events were lost. We will continue monitoring the situation and provide an update in 30 minutes.

5. monitoring Aug 21, 2025, 07:54 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Aug 21, 2025, 08:05 PM 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.

Read the full incident report →

Started Aug 19, 2025, 02:00 PM UTC· resolved Aug 19, 2025, 03:41 PM UTC

1. investigating Aug 19, 2025, 02:00 PM UTC

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

2. identified Aug 19, 2025, 02:23 PM UTC

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

3. identified Aug 19, 2025, 02:40 PM 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 impacted - We are continuing to work on resolving the issue affecting this cluster and will provide updates as they become available.

4. monitoring Aug 19, 2025, 03:01 PM 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 Aug 19, 2025, 03:41 PM UTC

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

Read the full incident report →

Started Jul 30, 2025, 02:49 PM UTC· resolved Jul 30, 2025, 03:19 PM UTC

1. monitoring Jul 30, 2025, 02:49 PM 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 Jul 30, 2025, 03:18 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jul 30, 2025, 03:19 PM UTC

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

Read the full incident report →

Started Jul 17, 2025, 08:22 PM UTC· resolved Jul 17, 2025, 09:12 PM UTC

1. identified Jul 17, 2025, 08:22 PM 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 Jul 17, 2025, 08:31 PM 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 500 error when clicking on a shortened or tracked URL.

3. monitoring Jul 17, 2025, 08:59 PM 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 Jul 17, 2025, 09:12 PM UTC

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

Read the full incident report →

Started Jul 11, 2025, 07:43 AM UTC· resolved Jul 11, 2025, 08:19 AM UTC

1. investigating Jul 11, 2025, 07:43 AM 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 Jul 11, 2025, 07:57 AM 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 Jul 11, 2025, 08:19 AM UTC

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

Read the full incident report →

Started Jun 12, 2025, 07:01 PM UTC· resolved Jun 12, 2025, 09:30 PM UTC

1. investigating Jun 12, 2025, 07:01 PM 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 (https://status.cloud.google.com/). This is affecting our ability to deliver push notifications via Google Firebase. AWS is not provisioning new servers, which is preventing our ability to scale up, and may be related to this overall internet issue. We will provide additional updates soon.

2. identified Jun 12, 2025, 07:52 PM 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 Jun 12, 2025, 08:30 PM 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 cascading failure once the Google and Cloudflare incidents resolve and traffic starts flowing at higher rates again. Our SDK API is mostly returning error response codes to SDKs–this directs them to retry requests at a later time to throttle processing demand. Events and attribute updates will not be lost, and our SDKs will periodically retry requests automatically. Our REST APIs are operational; however, as inbound internet traffic is challenged, some requests may have timed out before they get to Braze. Per standard practice, any REST API calls that timeout or receive a 50X response code should be retried. Dashboard users may experience sporadic login timeouts when visiting https://dashboard.braze.com until upstream providers recover. Outbound messaging and data processing are continuing, but may experience latency until the incident is fully resolved upstream and Braze can re-scale our infrastructure. We are starting to see some signs of recovery and will be proactively ramping services back to normal behavior as we are able to. We will also continue to post regular updates.

4. identified Jun 12, 2025, 08:38 PM 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 Jun 12, 2025, 08:43 PM 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 Jun 12, 2025, 08:46 PM 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 API calls that timeout or receive a 50X response code should be retried.

7. identified Jun 12, 2025, 08:58 PM 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, US-04, US-05, US-07, and EU-02 are fully recovered.

8. identified Jun 12, 2025, 09:07 PM UTC

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

9. identified Jun 12, 2025, 09:13 PM UTC

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

10. resolved Jun 12, 2025, 09:30 PM UTC

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

Read the full incident report →

Started May 21, 2025, 03:30 PM UTC· resolved May 21, 2025, 03:30 PM UTC

1. resolved May 21, 2025, 06:11 PM 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 responded immediately when the issue was detected and restored full service functionality at 11:58 ET. All systems are now operating normally.

Read the full incident report →

Started Apr 23, 2025, 10:09 PM UTC· resolved Apr 23, 2025, 11:14 PM UTC

1. identified Apr 23, 2025, 10:09 PM 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 impact of the issue and working with Sendgrid to resolve.

2. monitoring Apr 23, 2025, 10:44 PM 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 expecting. We will continue to monitor this to ensure the issue does not recur until we have more details from Twilio.

3. resolved Apr 23, 2025, 11:14 PM 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: https://status.sendgrid.com/incidents/6fj45kvpw8n3

Read the full incident report →

Started Apr 15, 2025, 10:45 PM UTC· resolved Apr 16, 2025, 04:23 PM UTC

1. monitoring Apr 15, 2025, 10:45 PM 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 resulted in users who should have qualified for canvas steps being aborted out of impacted canvases and not receiving messages they otherwise qualified for. Current State and Next Steps The issue itself has been mitigated as of 15:28 UTC on Monday, April 14th, so that the unexpected behavior is no longer actively impacting new canvases. With respect to impacted canvases, we are still working to determine the full scope of the impact and the appropriate steps that can be taken to remediate that impact. We understand the impact that this has on you and are working urgently and with executive oversight to resolve all impacts as quickly as possible. Please know that this is a top priority for our engineering organization. We appreciate your partnership and patience while we continue to work through remediation of the remaining impact caused by this issue.

2. monitoring Apr 16, 2025, 02:39 AM 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 state. A small number of customers have received direct outreach from us regarding certain Canvases that were not modified by our team and we will handle next steps directly with them. We will continue monitoring and provide a final update in the morning Eastern time.

3. resolved Apr 16, 2025, 04:23 PM 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 affected customers to address their specific situations and will complete all customer communications by the end of the day. This incident is now resolved. We appreciate your patience throughout this process and apologize for any disruption this may have caused.

Read the full incident report →

Started Apr 03, 2025, 05:12 PM UTC· resolved Apr 03, 2025, 06:12 PM UTC

1. identified Apr 03, 2025, 05:12 PM UTC

   Braze Engineers are currently investigating an issue impacting US01 services.

2. monitoring Apr 03, 2025, 05:26 PM 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 stabilized and engineers continue working to ensure system stability.

3. monitoring Apr 03, 2025, 05:52 PM 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 confirm during the incident window the following Braze services experienced: - SDK Data Collection Errors - this will automatically retry and no action is needed by Braze customers - Outbound Messaging latency

4. resolved Apr 03, 2025, 06:12 PM 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 Errors - this will automatically retry and no action is needed by Braze customers Outbound Messaging latency

Read the full incident report →

Started Mar 19, 2025, 06:53 PM UTC· resolved Mar 19, 2025, 09:49 PM UTC

1. identified Mar 19, 2025, 06:53 PM 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 reporting features. Customers integrating Snowflake with CDI or Currents may also experience latencies and errors during this time.

2. resolved Mar 19, 2025, 09:49 PM 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.

Read the full incident report →

Started Mar 10, 2025, 03:10 PM UTC· resolved Mar 10, 2025, 05:31 PM UTC

1. identified Mar 10, 2025, 03:10 PM 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 information: https://beefree.statuspage.io/

2. monitoring Mar 10, 2025, 04:37 PM 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: https://beefree.statuspage.io/

3. resolved Mar 10, 2025, 05:31 PM UTC

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

Read the full incident report →

Started Mar 10, 2025, 04:27 AM UTC· resolved Mar 10, 2025, 10:21 PM UTC

1. identified Mar 10, 2025, 04:27 AM 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 Mar 10, 2025, 05:06 AM 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 Mar 10, 2025, 06:17 AM 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 Mar 10, 2025, 07:11 AM 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 Mar 10, 2025, 08:16 AM 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 CDI integrations. We appreciate your patience as we work to resolve these issues.

6. identified Mar 10, 2025, 11:15 AM 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 Mar 10, 2025, 12:56 PM 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 Mar 10, 2025, 03:47 PM 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 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.

9. identified Mar 10, 2025, 04:35 PM 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 operational bounds. Braze Engineers continue to work on processing the backlog of events impacted by the incident.

10. monitoring Mar 10, 2025, 06:48 PM 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 Mar 10, 2025, 07:01 PM UTC

    We are continuing to monitor for any further issues.

12. resolved Mar 10, 2025, 10:21 PM 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 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.

Read the full incident report →