Historial de interrupciones de Braze

1. September 2, 2026 at 11:30 AM UTCidentified

   Estamos investigando errores intermitentes y latencia que afectan al Dashboard US07.

2. September 2, 2026 at 11:58 AM UTCresolved

   Esta fue una repetición de un problema anterior que impactó al Dashboard. Se ha aplicado un arreglo permanente y el Dashboard ha permanecido estable desde entonces. Confiamos en que la cuestión se resuelva plenamente. Nos disculpamos por cualquier impacto.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 2, 2026 at 7:43 AM UTCinvestigating

   Nuestro equipo de Ingeniería está investigando latencia intermitente y errores en el panel US07.

2. September 2, 2026 at 8:58 AM UTCidentified

   Hemos identificado la cuestión que conduce a errores intermitentes de panel de control y la latencia y los ingenieros están trabajando para resolver el problema.

3. September 2, 2026 at 9:36 AM UTCmonitoring

   Los ingenieros han implementado una solución y el Dashboard ha estado estable durante más de 30 minutos. Seguimos vigilando la cuestión para garantizar la plena resolución.

4. September 2, 2026 at 10:09 AM UTCresolved

   El Dashboard ha seguido siendo estable y la cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 5, 2026 at 4:13 PM UTCinvestigating

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

2. August 5, 2026 at 5:54 PM UTCresolved

   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 have remained stable for the past hour. This incident is now resolved.

1. July 31, 2026 at 2:09 PM UTCinvestigating

   Actualmente estamos investigando el rendimiento degradado en nuestro grupo EU02, que está causando retrasos en el procesamiento de Corrientes para un pequeño subconjunto de clientes. No se han perdido datos, y la mayoría de los datos de Corrientes siguen fluyendo normalmente. Nuestro equipo está trabajando activamente para una resolución y proporcionará actualizaciones a medida que estén disponibles.

2. July 31, 2026 at 4:14 PM UTCidentified

   Seguimos investigando el rendimiento degradado en EU02. Hemos identificado la causa raíz de la latencia subyacente, que se deriva de múltiples conectores de Corrientes que no se reinician con gracia después del mantenimiento rutinario, pero apareciendo en un estado saludable en nuestro sistema de monitoreo. Esos servidores específicos construyen atrasos significativos mientras que en este estado. Hemos completado un buen reinicio, y hemos aumentado recursos adicionales para procesar a través de los elementos backlogged más rápidamente. En este punto ~95% de los datos fluyen normalmente, mientras que hasta ~5% de nuestros conectores, impactando un subconjunto de clientes, continúan experimentando latencia. Vemos el rendimiento significativamente mejorado debido a cambios de configuración, y proporcionará una actualización en 1 hora o cuando tenemos un cronograma actualizado.

3. July 31, 2026 at 6:04 PM UTCidentified

   Seguimos desbloqueando el retraso restante en la EU02, mejorando nuestro rendimiento y disminuyendo la latencia general. Esperamos estar atrapados en la próxima hora, aunque un pequeño número de eventos puede tardar un poco más en procesar completamente. El impacto restante se limita a menos de medio por ciento de nuestro tráfico general. Vamos a proporcionar otra actualización una vez que estamos completamente atrapados.

4. July 31, 2026 at 7:25 PM UTCresolved

   Este incidente está resuelto. A partir de 15:18 ET / 19:18 UTC, hemos procesado completamente el atraso de los trabajos, y nuestros conectores EU02 Currents se procesan de nuevo dentro de rangos normales de latencia. No se perdieron datos, y todos los eventos de Currents han sido enviados a sus destinos.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 7:54 PM UTCresolved

   Aproximadamente a las 7:30 AM ET, nos dimos cuenta de un outage de redes AWS en la región US-WEST-2 que afecta la conectividad de red entre las 6:55 AM ET y las 8:00 AM ET. AWS ha resuelto desde entonces la cuestión subyacente. Durante la ventana de impacto, algunos clientes pueden haber experimentado retrasos intermitentes y latencia en la entrega de correo electrónico. El correo está siendo entregado normalmente. A medida que aumenta la profundidad de la cola, algunos clientes pueden haber experimentado retrasos residuales en la entrega de mensajes. Estos retrasos se han resuelto a partir de las 2:40 PM ET de hoy. Esta perturbación se originó en la infraestructura de AWS y no fue causada por ningún componente de la plataforma Braze. Quienes deseen más información sobre el incidente de la AWS pueden consultar la página del estado de la AWS: https://health.aws.amazon.com/health/status

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 6:43 PM UTCinvestigating

   Braze engineers have identified an issue affecting the Braze AI Operator, where users may see the following error message: "Connection unstable - Check your Wi-Fi or internet signal and try again". We are actively investigating the issue and will provide updates as more information becomes available.

