Bird (MessageBird)

Affected: Bird Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 18:18 UTC

   We are currently investigating an increase in 5xx errors and delayed email deliveries. Please note: There is no impact to our Marketing Platform or SparkPost APIs.

2. identified 2026-10-05 18:40 UTC

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

3. monitoring 2026-10-05 19:11 UTC

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

4. resolved 2026-10-05 19:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: SMS - API, SMS - SMPP - EU - SMPP01, SMS - SMPP - EU - SMPP02, SMS - SMPP - EU - SMPP03, Channels - Europe, SMS - API V1, Channels - US (West), SMS - Mail to SMS Relay Service, Channels - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-04 15:27 UTC

   Since 2:55 PM UTC, we are experiencing increased latency with our SMS service (API, SMPP, Mail to SMS). We are investigating the issue and will provide an update as soon as we have more information.

2. monitoring 2026-10-04 15:41 UTC

   The situation has improved since 3:30 PM UTC. We are monitoring the services.

3. resolved 2026-10-04 16:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Bird Platform

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-26 15:59 UTC

   We are investigating an issue with the USA Bird Platform API. We are seeing increased Error codes returning.

2. identified 2026-09-26 16:06 UTC

   We have found the cause of the issue cycling the bad instances. Recovery expected soon.

3. monitoring 2026-09-26 16:11 UTC

   We are monitoring the systems while they recover. All errors have stopped and all queues are recovering.

4. resolved 2026-09-26 16:17 UTC

   Thank you for your patience. We are seeing a full recovery. No more errors are being returned, and all queues have caught up.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Flows - Europe

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 18:08 UTC

   We are currently investigating an issue in EU that is causing some flows to fail.

2. investigating 2026-09-21 18:12 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-21 18:13 UTC

   The current failure is in log retrieval not flow runs. Flows are running with out impact. Logs are failing to load upon request.

4. identified 2026-09-21 19:09 UTC

   We have identified the issue and are testing a fix. We expect logs to be available again with in an hour.

5. monitoring 2026-09-21 21:30 UTC

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

6. resolved 2026-09-21 21:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Analytics - US (West), Campaigns - US (West), Channels - US (West), Connectors - US (West), Contacts - US (West), Flows - US (West), Inbox - US (West), Journey - US (West)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-18 21:53 UTC

   Between 20:04 and 20:48 UTC on 18 September, a fault in an upstream cloud provider service disrupted internal event delivery in our US region. During this window, multiple platform services processed events with delays. Customers may have experienced delayed updates to their...

2. monitoring 2026-09-18 22:40 UTC

   The upstream fault has cleared and processing has returned to normal latency across affected services in our US region. A subset of operations did not complete during the affected window, and we are replaying those now. We are continuing to monitor before declaring this...

3. resolved 2026-09-18 23:23 UTC

   This incident is resolved. Processing has returned to normal latency across affected services in our US region, and operations that did not complete during the affected window have been replayed.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Bird Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 16:22 UTC

   We are investigating elevated error rates and increased latency for API requests in our US region, beginning approximately 15:31 UTC. Write operations are the most affected and may return errors or time out. Voice call setup and number routing are also degraded. Read operations...

2. monitoring 2026-09-17 16:46 UTC

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

3. monitoring 2026-09-17 16:46 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-17 17:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Voice - Connectivity - Global

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 11:38 UTC

   We are currently investigating the issue with calls to UK numbers resulting in one-way audio

2. investigating 2026-09-13 15:08 UTC

   We are working with the carrier to investigate and analyze this issue. We are observing this issue on some inbound calls to certain UK numbers.

3. resolved 2026-09-16 11:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: SMS - Connectivity - APAC, SMS - Connectivity - EMEA, SMS - Connectivity - LATAM, SMS - Connectivity - NORAM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-10 10:27 UTC

   Between 9:48 and 9:57 UTC, some SMS messages were not processed as expected for the Engagement Platform. The issue has been resolved, and normal SMS processing has resumed.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Inbox

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-13 17:06 UTC

   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. monitoring 2026-08-13 17:10 UTC

   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...

3. monitoring 2026-08-13 17:21 UTC

   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. resolved 2026-08-13 22:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Connectors - Europe, Connectors - US (West), Connectors - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 17:05 UTC

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

2. identified 2026-08-06 17:48 UTC

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

3. identified 2026-08-06 18:46 UTC

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

