Istoricul incidentelor Messagebird

1. 13 august 2026 la 17:06 UTCidentified

   Avem o pană intermitentă de platformă Bird Inbox (Classic). Utilizatorii pot experimenta probleme accesează inbox și conversații. Echipa noastră de ingineri a fost angajată şi investighează activ.

2. 13 august 2026 la 17:10 UTCmonitoring

   Am confirmat că furnizorul nostru de găzduire se confruntă în prezent cu probleme de capacitate care afectează disponibilitatea Inbox. Lucrăm cu furnizorul și evaluăm opțiunile de atenuare de partea noastră în paralel. Între timp, utilizatorii pot continua să aibă acces intermitent la conversaţii. Vom oferi o actualizare suplimentară în 30 de minute, sau mai devreme în cazul în care situația se schimbă.

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

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 6 august 2026 la 17:05 UTCinvestigating

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

2. 6 august 2026 la 17:48 UTCidentified

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

3. 6 august 2026 la 18:46 UTCidentified

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

4. 6 august 2026 la 20:49 UTCidentified

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

5. 6 august 2026 la 22:02 UTCmonitoring

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

6. 6 august 2026 la 22:02 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 6 august 2026 la 22:08 UTCresolved

   This incident has been resolved.

1. 22 iulie 2026 la 12:16 UTCidentified

   Am identificat o problemă care afectează funcționalitatea de căutare pe tabloul de bord. Toate serviciile rămân operaționale, dar elementele noi nu pot apărea în rezultatele căutării tabloului de bord.

2. 22 iulie 2026 la 12:54 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 22 iulie 2026 la 13:58 UTCmonitoring

   Fix a fost implementat, iar funcționalitatea de căutare bord a fost restaurată. Reluăm evenimentele din perioada incidentului pentru a reîmprospăta indicele de căutare și pentru a ne asigura că toate elementele afectate sunt disponibile în rezultatele căutării.

4. 22 iulie 2026 la 14:54 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 8 iulie 2026 la 20:12 UTCinvestigating

   Observăm întârzieri în procesarea obiectelor de contact & Mesaj. Investigăm în mod activ problema Impactul este limitat la Clientii din Bird Box, gazduiti in regiunea ne-vest-1.

2. 8 iulie 2026 la 22:10 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 8 iulie 2026 la 22:28 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 5 iulie 2026 la 15:50 UTCinvestigating

   Vedem un vârf de erori în jurnalele de călătorie chiar acum. Investigăm problema.

2. 5 iulie 2026 la 16:07 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 5 iulie 2026 la 16:12 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

   This incident has been resolved.

1. 4 iunie 2026 la 11:13 UTCinvestigating

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

2. 4 iunie 2026 la 12:02 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 1 iunie 2026 la 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 iunie 2026 la 16:51 UTCmonitoring

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

3. 1 iunie 2026 la 17:22 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 13 mai 2026 la 12:25 UTCmonitoring

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

4. 13 mai 2026 la 13:33 UTCresolved

   This incident has been resolved.

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

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

3. 12 mai 2026 la 14:16 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 1 mai 2026 la 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 mai 2026 la 21:14 UTCidentified

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

3. 1 mai 2026 la 21:37 UTCresolved

   This incident has been resolved.

1. 7 aprilie 2026 la 05:49 UTCinvestigating

   We are currently investigating this issue.

2. 7 aprilie 2026 la 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 aprilie 2026 la 08:32 UTCresolved

   All backlog fully processed.

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

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

3. 31 martie 2026 la 13:47 UTCresolved

   This incident has been resolved.

1. 24 martie 2026 la 13:49 UTCinvestigating

   We are currently investigating this issue.

2. 24 martie 2026 la 14:16 UTCmonitoring

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

3. 24 martie 2026 la 14:37 UTCresolved

   This incident has been resolved.

1. 23 martie 2026 la 07:29 UTCinvestigating

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

2. 23 martie 2026 la 08:42 UTCmonitoring

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

3. 23 martie 2026 la 09:34 UTCresolved

   This incident has been resolved.

1. 11 martie 2026 la 13:52 UTCinvestigating

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

2. 11 martie 2026 la 15:07 UTCresolved

   This incident has been resolved.

1. 23 februarie 2026 la 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 februarie 2026 la 22:43 UTCidentified

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

3. 23 februarie 2026 la 23:49 UTCidentified

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

4. 24 februarie 2026 la 00:00 UTCmonitoring

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

5. 24 februarie 2026 la 00:10 UTCresolved

   This incident has been resolved.