2. July 13, 2026 at 8:54 PM UTCmonitoring

   A fix is being deployed for the issue affecting the Braze AI Operator, where users were seeing the error message: "Connection unstable - Check your Wi-Fi or internet signal and try again." We are seeing error rates improve and are continuing to monitor closely to confirm full resolution. We will provide a further update once we can confirm the issue is fully resolved.

3. July 13, 2026 at 9:31 PM UTCresolved

   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.

1. June 12, 2026 at 2:58 PM UTCidentified

   Meta, a third-party, is currently experiencing an issue impacting WhatsApp services. During this time, WhatsApp messages may experience latency. Campaign and Canvas creation or modification may experience errors and latency when utilizing WhatsApp templates. Audience sync to Facebook may also experience errors and latency during this period.

2. June 12, 2026 at 4:52 PM UTCmonitoring

   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. June 12, 2026 at 6:13 PM UTCresolved

   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.

1. May 22, 2026 at 5:45 PM UTCinvestigating

   Starting at 1:00 PM ET, customers on our US-01 and EU-01 clusters are experiencing elevated latency affecting campaign and Canvas processing, data ingestion, and message sending. Our engineering team is actively investigating, and we will provide updates as the situation develops.

2. May 22, 2026 at 6:17 PM UTCinvestigating

   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. May 22, 2026 at 6:34 PM UTCmonitoring

   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. May 22, 2026 at 6:41 PM UTCresolved

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

1. May 8, 2026 at 4:35 AM UTCidentified

   Starting at 11:45 PM ET, Braze customers on our US05 have been experiencing latency across campaign/canvas processing, data processing, and message sending due to an ongoing issue with an upstream provider (AWS). We are working on a fix. Please see https://health.aws.amazon.com/health/status for more details.

2. May 8, 2026 at 5:04 AM UTCidentified

   We are continuing to experience delays in Campaign & Canvas Processing, Data Processing, and Message Sending. Additionally, Dashboard navigation is intermittently erroring. We are continuing to work on a fix while we await updates from AWS. Please see https://health.aws.amazon.com/health/status for more details.

3. May 8, 2026 at 5:32 AM UTCmonitoring

   We have implemented a fix to mitigate the impact of the ongoing AWS incident in Availability Zone (use1-az4) in the US-EAST-1 region. At this point, latency and error rates have returned to normal levels for all services. Additionally, AWS is reporting early signs of recovery. Please see https://health.aws.amazon.com/health/status for more details.

4. May 8, 2026 at 5:47 AM UTCresolved

   Latency and error rates have remained at normal levels for all services, post-implementation of our fix, and this incident is resolved. We will continue to monitor the overall system health until AWS reports full recovery. Please see https://health.aws.amazon.com/health/status for more details.

1. May 7, 2026 at 4:38 PM UTCidentified

   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. May 7, 2026 at 4:53 PM UTCmonitoring

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

3. May 7, 2026 at 5:19 PM UTCresolved

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

1. May 7, 2026 at 1:19 PM UTCidentified

   Braze Engineers have identified an issue causing SMS delivery delays across networks in multiple European countries. Braze Engineers confirmed this is related to an ongoing Twilio incident: https://status.twilio.com/incidents/shhrhbqxflt1 We expect to provide another update as soon as more information becomes available.

2. May 7, 2026 at 5:10 PM UTCidentified

   Braze Engineers continue to monitor the ongoing SMS delivery delays affecting multiple networks across European countries. This remains related to an active Twilio incident, and our team is closely tracking their progress. Twilio has identified the cause and is actively working to resolve the issue. We will provide another update as soon as the situation changes. For real-time updates from Twilio, please refer to: https://status.twilio.com/incidents/shhrhbqxflt1

