Messagebird 장애 기록

1. 2026년 8월 13일 PM 5:06 UTCidentified

   We are experiencing an intermittent outage of Bird Inbox (Classic) platform. Users may experience issues accesses inbox and conversations. Our engineering team has been engaged and is actively investigating.

2. 2026년 8월 13일 PM 5:10 UTCmonitoring

   We have confirmed that our hosting provider is currently experiencing capacity issues which are affecting the availability of the Inbox. We are working with the provider and evaluating mitigation options on our side in parallel. Users may continue to experience intermittent access to conversations in the meantime. We will provide a further update within 30 minutes, or sooner if the situation changes.

3. 2026년 8월 13일 PM 5:21 UTCmonitoring

   We are seeing stabilization of Inbox availability. Users should now be able to access conversations. We are continuing to monitor closely to confirm the issue is fully resolved before closing this incident. We will provide a further update within 60 minutes.

4. 2026년 8월 13일 PM 10:17 UTCresolved

   This incident has been resolved.

1. 2026년 8월 6일 PM 5:05 UTCinvestigating

   We are noticing failures in the connector service. We are investigating to identify the root cause

2. 2026년 8월 6일 PM 5:48 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 8월 6일 PM 6:46 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026년 8월 6일 PM 8:49 UTCidentified

   We identified the root cause and continuing to work on a fix for this issue.

5. 2026년 8월 6일 PM 10:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 2026년 8월 6일 PM 10:02 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 2026년 8월 6일 PM 10:08 UTCresolved

   This incident has been resolved.

1. 2026년 7월 22일 PM 12:16 UTCidentified

   대시보드의 검색 기능에 영향을 미치는 문제점을 발견했습니다. 모든 서비스는 운영을 유지하지만 새로운 항목은 대시보드 검색 결과에 표시되지 않을 수 있습니다.

2. 2026년 7월 22일 PM 12:54 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 22일 PM 1:58 UTCmonitoring

   수정이 배포되었으며 대시보드 검색 기능이 복원되었습니다. 검색 결과를 찾을 수 없습니다. 검색 결과를 찾을 수 없습니다.

4. 2026년 7월 22일 PM 2:54 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 8일 PM 8:12 UTCinvestigating

   메시지 및 연락처 개체의 처리 지연을 관찰하고 있습니다. 우리는 적극적으로 문제를 조사하고있다. 충격은 버드 박스 플랫폼에서 고객에게 제한되며, us-west-1 지역에서 호스팅됩니다.

2. 2026년 7월 8일 PM 10:10 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 8일 PM 10:28 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 5일 PM 3:50 UTCinvestigating

   현재 여행 로그에 오류가 발생하고 있습니다. 우리는 문제를 조사하고 있습니다.

2. 2026년 7월 5일 PM 4:07 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 5일 PM 4:12 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 6월 12일 PM 2:10 UTCinvestigating

   We are investigating increased WhatsApp message delivery failures caused by connectivity issues with Meta services. Customers may experience delays or failures when sending WhatsApp messages. Our team is actively monitoring the situation and working to mitigate the impact. We will provide further updates as more information becomes available.

2. 2026년 6월 12일 PM 3:05 UTCidentified

   We are continuing to monitor increased WhatsApp message delivery failures caused by ongoing disruptions in Meta’s services, as confirmed by Meta.

3. 2026년 6월 12일 PM 6:22 UTCresolved

   This incident has been resolved.

1. 2026년 6월 4일 AM 11:13 UTCinvestigating

   Flows and Journeys are unable to retrieve the Message Body property for Conversation Messages. We are investigating the issue.

2. 2026년 6월 4일 PM 12:02 UTCresolved

   This incident has been resolved.

1. 2026년 6월 4일 AM 9:57 UTCmonitoring

   Between 9:30 AM and 9:34 AM UTC, there has been an intermittent increase in delivery latency for messages sent. The issue has been resolved. We are monitoring the situation.

2. 2026년 6월 4일 AM 11:42 UTCresolved

   This incident has been resolved.