4. identified 2026-08-06 20:49 UTC

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

5. monitoring 2026-08-06 22:02 UTC

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

6. monitoring 2026-08-06 22:02 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-08-06 22:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Dashboard - app.bird.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-22 12:16 UTC

   We've identified an issue affecting search functionality on the dashboard. All services remain operational, but new items may not appear in dashboard search results.

2. monitoring 2026-07-22 12:54 UTC

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

3. monitoring 2026-07-22 13:58 UTC

   The fix has been deployed, and dashboard search functionality has been restored. We are replaying events from the incident period to refresh the search index and ensure all affected items are available in search results.

4. resolved 2026-07-22 14:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Dashboard - app.bird.com, Analytics - US (West), Contacts - US (West)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-08 20:12 UTC

   We are observing delays in processing of Message & Contact Objects. We are actively investigating the issue The impact is limited to Customers in Bird Box platform, hosted in the us-west-1 region.

2. identified 2026-07-08 22:10 UTC

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

3. resolved 2026-07-08 22:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Journey - US (West)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-05 15:50 UTC

   We are seeing a spike in errors in the Journeys logs right now. We are investigating the issue.

2. monitoring 2026-07-05 16:07 UTC

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

3. resolved 2026-07-05 16:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Channels - Europe, Channels - US (West), Channels - Asia (India), WhatsApp Channel

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-12 14:10 UTC

   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...

2. identified 2026-06-12 15:05 UTC

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

3. resolved 2026-06-12 18:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Flows - Europe, Flows - US (West), Flows - Asia (India)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 11:13 UTC

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

2. resolved 2026-06-04 12:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: SMS - API, SMS - SMPP - EU - SMPP01, SMS - SMPP - EU - SMPP02, SMS - SMPP - EU - SMPP03

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-04 09:57 UTC

   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. resolved 2026-06-04 11:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Conversations - API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 16:33 UTC

   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. monitoring 2026-06-01 16:51 UTC

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

3. resolved 2026-06-01 17:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-20 10:06 UTC

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

2. resolved 2026-05-20 10:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Journey - Europe

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 11:33 UTC

   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...

2. identified 2026-05-13 12:16 UTC

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

3. monitoring 2026-05-13 12:25 UTC

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

4. resolved 2026-05-13 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Journey - Europe

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-12 13:41 UTC

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

2. monitoring 2026-05-12 13:58 UTC

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

3. resolved 2026-05-12 14:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: SMS - Connectivity - EMEA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-08 10:55 UTC

   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. resolved 2026-05-16 07:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Conversations - API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-01 20:06 UTC

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

2. identified 2026-05-01 21:14 UTC

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

3. resolved 2026-05-01 21:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Flows - US (West), Journey - US (West)

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-07 05:49 UTC

   We are currently investigating this issue.

2. monitoring 2026-04-07 07:28 UTC

   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...

3. resolved 2026-04-07 08:32 UTC

   All backlog fully processed.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Campaigns - Europe, Campaigns - US (West), Campaigns - Asia (India)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-31 11:29 UTC

   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. monitoring 2026-03-31 12:25 UTC

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

3. resolved 2026-03-31 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Contacts - Europe, Contacts - US (West), Contacts - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-24 13:49 UTC

   We are currently investigating this issue.

2. monitoring 2026-03-24 14:16 UTC

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

3. resolved 2026-03-24 14:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Flows - Asia (India), Journey - Asia (India)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-23 07:29 UTC

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

2. monitoring 2026-03-23 08:42 UTC

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

3. resolved 2026-03-23 09:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Contacts - Europe, Contacts - US (West), Contacts - Asia (India)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-11 13:52 UTC

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

2. resolved 2026-03-11 15:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-23 22:30 UTC

   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. identified 2026-02-23 22:43 UTC

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

3. identified 2026-02-23 23:49 UTC

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

4. monitoring 2026-02-24 00:00 UTC

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

5. resolved 2026-02-24 00:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-02-15 14:30 UTC

   Between 12:36 AM and 5:10 AM EST on February 15, 2026, the data platform experienced a brief period of degraded performance. During this window, journey runs experienced elevated delays. All affected journeys have been successfully completed. The platform fully recovered by 5:10...

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-02-09 12:30 UTC

   Between February 6th, 17:50 GMT and February 9th, 13:50 GMT, activating a scheduled campaign resulted in it being sent immediately instead of at the scheduled time.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Analytics - US (West), Campaigns - US (West), Contacts - US (West)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-27 18:56 UTC

   We are currently experiencing a database performance issue that is impacting multiple platform services. Customers may encounter timeouts, slow response times, and intermittent errors when accessing the following areas: * CDP (Customer Data Platform) - Data synchronization and...