3. May 8, 2026 at 12:44 AM UTCmonitoring

   Braze Engineers continue to monitor the ongoing SMS delivery delays affecting multiple networks across European countries. This remains an active Twilio incident, and our team is closely tracking their progress. Twilio has identified the cause and is actively working to resolve the issue. They state that delivery delays to multiple networks continue in Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde. The incident has been resolved, and latency has returned to normal in all other countries. Braze's next update on the issue will be 10 UTC on 9 May 2026. For real-time updates from Twilio, please refer to: https://status.twilio.com/incidents/shhrhbqxflt1

4. May 8, 2026 at 11:46 AM UTCmonitoring

   SMS sending delays have been resolved for the majority of countries and sending has returned to normal. SMS delivery delays continue to impact Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde. For real-time updates from Twilio, please refer to: https://status.twilio.com/incidents/shhrhbqxflt1

5. May 8, 2026 at 12:36 PM UTCresolved

   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

1. April 20, 2026 at 4:18 PM UTCinvestigating

   We are currently investigating an issue with the EU01 cluster.

2. April 20, 2026 at 4:49 PM UTCidentified

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

3. April 20, 2026 at 5:13 PM UTCmonitoring

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

4. April 20, 2026 at 5:33 PM UTCmonitoring

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

5. April 20, 2026 at 6:02 PM UTCmonitoring

   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. April 20, 2026 at 7:24 PM UTCresolved

   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.

1. April 17, 2026 at 10:19 PM UTCresolved

   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.

1. April 8, 2026 at 7:05 PM UTCinvestigating

   We are currently experiencing an issue where cases sent to [email protected] may not be created as expected. Our team is actively investigating the issue. In the meantime, if you require assistance, please submit your request via the Braze Support Portal or reach out to your Customer Success Manager. We will provide an update as soon as more information becomes available.

2. April 8, 2026 at 7:44 PM UTCidentified

   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. April 8, 2026 at 8:34 PM UTCidentified

   We are continuing to investigate this incident. Both Google Workspace and Salesforce's Email-to-Case functionality are reporting issues related to the processing of email. New cases created by emailing support@braze as well as responses on existing cases are not being processed. In the meantime please submit your request by clicking "Get Help" in the top-right corner of your Braze workspace. Alternatively, your CSM may also be able to support.

4. April 8, 2026 at 9:27 PM UTCmonitoring

   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. April 8, 2026 at 9:49 PM UTCresolved

   The issue affecting email processing for support cases has been resolved. New cases sent to [email protected] 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. Thank you for your patience while we worked through this.

1. April 6, 2026 at 10:36 PM UTCresolved

   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.

1. March 24, 2026 at 5:45 PM UTCinvestigating

   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. March 24, 2026 at 5:50 PM UTCmonitoring

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

3. March 24, 2026 at 5:58 PM UTCresolved

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

1. March 20, 2026 at 6:25 PM UTCinvestigating

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

2. March 20, 2026 at 7:19 PM UTCmonitoring

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

3. March 20, 2026 at 7:29 PM UTCresolved

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

1. March 17, 2026 at 8:49 PM UTCinvestigating

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

2. March 17, 2026 at 8:57 PM UTCmonitoring

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

3. March 17, 2026 at 9:04 PM UTCresolved

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

1. February 24, 2026 at 7:34 PM UTCinvestigating

   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 follow their Statuspage for updates, and we'll update here in 30 minutes, or when we learn more. https://status.sparkpost.com/incidents/ndjn00g5vwm3

2. February 24, 2026 at 7:42 PM UTCinvestigating

   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. February 24, 2026 at 8:00 PM UTCresolved

   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 automatically retried. This incident is considered resolved.

1. February 18, 2026 at 12:07 PM UTCinvestigating

   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. February 18, 2026 at 12:39 PM UTCinvestigating

   We are continuing to investigate the issue.

3. February 18, 2026 at 3:20 PM UTCinvestigating

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

4. February 18, 2026 at 5:51 PM UTCidentified

   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. February 18, 2026 at 6:13 PM UTCmonitoring

   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. February 18, 2026 at 7:22 PM UTCresolved

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