История сбоев Messagebird

1. 13 августа 2026 г. в 17: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. 13 августа 2026 г. в 17: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. 13 августа 2026 г. в 17: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. 13 августа 2026 г. в 22:17 UTCresolved

   This incident has been resolved.

1. 6 августа 2026 г. в 17:05 UTCinvestigating

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

2. 6 августа 2026 г. в 17:48 UTCidentified

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

3. 6 августа 2026 г. в 18:46 UTCidentified

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

4. 6 августа 2026 г. в 20:49 UTCidentified

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

5. 6 августа 2026 г. в 22:02 UTCmonitoring

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

6. 6 августа 2026 г. в 22:02 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 6 августа 2026 г. в 22:08 UTCresolved

   This incident has been resolved.

1. 22 июля 2026 г. в 12:16 UTCidentified

   Мы выявили проблему, затрагивающую функциональность поиска на приборной панели. Все службы остаются в рабочем состоянии, но новые элементы могут не отображаться в результатах поиска.

2. 22 июля 2026 г. в 12:54 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 22 июля 2026 г. в 13:58 UTCmonitoring

   Исправление было развернуто, и функция поиска панели приборов была восстановлена. Мы воспроизводим события периода инцидента, чтобы обновить поисковый индекс и обеспечить доступность всех затронутых элементов в результатах поиска.

4. 22 июля 2026 г. в 14:54 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 8 июля 2026 г. в 20:12 UTCinvestigating

   Мы наблюдаем задержки в обработке сообщений и контактных объектов. Мы активно изучаем этот вопрос. Влияние ограничено клиентской платформой Bird Box, размещенной в регионе США-Запад-1.

2. 8 июля 2026 г. в 22:10 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 8 июля 2026 г. в 22:28 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 5 июля 2026 г. в 15:50 UTCinvestigating

   Мы видим всплеск ошибок в журналах Journeys прямо сейчас. Мы расследуем этот вопрос.

2. 5 июля 2026 г. в 16:07 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 5 июля 2026 г. в 16:12 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 12 июня 2026 г. в 14: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. 12 июня 2026 г. в 15: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. 12 июня 2026 г. в 18:22 UTCresolved

   This incident has been resolved.

1. 4 июня 2026 г. в 11:13 UTCinvestigating

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

2. 4 июня 2026 г. в 12:02 UTCresolved

   This incident has been resolved.

1. 4 июня 2026 г. в 09: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. 4 июня 2026 г. в 11:42 UTCresolved

   This incident has been resolved.

1. 1 июня 2026 г. в 16: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. 1 июня 2026 г. в 16:51 UTCmonitoring

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

3. 1 июня 2026 г. в 17:22 UTCresolved

   This incident has been resolved.

1. 20 мая 2026 г. в 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. 20 мая 2026 г. в 10:16 UTCresolved

   This incident has been resolved.

1. 13 мая 2026 г. в 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. 13 мая 2026 г. в 12:16 UTCidentified

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

3. 13 мая 2026 г. в 12:25 UTCmonitoring

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

4. 13 мая 2026 г. в 13:33 UTCresolved

   This incident has been resolved.

1. 12 мая 2026 г. в 13:41 UTCinvestigating

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

2. 12 мая 2026 г. в 13:58 UTCmonitoring

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

3. 12 мая 2026 г. в 14:16 UTCresolved

   This incident has been resolved.

1. 8 мая 2026 г. в 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. 16 мая 2026 г. в 07:43 UTCresolved

   This incident has been resolved.

1. 1 мая 2026 г. в 20:06 UTCinvestigating

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

2. 1 мая 2026 г. в 21:14 UTCidentified

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

3. 1 мая 2026 г. в 21:37 UTCresolved

   This incident has been resolved.

1. 7 апреля 2026 г. в 05:49 UTCinvestigating

   We are currently investigating this issue.

2. 7 апреля 2026 г. в 07: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. 7 апреля 2026 г. в 08:32 UTCresolved

   All backlog fully processed.

1. 31 марта 2026 г. в 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. 31 марта 2026 г. в 12:25 UTCmonitoring

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

3. 31 марта 2026 г. в 13:47 UTCresolved

   This incident has been resolved.

1. 24 марта 2026 г. в 13:49 UTCinvestigating

   We are currently investigating this issue.

2. 24 марта 2026 г. в 14:16 UTCmonitoring

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

3. 24 марта 2026 г. в 14:37 UTCresolved

   This incident has been resolved.

1. 23 марта 2026 г. в 07:29 UTCinvestigating

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

2. 23 марта 2026 г. в 08:42 UTCmonitoring

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

3. 23 марта 2026 г. в 09:34 UTCresolved

   This incident has been resolved.

1. 11 марта 2026 г. в 13:52 UTCinvestigating

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

2. 11 марта 2026 г. в 15:07 UTCresolved

   This incident has been resolved.

1. 23 февраля 2026 г. в 22: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. 23 февраля 2026 г. в 22:43 UTCidentified

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

3. 23 февраля 2026 г. в 23:49 UTCidentified

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

4. 24 февраля 2026 г. в 00:00 UTCmonitoring

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

5. 24 февраля 2026 г. в 00:10 UTCresolved

   This incident has been resolved.