Braze 장애 기록

1. 2026년 9월 2일 AM 11:30 UTCidentified

   우리는 미국07 대시 보드에 영향을 미치는 간헐적 오류 및 대기 시간을 조사하고 있습니다.

2. 2026년 9월 2일 AM 11:58 UTCresolved

   이것은 대시보드에 영향을 미치는 이전 문제의 재발견이었다. 영구 수정이 구현되었으며 Dashboard는 안정적으로 유지되었습니다. 우리는 문제가 완전히 해결되었습니다. 우리는 어떤 충격든지를 위해 apologize.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 2일 AM 7:43 UTCinvestigating

   우리의 엔지니어링 팀은 US07 대시 보드에 대한 간헐적 인 대기 시간 및 오류를 조사하고 있습니다.

2. 2026년 9월 2일 AM 8:58 UTCidentified

   우리는 intermittent 대시보드 오류 및 대기 시간 및 엔지니어가 문제를 해결하기 위해 노력하고 있습니다.

3. 2026년 9월 2일 AM 9:36 UTCmonitoring

   엔지니어는 수정을 구현했으며 Dashboard는 30 분 이상 안정적으로 운영되었습니다. 전체 해상도를 보장하기 위해 문제가 계속됩니다.

4. 2026년 9월 2일 AM 10:09 UTCresolved

   Dashboard는 안정을 유지하고 문제가 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 5일 PM 4:13 UTCinvestigating

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

2. 2026년 8월 5일 PM 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. 2026년 7월 31일 PM 2:09 UTCinvestigating

   우리는 현재 EU02 클러스터의 향상된 성능을 조사하고 있으며, 고객의 작은 하위 세트에 대한 현재 처리 지연을 유발합니다. 데이터가 손실되지 않고, 현재 데이터의 대다수는 일반적으로 흐름을 계속합니다. 우리의 팀은 해결책에 적극적으로 일하고 그들이 유효한 것과 같이 갱신을 제공할 것입니다.

2. 2026년 7월 31일 PM 4:14 UTCidentified

   우리는 유럽 연합 (EU02)의 성적을 조사 계속합니다. 우리는 일상적인 정비 후에 우아한 재시작에 실패한 다수 현재 연결관에서 줄기로 뻗은 underlying latency의 뿌리 원인을, 그러나 우리의 감시 체계에 있는 건강한 국가에서 나타나는 것을 확인했습니다. 이러한 특정 서버는 이 상태에서 상당한 backlogs를 구축합니다. 우리는 우아한 재시작을 완료하고, backl에 의하여 기록된 품목을 더 급속하게 가공하는 추가 리소스를 회전시켰습니다. 이 시점에서 ~ 95 %의 데이터는 일반적으로 흐르는 반면, 우리의 커넥터의 최대 ~ 5 %가 고객의 하위 세트에 영향을 미치며 대기 시간을 계속 경험하십시오. 우리는 config 변경으로 인해 처리량을 크게 향상 시키며 1 시간 동안 업데이트를 제공하거나 업데이트 된 타임 라인이있을 때.

3. 2026년 7월 31일 PM 6:04 UTCidentified

   우리는 유럽 연합 (EU02)에 남아있는 백로를 명확하게하고, 우리의 성과를 개량하고, 전반적인 대기권을 감소시키기 위하여 계속합니다. 우리는 다음 시간 이내에 잡을 것으로 예상하지만, 작은 이벤트의 수는 완전히 공정에 약간 더 길게 걸릴 수 있습니다. 나머지 영향은 전체 트래픽의 30 % 미만으로 제한됩니다. 우리는 완전히 붙잡은 일단 또 다른 갱신을 제공할 것입니다.

4. 2026년 7월 31일 PM 7:25 UTCresolved

   이 사건은 해결됩니다. 15:18 ET / 19:18 UTC로, 우리는 작업의 백 로그를 완전히 처리하고, 우리의 EU02 현재 커넥터는 정상적인 대기 시간 범위 내에서 다시 처리됩니다. 데이터가 손실되지 않고, 모든 현재 이벤트는 목적지로 전송되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 PM 7:54 UTCresolved

   약 7 : 30 AM ET, 우리는 6 : 55 AM ET 및 8 AM ET 사이의 네트워크 연결에 영향을 미치는 미국 - WEST-2 지역의 AWS 네트워킹 아웃리지의 인식이되었습니다. AWS는 부정적 문제를 해결했습니다. 충격 창 도중, 몇몇 고객은 이메일 납품에 있는 intermittent 지연 그리고 지연을 경험할지도 모릅니다. 메일은 일반적으로 배달됩니다. 수심 증가로, 몇몇 고객은 메시지 납품에 있는 경험있는 잔여 지연이 있을지도 모릅니다. 이 지연은 오늘 오후 2시 40분으로 해결되었습니다. 이 붕괴는 AWS 인프라 내에서 시작되었으며 Braze 플랫폼의 모든 구성 요소에 의해 발생하지 않았습니다. AWS 사건에 대한 자세한 내용은 AWS 상태 페이지를 참조하십시오. https://health.aws.amazon.com/health/status

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 13일 PM 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. 2026년 7월 13일 PM 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. 2026년 7월 13일 PM 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. 2026년 6월 12일 PM 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. 2026년 6월 12일 PM 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. 2026년 6월 12일 PM 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. 2026년 5월 22일 PM 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. 2026년 5월 22일 PM 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. 2026년 5월 22일 PM 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. 2026년 5월 22일 PM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 7일 PM 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. 2026년 5월 7일 PM 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. 2026년 5월 7일 PM 5:19 UTCresolved

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

1. 2026년 5월 7일 PM 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. 2026년 5월 7일 PM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 PM 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. 2026년 4월 20일 PM 4:18 UTCinvestigating

   We are currently investigating an issue with the EU01 cluster.

2. 2026년 4월 20일 PM 4:49 UTCidentified

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

3. 2026년 4월 20일 PM 5:13 UTCmonitoring

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

4. 2026년 4월 20일 PM 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. 2026년 4월 20일 PM 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. 2026년 4월 20일 PM 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. 2026년 4월 17일 PM 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. 2026년 4월 8일 PM 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. 2026년 4월 8일 PM 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. 2026년 4월 8일 PM 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. 2026년 4월 8일 PM 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. 2026년 4월 8일 PM 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. 2026년 4월 6일 PM 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. 2026년 3월 24일 PM 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. 2026년 3월 24일 PM 5:50 UTCmonitoring

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

3. 2026년 3월 24일 PM 5:58 UTCresolved

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

1. 2026년 3월 20일 PM 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. 2026년 3월 20일 PM 7:19 UTCmonitoring

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

3. 2026년 3월 20일 PM 7:29 UTCresolved

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

1. 2026년 3월 17일 PM 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. 2026년 3월 17일 PM 8:57 UTCmonitoring

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

3. 2026년 3월 17일 PM 9:04 UTCresolved

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

1. 2026년 2월 24일 PM 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. 2026년 2월 24일 PM 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. 2026년 2월 24일 PM 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. 2026년 2월 18일 PM 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. 2026년 2월 18일 PM 12:39 UTCinvestigating

   We are continuing to investigate the issue.

3. 2026년 2월 18일 PM 3:20 UTCinvestigating

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

4. 2026년 2월 18일 PM 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. 2026년 2월 18일 PM 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. 2026년 2월 18일 PM 7:22 UTCresolved

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