Cronologia delle interruzioni di Braze

1. 2 settembre 2026 alle ore 11:30 UTCidentified

   Stiamo indagando sugli errori intermittenti e sulla latenza che colpisce la US07 Dashboard.

2. 2 settembre 2026 alle ore 11:58 UTCresolved

   Questa è stata una ricorrenza di un precedente problema che colpisce il Dashboard. Una fissazione permanente è stata implementata e il Dashboard è rimasto stabile da allora. Siamo fiduciosi che il problema sia ora pienamente risolto. Ci scusiamo per qualsiasi impatto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 2 settembre 2026 alle ore 07:43 UTCinvestigating

   Il nostro team di ingegneria sta indagando latenza intermittente e gli errori sulla US07 Dashboard.

2. 2 settembre 2026 alle ore 08:58 UTCidentified

   Abbiamo identificato il problema che porta a errori di dashboard intermittenti e latenza e gli ingegneri stanno lavorando per risolvere il problema.

3. 2 settembre 2026 alle ore 09:36 UTCmonitoring

   Gli ingegneri hanno implementato una correzione e il Dashboard è stato stabile per oltre 30 minuti. Stiamo continuando a monitorare il problema per garantire la piena risoluzione.

4. 2 settembre 2026 alle ore 10:09 UTCresolved

   Il Dashboard continua a rimanere stabile e il problema viene risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 5 agosto 2026 alle ore 16:13 UTCinvestigating

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

2. 5 agosto 2026 alle ore 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 luglio 2026 alle ore 14:09 UTCinvestigating

   Stiamo attualmente indagando sulle prestazioni degradate nel nostro cluster EU02, che sta causando ritardi nell'elaborazione delle correnti per un piccolo sottoinsieme di clienti. Nessun dato è stato perso, e la maggior parte dei dati correnti continua a scorrere normalmente. Il nostro team sta lavorando attivamente verso una risoluzione e fornirà aggiornamenti come diventano disponibili.

2. 31 luglio 2026 alle ore 16:14 UTCidentified

   Continuiamo a indagare sulle prestazioni degradate nell'UE02. Abbiamo identificato la causa principale della latenza sottostante, che derivava da più connettori di Correnti che non riescono a riavviare con grazia dopo la manutenzione di routine, ma apparendo in uno stato sano nel nostro sistema di monitoraggio. Quei server specifici costruiscono backlog significativi mentre in questo stato. Abbiamo completato un riavvio aggraziato, e hanno spun up ulteriori risorse per elaborare attraverso gli articoli backlogged più rapidamente. A questo punto ~95% dei dati scorre normalmente, mentre fino al ~5% dei nostri connettori, impatto di un sottoinsieme di clienti, continuano a sperimentare la latenza. Vediamo il throughput notevolmente migliorato a causa di modifiche di configurazione, e fornirà un aggiornamento in 1 ora o quando abbiamo una timeline aggiornata.

3. 31 luglio 2026 alle ore 18:04 UTCidentified

   Continuiamo a fare progressi nella compensazione del restante backlog su EU02, migliorando le nostre prestazioni e diminuendo la latenza generale. Ci aspettiamo di essere catturati entro l'ora successiva, anche se un piccolo numero di eventi può richiedere un po 'più a lungo per elaborare completamente. L'impatto rimanente è limitato a meno di mezzo per cento del nostro traffico complessivo. Provvederemo un altro aggiornamento una volta che siamo completamente catturati.

4. 31 luglio 2026 alle ore 19:25 UTCresolved

   Questo incidente è risolto. A partire da 15:18 ET / 19:18 UTC, abbiamo completamente elaborato il backlog di lavori, e i nostri connettori EU02 Correnti sono tutti di nuovo elaborazione all'interno normali intervalli di latenza. Nessun dato è stato perso, e tutti gli eventi di Corrente sono stati inviati alle loro destinazioni.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 19:54 UTCresolved

   A circa 7:30 AM ET, siamo diventati consapevoli di un outage di rete AWS nella regione US-WEST-2 che interessa la connettività di rete tra le 6:55 AM ET e le 8:00 AM ET. Da allora AWS ha risolto il problema sottostante. Durante la finestra di impatto, alcuni clienti possono aver sperimentato ritardi intermittenti e latenza nella consegna e-mail. La posta viene consegnata normalmente. Mentre la profondità della coda è aumentata, alcuni clienti potrebbero avere avuto ritardi residui nella consegna dei messaggi. Questi ritardi sono stati risolti a partire da 2:40 PM ET oggi. Questa interruzione ha avuto origine nell'infrastruttura AWS e non è stata causata da alcun componente della piattaforma Braze. Per ulteriori dettagli sull'incidente di AWS, consultare la pagina di stato AWS: https://health.aws.amazon.com/health/status

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 17:19 UTCresolved

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

1. 7 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 16:18 UTCinvestigating

   We are currently investigating an issue with the EU01 cluster.

2. 20 aprile 2026 alle ore 16:49 UTCidentified

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

3. 20 aprile 2026 alle ore 17:13 UTCmonitoring

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

4. 20 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 17:50 UTCmonitoring

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

3. 24 marzo 2026 alle ore 17:58 UTCresolved

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

1. 20 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 19:29 UTCresolved

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

1. 17 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 21:04 UTCresolved

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

1. 24 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 12:39 UTCinvestigating

   We are continuing to investigate the issue.

3. 18 febbraio 2026 alle ore 15:20 UTCinvestigating

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

4. 18 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 19:22 UTCresolved

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