Historial de interrupciones de Messagebird

1. August 13, 2026 at 5:06 PM 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. August 13, 2026 at 5:10 PM 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. August 13, 2026 at 5:21 PM 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. August 13, 2026 at 10:17 PM UTCresolved

   This incident has been resolved.

1. August 6, 2026 at 5:05 PM UTCinvestigating

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

2. August 6, 2026 at 5:48 PM UTCidentified

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

3. August 6, 2026 at 6:46 PM UTCidentified

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

4. August 6, 2026 at 8:49 PM UTCidentified

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

5. August 6, 2026 at 10:02 PM UTCmonitoring

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

6. August 6, 2026 at 10:02 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. August 6, 2026 at 10:08 PM UTCresolved

   This incident has been resolved.

1. July 22, 2026 at 12:16 PM UTCidentified

   Hemos identificado un problema que afecta la funcionalidad de búsqueda en el panel. Todos los servicios siguen siendo operativos, pero los nuevos artículos pueden no aparecer en los resultados de búsqueda de tableros de control.

2. July 22, 2026 at 12:54 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 22, 2026 at 1:58 PM UTCmonitoring

   La solución ha sido implementada, y se ha restaurado la funcionalidad de búsqueda de dashboard. Estamos reproduciendo eventos desde el período del incidente para actualizar el índice de búsqueda y asegurar que todos los elementos afectados estén disponibles en los resultados de búsqueda.

4. July 22, 2026 at 2:54 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 8, 2026 at 8:12 PM UTCinvestigating

   Estamos observando retrasos en el procesamiento de Mensaje " Objetos de Contacto. Estamos investigando activamente la cuestión El impacto se limita a los clientes en la plataforma Bird Box, alojada en la región nosotros-oeste-1.

2. July 8, 2026 at 10:10 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 8, 2026 at 10:28 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 5, 2026 at 3:50 PM UTCinvestigating

   Estamos viendo un aumento de errores en los registros de Viajes ahora mismo. Estamos investigando el tema.

2. July 5, 2026 at 4:07 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 5, 2026 at 4:12 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 12, 2026 at 2:10 PM 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. June 12, 2026 at 3:05 PM UTCidentified

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

3. June 12, 2026 at 6:22 PM UTCresolved

   This incident has been resolved.

1. June 4, 2026 at 11:13 AM UTCinvestigating

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

2. June 4, 2026 at 12:02 PM UTCresolved

   This incident has been resolved.

1. June 4, 2026 at 9:57 AM 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. June 4, 2026 at 11:42 AM UTCresolved

   This incident has been resolved.

1. June 1, 2026 at 4:33 PM 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. June 1, 2026 at 4:51 PM UTCmonitoring

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

3. June 1, 2026 at 5:22 PM UTCresolved

   This incident has been resolved.

1. May 20, 2026 at 10:06 AM UTCinvestigating

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

2. May 20, 2026 at 10:16 AM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 11:33 AM 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. May 13, 2026 at 12:16 PM UTCidentified

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

3. May 13, 2026 at 12:25 PM UTCmonitoring

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

4. May 13, 2026 at 1:33 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 1:41 PM UTCinvestigating

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

2. May 12, 2026 at 1:58 PM UTCmonitoring

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

3. May 12, 2026 at 2:16 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 10:55 AM 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. May 16, 2026 at 7:43 AM UTCresolved

   This incident has been resolved.

1. May 1, 2026 at 8:06 PM UTCinvestigating

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

2. May 1, 2026 at 9:14 PM UTCidentified

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

3. May 1, 2026 at 9:37 PM UTCresolved

   This incident has been resolved.

1. April 7, 2026 at 5:49 AM UTCinvestigating

   We are currently investigating this issue.

2. April 7, 2026 at 7:28 AM 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. April 7, 2026 at 8:32 AM UTCresolved

   All backlog fully processed.

1. March 31, 2026 at 11:29 AM 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. March 31, 2026 at 12:25 PM UTCmonitoring

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

3. March 31, 2026 at 1:47 PM UTCresolved

   This incident has been resolved.

1. March 24, 2026 at 1:49 PM UTCinvestigating

   We are currently investigating this issue.

2. March 24, 2026 at 2:16 PM UTCmonitoring

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

3. March 24, 2026 at 2:37 PM UTCresolved

   This incident has been resolved.

1. March 23, 2026 at 7:29 AM UTCinvestigating

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

2. March 23, 2026 at 8:42 AM UTCmonitoring

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

3. March 23, 2026 at 9:34 AM UTCresolved

   This incident has been resolved.

1. March 11, 2026 at 1:52 PM UTCinvestigating

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

2. March 11, 2026 at 3:07 PM UTCresolved

   This incident has been resolved.

1. February 23, 2026 at 10:30 PM 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. February 23, 2026 at 10:43 PM UTCidentified

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

3. February 23, 2026 at 11:49 PM UTCidentified

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

4. February 24, 2026 at 12:00 AM UTCmonitoring

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

5. February 24, 2026 at 12:10 AM UTCresolved

   This incident has been resolved.