2. identified 2026-01-27 19:55 UTC

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

3. identified 2026-01-27 20:27 UTC

   The team has made additional adjustments and we have started seeing accelerated recovery of the cluster.

4. identified 2026-01-27 20:31 UTC

   We have identified which hardware was causing the issues and are replacing it. We are already seeing some improvement and expect that to continue.

5. monitoring 2026-01-27 20:53 UTC

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

6. resolved 2026-01-27 21:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Analytics - US (West)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-23 07:08 UTC

   We are currently investigating this issue.

2. identified 2026-01-23 08:14 UTC

   Customers are having problems seeing contacts and segments. The issue has been identified and the team is working on a fix.

3. identified 2026-01-23 09:27 UTC

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

4. identified 2026-01-23 09:54 UTC

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

5. identified 2026-01-23 10:46 UTC

   We are seeing an improvement: piled up inserts are processing and we hope to start restoring systems in some time.

6. monitoring 2026-01-23 11:07 UTC

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

7. resolved 2026-01-23 11:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: WhatsApp Channel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 17:07 UTC

   We are currently investigating this issue.

2. monitoring 2026-01-20 17:08 UTC

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

3. resolved 2026-01-20 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Channels - Europe, Channels - US (West), Channels - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 14:14 UTC

   We are currently investigating this issue.

2. identified 2026-01-20 15:48 UTC

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

3. monitoring 2026-01-20 16:54 UTC

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

4. resolved 2026-01-20 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Analytics - US (West)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-10 21:26 UTC

   We are investigating a delay in email sending data. There is no delay in email sending.

2. monitoring 2025-12-11 00:24 UTC

   Our pipeline that was having issue has recovered. We are monitoring to ensure we stay in a good state. Very sorry for the inconvenience.

3. monitoring 2025-12-11 00:24 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-12-11 00:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Contacts - Europe

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-04 16:16 UTC

   We are currently investigating a degraded performance with Contacts In the EU region which impacts but is not limited to Contacts pages, Journeys and Flows.

2. monitoring 2025-12-04 17:14 UTC

   The degradation has been mitigated and all service functionality has been fully restored.

3. resolved 2025-12-05 09:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Contacts - Europe

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-04 09:19 UTC

   We are currently investigating a degraded performance with Contacts In the EU region which impacts but is not limited to Contacts pages, Journeys and Flows.

2. monitoring 2025-12-04 09:31 UTC

   We have identified the issue and a fix has been implemented. We are monitoring the situation.

3. resolved 2025-12-04 09:37 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-04 04:22 UTC

   We are currently investigating this issue.

2. investigating 2025-12-04 04:30 UTC

   The EU region is impacted

3. monitoring 2025-12-04 04:38 UTC

   A solution has been implemented and we are monitoring the results. No messages or data has been lost.

4. resolved 2025-12-04 04:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Contacts - Europe, Contacts - Asia (India)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-28 16:43 UTC

   We have identified an issue affecting contact event segments in the EU and AP regions. Some segments may not include all contacts that match the event criteria. We are actively investigating and will provide updates as we work toward a resolution.

2. identified 2025-11-28 17:01 UTC

   We are actively working on a fix. This issue only affects contacts that have not been updated since August 11, 2025.

3. identified 2025-11-28 18:04 UTC

   The segmentation issue in the EU region has been resolved. As part of our fix, contact updates in the EU and AP regions are experiencing delays. We expect this to be resolved within the next few minutes.

4. monitoring 2025-11-28 18:13 UTC

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

5. resolved 2025-11-28 19:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Channels - Europe, Channels - US (West), Channels - Asia (India)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-27 10:57 UTC

   We are investigating issues preventing some customers from installing WhatsApp channels for pre-verified numbers only.

2. identified 2025-12-01 10:58 UTC

   We've identified the issue and are working with Meta (WhatsApp) to resolve it.

3. monitoring 2025-12-02 14:33 UTC

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

