Histórico de interrupções do Messagebird

1. 13 Eost 2026 da 17:06 UTCidentified

   Estamos experimentando uma falha intermitente da plataforma Bird Inbox (Classic). Os usuários podem experimentar problemas de acesso à caixa de entrada e conversas. A nossa equipa de engenharia esteve envolvida e está a investigar ativamente.

2. 13 Eost 2026 da 17:10 UTCmonitoring

   Confirmamos que nosso provedor de hospedagem está atualmente enfrentando problemas de capacidade que estão afetando a disponibilidade da Caixa de entrada. Estamos trabalhando com o provedor e avaliando opções de mitigação do nosso lado em paralelo. Entretanto, os utilizadores podem continuar a ter acesso intermitente a conversas. Nós forneceremos uma atualização adicional dentro de 30 minutos, ou mais cedo se a situação mudar.

3. 13 Eost 2026 da 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 Eost 2026 da 22:17 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Eost 2026 da 17:05 UTCinvestigating

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

2. 6 Eost 2026 da 17:48 UTCidentified

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

3. 6 Eost 2026 da 18:46 UTCidentified

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

4. 6 Eost 2026 da 20:49 UTCidentified

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

5. 6 Eost 2026 da 22:02 UTCmonitoring

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

6. 6 Eost 2026 da 22:02 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 6 Eost 2026 da 22:08 UTCresolved

   This incident has been resolved.

1. 22 Gouere 2026 da 12:16 UTCidentified

   Identificámos um problema que afectava a funcionalidade de busca no painel. Todos os serviços permanecem operacionais, mas novos itens podem não aparecer nos resultados da pesquisa do painel.

2. 22 Gouere 2026 da 12:54 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 22 Gouere 2026 da 13:58 UTCmonitoring

   A correção foi implantada e a funcionalidade de pesquisa do painel foi restaurada. Estamos repetindo eventos do período incidente para atualizar o índice de busca e garantir que todos os itens afetados estejam disponíveis nos resultados da pesquisa.

4. 22 Gouere 2026 da 14:54 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 20:12 UTCinvestigating

   Estamos observando atrasos no processamento de Objetos de Mensagem e Contato. Estamos a investigar activamente a questão O impacto é limitado aos Clientes na plataforma Bird Box, hospedada na região us-west-1.

2. 8 Gouere 2026 da 22:10 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 8 Gouere 2026 da 22:28 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 5 Gouere 2026 da 15:50 UTCinvestigating

   Estamos vendo um pico de erros nos registros Journeys agora. Estamos a investigar a questão.

2. 5 Gouere 2026 da 16:07 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 5 Gouere 2026 da 16:12 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 18:22 UTCresolved

   This incident has been resolved.

1. 4 Mezheven 2026 da 11:13 UTCinvestigating

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

2. 4 Mezheven 2026 da 12:02 UTCresolved

   This incident has been resolved.

1. 4 Mezheven 2026 da 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 Mezheven 2026 da 11:42 UTCresolved

   This incident has been resolved.

1. 1 Mezheven 2026 da 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 Mezheven 2026 da 16:51 UTCmonitoring

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

3. 1 Mezheven 2026 da 17:22 UTCresolved

   This incident has been resolved.

1. 20 Mae 2026 da 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 Mae 2026 da 10:16 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 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 Mae 2026 da 12:16 UTCidentified

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

3. 13 Mae 2026 da 12:25 UTCmonitoring

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

4. 13 Mae 2026 da 13:33 UTCresolved

   This incident has been resolved.

1. 12 Mae 2026 da 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 Mae 2026 da 13:58 UTCmonitoring

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

3. 12 Mae 2026 da 14:16 UTCresolved

   This incident has been resolved.

1. 8 Mae 2026 da 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 Mae 2026 da 07:43 UTCresolved

   This incident has been resolved.

1. 1 Mae 2026 da 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 Mae 2026 da 21:14 UTCidentified

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

3. 1 Mae 2026 da 21:37 UTCresolved

   This incident has been resolved.

1. 7 Ebrel 2026 da 05:49 UTCinvestigating

   We are currently investigating this issue.

2. 7 Ebrel 2026 da 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 Ebrel 2026 da 08:32 UTCresolved

   All backlog fully processed.

1. 31 Meurzh 2026 da 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 Meurzh 2026 da 12:25 UTCmonitoring

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

3. 31 Meurzh 2026 da 13:47 UTCresolved

   This incident has been resolved.

1. 24 Meurzh 2026 da 13:49 UTCinvestigating

   We are currently investigating this issue.

2. 24 Meurzh 2026 da 14:16 UTCmonitoring

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

3. 24 Meurzh 2026 da 14:37 UTCresolved

   This incident has been resolved.

1. 23 Meurzh 2026 da 07:29 UTCinvestigating

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

2. 23 Meurzh 2026 da 08:42 UTCmonitoring

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

3. 23 Meurzh 2026 da 09:34 UTCresolved

   This incident has been resolved.

1. 11 Meurzh 2026 da 13:52 UTCinvestigating

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

2. 11 Meurzh 2026 da 15:07 UTCresolved

   This incident has been resolved.

1. 23 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 22:43 UTCidentified

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

3. 23 Cʼhwevrer 2026 da 23:49 UTCidentified

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

4. 24 Cʼhwevrer 2026 da 00:00 UTCmonitoring

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

5. 24 Cʼhwevrer 2026 da 00:10 UTCresolved

   This incident has been resolved.