Ιστορικό διακοπών του Braze

1. 2 Σεπτεμβρίου 2026 στις 11:30 π.μ. UTCidentified

   Ερευνούμε διαλείποντα σφάλματα και λανθάνουσα λανθάνουσας λανθάνουσας λανθάνουσας πτώσεως του πίνακα US07.

2. 2 Σεπτεμβρίου 2026 στις 11:58 π.μ. UTCresolved

   Αυτό ήταν μια επανάληψη ενός προγενέστερου θέματος που επηρέασε το Dashboard. Μια μόνιμη ρύθμιση έχει εφαρμοστεί και η Dashboard παραμένει σταθερή από τότε. Είμαστε πεπεισμένοι ότι το ζήτημα έχει πλέον επιλυθεί πλήρως. Ζητάμε συγγνώμη για οποιαδήποτε επίπτωση.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 2 Σεπτεμβρίου 2026 στις 7:43 π.μ. UTCinvestigating

   Η ομάδα μηχανικών μας ερευνά διαλείπουσα λανθάνουσα λανθάνουσα κατάσταση και λάθη στον πίνακα US07.

2. 2 Σεπτεμβρίου 2026 στις 8:58 π.μ. UTCidentified

   Έχουμε εντοπίσει το ζήτημα που οδηγεί σε διαλείποντα σφάλματα ταμπλό και λανθάνουσα λανθάνουσα και οι μηχανικοί εργάζονται για την επίλυση του ζητήματος.

3. 2 Σεπτεμβρίου 2026 στις 9:36 π.μ. UTCmonitoring

   Οι μηχανικοί έχουν εφαρμόσει ένα fix και ο πίνακας είναι σταθερός για πάνω από 30 λεπτά. Συνεχίζουμε να παρακολουθούμε το ζήτημα για να διασφαλίσουμε την πλήρη επίλυση.

4. 2 Σεπτεμβρίου 2026 στις 10:09 π.μ. UTCresolved

   Ο πίνακας έχει συνεχίσει να παραμένει σταθερός και το θέμα έχει πλέον επιλυθεί.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 5 Αυγούστου 2026 στις 4:13 μ.μ. UTCinvestigating

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

2. 5 Αυγούστου 2026 στις 5: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 Ιουλίου 2026 στις 2:09 μ.μ. UTCinvestigating

   Αυτή τη στιγμή διερευνούμε τις υποβαθμισμένες επιδόσεις στην ομάδα μας EU02, η οποία προκαλεί καθυστερήσεις στην επεξεργασία των ρευμάτων για ένα μικρό υποσύνολο πελατών. Δεν έχουν χαθεί δεδομένα και η πλειοψηφία των δεδομένων του ρεύματος συνεχίζει να ρέει κανονικά. Η ομάδα μας εργάζεται ενεργά προς μια λύση και θα παρέχει ενημερώσεις καθώς θα είναι διαθέσιμες.

2. 31 Ιουλίου 2026 στις 4:14 μ.μ. UTCidentified

   Συνεχίζουμε να ερευνούμε τις υποβαθμισμένες επιδόσεις στην ΕΕ02. Αναγνωρίσαμε τη βασική αιτία της υποκείμενης λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας λανθάνουσας . Αυτοί οι συγκεκριμένοι διακομιστές φτιάχνουν σημαντικά backlog ενώ βρίσκονται σε αυτή την κατάσταση. Έχουμε ολοκληρώσει μια χαριτωμένη επανεκκίνηση, και έχουμε δημιουργήσει επιπλέον πόρους για να επεξεργαστεί μέσω των backlogged στοιχεία πιο γρήγορα. Σε αυτό το σημείο ~95% των δεδομένων ρέει κανονικά, ενώ μέχρι ~5% των συνδέσεων μας, προσκρούοντας σε ένα υποσύνολο πελατών, συνεχίζουν να βιώνουν λανθάνουσα. Βλέπουμε το throughput να βελτιώνεται σημαντικά λόγω αλλαγών ρυθμίσεων, και θα παρέχει μια ενημέρωση σε 1 ώρα ή όταν έχουμε ένα ενημερωμένο χρονοδιάγραμμα.

3. 31 Ιουλίου 2026 στις 6:04 μ.μ. UTCidentified

   Συνεχίζουμε να σημειώνουμε πρόοδο όσον αφορά την εκκαθάριση των υπολοίπων πιστώσεων για την ΕΕ02, τη βελτίωση των επιδόσεών μας και τη μείωση της συνολικής καθυστέρησης. Αναμένουμε να προφτάσουμε μέσα στην επόμενη ώρα, αν και ένας μικρός αριθμός γεγονότων μπορεί να πάρει λίγο περισσότερο χρόνο για να επεξεργαστεί πλήρως. Οι υπόλοιπες επιπτώσεις περιορίζονται σε λιγότερο από το μισό τοις εκατό της συνολικής μας κυκλοφορίας. Θα δώσουμε νέα ενημέρωση μόλις μας προλάβουν.

