Historique des pannes de Braze

1. 2 septembre 2026 à 11:30 UTCidentified

   Nous enquêtons sur les erreurs intermittentes et la latence qui ont une incidence sur le tableau de bord US07.

2. 2 septembre 2026 à 11:58 UTCresolved

   Il s'agissait d'une récurrence d'un problème antérieur touchant le tableau de bord. Un correctif permanent a été mis en place et le tableau de bord est resté stable depuis. Nous sommes convaincus que la question est maintenant entièrement résolue. Nous nous excusons pour tout impact.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 septembre 2026 à 07:43 UTCinvestigating

   Notre équipe d'ingénierie enquête sur la latence intermittente et les erreurs sur le tableau de bord US07.

2. 2 septembre 2026 à 08:58 UTCidentified

   Nous avons identifié le problème qui entraîne des erreurs intermittentes dans le tableau de bord et des latences et les ingénieurs s'efforcent de résoudre le problème.

3. 2 septembre 2026 à 09:36 UTCmonitoring

   Les ingénieurs ont mis en place une solution et le tableau de bord est stable depuis plus de 30 minutes. Nous continuons de suivre la question afin d'assurer un règlement complet.

4. 2 septembre 2026 à 10:09 UTCresolved

   Le tableau de bord reste stable et la question est maintenant réglée.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 août 2026 à 16:13 UTCinvestigating

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

2. 5 août 2026 à 17:54 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. 31 juillet 2026 à 14:09 UTCinvestigating

   Nous enquêtons actuellement sur la dégradation des performances de notre grappe EU02, qui retarde le traitement des courants pour un petit sous-ensemble de clients. Aucune donnée n'a été perdue et la majorité des données sur les courants continuent de circuler normalement. Notre équipe travaille activement à une résolution et fournira des mises à jour à mesure qu'elles seront disponibles.

2. 31 juillet 2026 à 16:14 UTCidentified

   Nous continuons d'étudier la dégradation des performances dans EU02. Nous avons identifié la cause profonde de la latence sous-jacente, qui découle de plusieurs connecteurs de courant qui ne redémarrent pas gracieusement après maintenance courante, mais qui apparaissent dans un état sain dans notre système de surveillance. Ces serveurs spécifiques créent des arriérés importants dans cet état. Nous avons terminé un redémarrage gracieusement et avons créé des ressources supplémentaires pour traiter plus rapidement les articles en retard. À ce stade ~95% des données circulent normalement, tandis que jusqu'à ~5% de nos connecteurs, impactant un sous-ensemble de clients, continuent d'éprouver la latence. Nous voyons le débit considérablement amélioré en raison des changements de configuration, et fournira une mise à jour dans 1 heure ou lorsque nous avons un calendrier mis à jour.

3. 31 juillet 2026 à 18:04 UTCidentified

   Nous continuons de faire des progrès pour résorber l'arriéré restant sur EU02, améliorer nos performances et réduire la latence globale. Nous nous attendons à être rattrapés dans l'heure qui vient, bien qu'un petit nombre d'événements puissent prendre un peu plus de temps à traiter. L'impact restant est limité à moins d'un demi-pour cent de notre trafic global. Nous fournirons une autre mise à jour une fois que nous serons complètement rattrapés.

4. 31 juillet 2026 à 19:25 UTCresolved

   Cet incident est résolu. À partir de 15:18 ET / 19:18 UTC, nous avons complètement traité l'arriéré d'emplois, et nos connecteurs de courant EU02 sont tous à nouveau le traitement dans des plages de latence normales. Aucune donnée n'a été perdue, et tous les événements de Currents ont été envoyés à leurs destinations.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 19:54 UTCresolved

   Vers 7 h 30 HE, nous avons pris connaissance d'une panne de réseau AWS dans la région US-WEST-2 affectant la connectivité réseau entre 6 h 55 HE et 8 h HE. AWS a depuis résolu le problème sous-jacent. Pendant la fenêtre d'impact, certains clients ont peut-être connu des retards et des latences dans la livraison des courriels. Le courrier est maintenant livré normalement. Au fur et à mesure que la profondeur de la file d'attente augmente, certains clients peuvent avoir subi des retards résiduels dans la livraison des messages. Ces retards ont été résolus à partir de 14h40 HNE aujourd'hui. Cette perturbation provient de l'infrastructure AWS et n'a été causée par aucun élément de la plate-forme Braze. Pour plus de détails sur l'incident du SSFE, veuillez consulter la page d'état du SSFE : https://health.aws.amazon.com/health/status

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 13 juillet 2026 à 18:43 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. 13 juillet 2026 à 20:54 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. 13 juillet 2026 à 21:31 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. 12 juin 2026 à 14:58 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. 12 juin 2026 à 16:52 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. 12 juin 2026 à 18:13 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. 22 mai 2026 à 17:45 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. 22 mai 2026 à 18:17 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. 22 mai 2026 à 18:34 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. 22 mai 2026 à 18:41 UTCresolved

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

1. 8 mai 2026 à 04:35 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. 8 mai 2026 à 05:04 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. 8 mai 2026 à 05:32 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. 8 mai 2026 à 05:47 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. 7 mai 2026 à 16:38 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. 7 mai 2026 à 16:53 UTCmonitoring

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

3. 7 mai 2026 à 17:19 UTCresolved

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

1. 7 mai 2026 à 13:19 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. 7 mai 2026 à 17:10 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. 8 mai 2026 à 00:44 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. 8 mai 2026 à 11:46 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. 8 mai 2026 à 12:36 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. 20 avril 2026 à 16:18 UTCinvestigating

   We are currently investigating an issue with the EU01 cluster.

2. 20 avril 2026 à 16:49 UTCidentified

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

3. 20 avril 2026 à 17:13 UTCmonitoring

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

4. 20 avril 2026 à 17:33 UTCmonitoring

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

5. 20 avril 2026 à 18:02 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. 20 avril 2026 à 19:24 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. 17 avril 2026 à 22:19 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. 8 avril 2026 à 19:05 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. 8 avril 2026 à 19:44 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. 8 avril 2026 à 20:34 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. 8 avril 2026 à 21:27 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. 8 avril 2026 à 21:49 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. 6 avril 2026 à 22:36 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. 24 mars 2026 à 17:45 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. 24 mars 2026 à 17:50 UTCmonitoring

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

3. 24 mars 2026 à 17:58 UTCresolved

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

1. 20 mars 2026 à 18:25 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. 20 mars 2026 à 19:19 UTCmonitoring

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

3. 20 mars 2026 à 19:29 UTCresolved

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

1. 17 mars 2026 à 20:49 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. 17 mars 2026 à 20:57 UTCmonitoring

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

3. 17 mars 2026 à 21:04 UTCresolved

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

1. 24 février 2026 à 19:34 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. 24 février 2026 à 19:42 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. 24 février 2026 à 20:00 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. 18 février 2026 à 12:07 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. 18 février 2026 à 12:39 UTCinvestigating

   We are continuing to investigate the issue.

3. 18 février 2026 à 15:20 UTCinvestigating

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

4. 18 février 2026 à 17:51 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. 18 février 2026 à 18:13 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. 18 février 2026 à 19:22 UTCresolved

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