4. resolved 2025-12-04 16:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Campaigns - Europe, Contacts - Europe, Contacts - US (West), Contacts - Asia (India), Journey - Europe, Journey - US (West), Journey - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-26 10:42 UTC

   We are currently investigating this issue.

2. investigating 2025-11-26 10:49 UTC

   We are continuing to investigate this issue.

3. identified 2025-11-26 11:17 UTC

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

4. identified 2025-11-26 12:24 UTC

   We are continuing to work on the issue. We see that there is very little impact at the moment but some underlying systems are still not stable.

5. identified 2025-11-26 15:14 UTC

   We are continuing to work on the issue. Multiple services have recovered. Contacts, Journeys and Campaigns still experience degraded performance.

6. monitoring 2025-11-26 16:14 UTC

   Systems have stabilized. We are continuously monitoring the services.

7. resolved 2025-11-26 18:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: WhatsApp Channel

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-25 15:22 UTC

   We are currently investigating this issue.

2. monitoring 2025-11-25 15:46 UTC

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

3. resolved 2025-11-25 16:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Channels - Europe, Channels - US (West), Channels - Asia (India)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-24 11:47 UTC

   We are investigating issues preventing some customers from installing WhatsApp channels.

2. identified 2025-11-24 12:36 UTC

   We have confirmed that impact is scoped to pre-verified numbers only. The issue has been escalated to Meta for further investigations.

3. identified 2025-11-24 17:43 UTC

   Meta's engineering team has been engaged for investigations.

4. identified 2025-11-25 09:30 UTC

   We are continuing investigations alongside Meta engineering teams.

5. identified 2025-11-26 09:25 UTC

   We are continuing investigations.

6. identified 2025-11-26 10:18 UTC

   Meta identified some issues regarding sign-up flows on their end and have provided a temporary workaround; we are in the process of confirming and deploying it.

7. resolved 2025-11-26 11:12 UTC

   We have deployed the proposed workaround and full service functionality has been restored.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Organizations (Billing, IAM, Settings, Wallets) - Europe, Organizations (Billing, IAM, Settings, Wallets) - US (West), Organizations (Billing, IAM, Settings, Wallets) - Asia (India)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-12 21:03 UTC

   We're currently experiencing an issue that is affecting the provisioning of new workspaces. Customers may encounter delays when creating new workspaces. Our team is investigating and working to resolve this as quickly as possible.

2. resolved 2025-11-12 21:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Flows - Europe, Flows - US (West), Flows - Asia (India)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-11 06:55 UTC

   We identified elevated error rates in the Flows service earlier today. Some customers may notice failures in flow invocations starting around 17:00 UTC on November 10. A mitigation is in progress, and our team is working to restore normal performance.

2. monitoring 2025-11-11 07:17 UTC

   A fix has been implemented. We are monitoring the results.

3. resolved 2025-11-11 07:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Channels - Europe, Channels - US (West), Channels - Asia (India)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-04 13:44 UTC

   We have identified an issue with WhatsApp message status updates. No message status updates are lost.

2. identified 2025-11-04 13:45 UTC

   We have fixed the issue and are rolling-out the solution

3. resolved 2025-11-04 13:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-28 12:26 UTC

   We are currently investigating this issue.

2. resolved 2025-10-28 13:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Conversations - API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-25 00:35 UTC

   We are seeing some small amount of API request acceptance errors on the conversations API on the Connectivity Platform. Some API calls are also experiencing increased latency. It is being actively investigated.

2. investigating 2025-10-25 00:37 UTC

   We are continuing to investigate this issue.

3. identified 2025-10-25 00:44 UTC

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

4. monitoring 2025-10-25 01:26 UTC

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

5. resolved 2025-10-25 01:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Affected: Conversations - API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-21 14:11 UTC

   We are currently experiencing slower than expected sending of messages through Viber due to a slowdown in processing rate from Viber.

2. investigating 2025-10-23 12:11 UTC

   A limited subset of customers are unable to send messages through Viber channel; investigation and remediations ongoing.

3. investigating 2025-10-24 07:42 UTC

   Ability to sent messages through Viber has been fully restored.

4. resolved 2025-10-24 07:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-10-21 07:30 UTC

   In Bird CRM, for custom contact attributes created before August 2024, updates experienced failures from flows, API, or connectors since around October 21 2025 7:30 UTC. This doesn't affect updating other attributes like standard attributes or custom attributes created after...

Excerpts are shortened. Read the full incident on Bird (MessageBird)'s status page.