1. 2026년 6월 1일 PM 4:33 UTCinvestigating

   We are currently looking into an issue where processing conversations date is running behind in our US West cluster. This is causing the reporting to be behind.

2. 2026년 6월 1일 PM 4:51 UTCmonitoring

   The processing has caught up and we are monitoring to ensure it doesn't get behind again.

3. 2026년 6월 1일 PM 5:22 UTCresolved

   This incident has been resolved.

1. 2026년 5월 20일 AM 10:06 UTCinvestigating

   We are currently investigating an issue where the overview pages for Journeys, Flows, Search and other products are down and unavailable.

2. 2026년 5월 20일 AM 10:16 UTCresolved

   This incident has been resolved.

1. 2026년 5월 13일 AM 11:33 UTCinvestigating

   We are currently experiencing an issue where journeys are not displaying in the user interface. Journey runs are not affected and continue to execute normally. At this time, the issue is limited to the listing/viewing of journeys in the UI. Our engineering team is actively investigating the root cause.

2. 2026년 5월 13일 PM 12:16 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 5월 13일 PM 12:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 5월 13일 PM 1:33 UTCresolved

   This incident has been resolved.

1. 2026년 5월 12일 PM 1:41 UTCinvestigating

   We are currently experiencing delays in processing journeys. The team is actively working to increase processing speed and reduce delays.

2. 2026년 5월 12일 PM 1:58 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 5월 12일 PM 2:16 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 AM 10:55 UTCidentified

   KPN Netherlands has reported issues with A2P delivery to a small subset of their customer base, which may cause messages to be delivered with a delay or not at all. We are working closely with their engineering teams to have this resolved.

2. 2026년 5월 16일 AM 7:43 UTCresolved

   This incident has been resolved.

1. 2026년 5월 1일 PM 8:06 UTCinvestigating

   We are seeing elevated errors with conversations involving bots in the EU region and we are currently investigating this issue.

2. 2026년 5월 1일 PM 9:14 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 5월 1일 PM 9:37 UTCresolved

   This incident has been resolved.

1. 2026년 4월 7일 AM 5:49 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 7일 AM 7:28 UTCmonitoring

   We've identified the cause of the issue affecting wait steps in automations. A rapid spike in automation activity outpaced our infrastructure's autoscaling response, leading to a temporary processing backlog. Our systems have since scaled to meet demand and the backlog is expected to clear completely in 30mins.

3. 2026년 4월 7일 AM 8:32 UTCresolved

   All backlog fully processed.

1. 2026년 3월 31일 AM 11:29 UTCidentified

   We are currently investigating an issue impacting campaigns activated in the EP Marketing Suite within the last 30 minutes. Affected campaigns are failing approximately 10 minutes after activation. Our team is actively working on a fix.

2. 2026년 3월 31일 PM 12:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Affected customers are advised to retry their campaigns.

3. 2026년 3월 31일 PM 1:47 UTCresolved

   This incident has been resolved.

1. 2026년 3월 24일 PM 1:49 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 24일 PM 2:16 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 3월 24일 PM 2:37 UTCresolved

   This incident has been resolved.

1. 2026년 3월 23일 AM 7:29 UTCinvestigating

   Flows and Journeys are impacted. We are investigating this issue.

2. 2026년 3월 23일 AM 8:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 3월 23일 AM 9:34 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 PM 1:52 UTCinvestigating

   We are currently investigating processing delays impacting a subset of flows & journeys configured with contact-added-to-list triggers.

2. 2026년 3월 11일 PM 3:07 UTCresolved

   This incident has been resolved.

1. 2026년 2월 23일 PM 10:30 UTCinvestigating

   We are currently observing problems with our MMS service resulting in failed messages sending to US based routes. We are investigating the situation and we will provide an update as soon as we have additional information.

2. 2026년 2월 23일 PM 10:43 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 2월 23일 PM 11:49 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026년 2월 24일 AM 12:00 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2026년 2월 24일 AM 12:10 UTCresolved

   This incident has been resolved.