4. 31 Ιουλίου 2026 στις 7:25 μ.μ. UTCresolved

   Το περιστατικό λύθηκε. Από τις 15:18 ET / 19:18 UTC, έχουμε επεξεργαστεί πλήρως το backlog των θέσεων εργασίας, και οι συνδετήρες ρευμάτων μας EU02 είναι και πάλι επεξεργασία εντός κανονικών ορίων λανθάνουσας ισχύος. Δεν χάθηκαν δεδομένα, και όλα τα γεγονότα του ρεύματος έχουν σταλεί στους προορισμούς τους.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 24 Ιουλίου 2026 στις 7:54 μ.μ. UTCresolved

   Περίπου στις 7:30 π.μ. ET, λάβαμε γνώση για διακοπή δικτύου AWS στην περιοχή ΗΠΑ-WEST-2 που επηρεάζει τη συνδεσιμότητα δικτύου μεταξύ 6:55 π.μ. ET και 8:00 π.μ. ET. Η AWS έχει από τότε επιλύσει το υποκείμενο ζήτημα. Κατά τη διάρκεια του παραθύρου πρόσκρουσης, μερικοί πελάτες μπορεί να έχουν βιώσει διαλείπουσες καθυστερήσεις και λανθάνουσα λανθάνουσα στην παράδοση ηλεκτρονικού ταχυδρομείου. Η αλληλογραφία τώρα παραδίδεται κανονικά. Καθώς αυξήθηκε το βάθος της ουράς, ορισμένοι πελάτες μπορεί να έχουν βιώσει υπολειπόμενες καθυστερήσεις στην παράδοση μηνυμάτων. Αυτές οι καθυστερήσεις έχουν επιλυθεί από τις 2:40 μμ ET σήμερα. Αυτή η διαταραχή προήλθε από την υποδομή AWS και δεν προκλήθηκε από καμία συνιστώσα της πλατφόρμας Braze. Για περισσότερες λεπτομέρειες σχετικά με το περιστατικό AWS, ανατρέξτε στη σελίδα κατάστασης AWS: https://health.aws.amazon.com/health/status

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 13 Ιουλίου 2026 στις 6: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 Ιουλίου 2026 στις 8: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 Ιουλίου 2026 στις 9: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 Ιουνίου 2026 στις 2: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 Ιουνίου 2026 στις 4: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 Ιουνίου 2026 στις 6: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 Μαΐου 2026 στις 5: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 Μαΐου 2026 στις 6: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 Μαΐου 2026 στις 6: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 Μαΐου 2026 στις 6: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 Μαΐου 2026 στις 4: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 Μαΐου 2026 στις 5: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 Μαΐου 2026 στις 5: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 Μαΐου 2026 στις 5: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 Μαΐου 2026 στις 4: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 Μαΐου 2026 στις 4: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 Μαΐου 2026 στις 5:19 μ.μ. UTCresolved

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

1. 7 Μαΐου 2026 στις 1: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 Μαΐου 2026 στις 5: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 Μαΐου 2026 στις 12: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 Μαΐου 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 Μαΐου 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 Απριλίου 2026 στις 4:18 μ.μ. UTCinvestigating

   We are currently investigating an issue with the EU01 cluster.

2. 20 Απριλίου 2026 στις 4:49 μ.μ. UTCidentified

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

3. 20 Απριλίου 2026 στις 5:13 μ.μ. UTCmonitoring

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

4. 20 Απριλίου 2026 στις 5: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 Απριλίου 2026 στις 6: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 Απριλίου 2026 στις 7: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 Απριλίου 2026 στις 10: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 Απριλίου 2026 στις 7: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 Απριλίου 2026 στις 7: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 Απριλίου 2026 στις 8: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 Απριλίου 2026 στις 9: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 Απριλίου 2026 στις 9: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 Απριλίου 2026 στις 10: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 Μαρτίου 2026 στις 5: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 Μαρτίου 2026 στις 5:50 μ.μ. UTCmonitoring

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

3. 24 Μαρτίου 2026 στις 5:58 μ.μ. UTCresolved

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

1. 20 Μαρτίου 2026 στις 6: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 Μαρτίου 2026 στις 7:19 μ.μ. UTCmonitoring

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

3. 20 Μαρτίου 2026 στις 7:29 μ.μ. UTCresolved

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

1. 17 Μαρτίου 2026 στις 8: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 Μαρτίου 2026 στις 8:57 μ.μ. UTCmonitoring

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

3. 17 Μαρτίου 2026 στις 9:04 μ.μ. UTCresolved

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

1. 24 Φεβρουαρίου 2026 στις 7: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 Φεβρουαρίου 2026 στις 7: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 Φεβρουαρίου 2026 στις 8: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 Φεβρουαρίου 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 Φεβρουαρίου 2026 στις 12:39 μ.μ. UTCinvestigating

   We are continuing to investigate the issue.

3. 18 Φεβρουαρίου 2026 στις 3:20 μ.μ. UTCinvestigating

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

4. 18 Φεβρουαρίου 2026 στις 5: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 Φεβρουαρίου 2026 στις 6: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 Φεβρουαρίου 2026 στις 7:22 μ.μ. UTCresolved

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