Bird Outage History

Started Oct 23, 2026, 02:16 PM UTC· resolved Oct 23, 2026, 02:44 PM UTC

1. identified Oct 23, 2026, 02:16 PM UTC

   We are currently pushing a fix for an issue we noticed with a some Whatsapp messages not getting sent.

2. monitoring Oct 23, 2026, 02:31 PM UTC

   The backlog has caught up. All messages have been sent. We are monitoring to ensure the fix holds.

3. resolved Oct 23, 2026, 02:44 PM UTC

   This incident has been resolved. All messages have been sent.

Read the full incident report →

Started Oct 05, 2026, 06:18 PM UTC· resolved Oct 05, 2026, 07:12 PM UTC

1. investigating Oct 05, 2026, 06:18 PM 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 Oct 05, 2026, 06:40 PM UTC

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

3. monitoring Oct 05, 2026, 07:11 PM UTC

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

4. resolved Oct 05, 2026, 07:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 04, 2026, 03:27 PM UTC· resolved Oct 04, 2026, 04:13 PM UTC

1. investigating Oct 04, 2026, 03:27 PM 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 Oct 04, 2026, 03:41 PM UTC

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

3. resolved Oct 04, 2026, 04:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 26, 2026, 03:59 PM UTC· resolved Sep 26, 2026, 04:17 PM UTC

1. investigating Sep 26, 2026, 03:59 PM UTC

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

2. identified Sep 26, 2026, 04:06 PM UTC

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

3. monitoring Sep 26, 2026, 04:11 PM UTC

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

4. resolved Sep 26, 2026, 04:17 PM UTC

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

Read the full incident report →

Started Sep 21, 2026, 06:08 PM UTC· resolved Sep 21, 2026, 09:36 PM UTC

1. investigating Sep 21, 2026, 06:08 PM UTC

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

2. investigating Sep 21, 2026, 06:12 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 21, 2026, 06:13 PM 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 Sep 21, 2026, 07:09 PM UTC

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

5. monitoring Sep 21, 2026, 09:30 PM UTC

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

6. resolved Sep 21, 2026, 09:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 18, 2026, 09:53 PM UTC· resolved Sep 18, 2026, 11:23 PM UTC

1. investigating Sep 18, 2026, 09:53 PM 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 data, delayed or missing webhook deliveries, and delayed integration and automation runs. The underlying fault has cleared. Processing backlogs continued to drain. We are verifying full recovery and identifying any events that require replay.

2. monitoring Sep 18, 2026, 10:40 PM 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 resolved. Next update within 30 minutes.

3. resolved Sep 18, 2026, 11:23 PM 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.

Read the full incident report →

Started Sep 17, 2026, 04:22 PM UTC· resolved Sep 17, 2026, 05:44 PM UTC

1. investigating Sep 17, 2026, 04:22 PM 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 and our EU region are unaffected. We are actively engaged and will provide an update within 30 minutes.

2. monitoring Sep 17, 2026, 04:46 PM UTC

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

3. monitoring Sep 17, 2026, 04:46 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 17, 2026, 05:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 11:38 AM UTC· resolved Sep 16, 2026, 11:43 AM UTC

1. investigating Sep 11, 2026, 11:38 AM UTC

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

2. investigating Sep 13, 2026, 03:08 PM 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 Sep 16, 2026, 11:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 10, 2026, 09:48 AM UTC· resolved Sep 10, 2026, 09:57 AM UTC

1. resolved Sep 10, 2026, 10:27 AM 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.

Read the full incident report →

Started Aug 13, 2026, 05:06 PM UTC· resolved Aug 13, 2026, 10:17 PM UTC

1. identified Aug 13, 2026, 05:06 PM 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 Aug 13, 2026, 05:10 PM 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 access to conversations in the meantime. We will provide a further update within 30 minutes, or sooner if the situation changes.

3. monitoring Aug 13, 2026, 05:21 PM 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 Aug 13, 2026, 10:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2026, 05:05 PM UTC· resolved Aug 06, 2026, 10:08 PM UTC

1. investigating Aug 06, 2026, 05:05 PM UTC

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

2. identified Aug 06, 2026, 05:48 PM UTC

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

3. identified Aug 06, 2026, 06:46 PM UTC

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

4. identified Aug 06, 2026, 08:49 PM UTC

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

5. monitoring Aug 06, 2026, 10:02 PM UTC

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

6. monitoring Aug 06, 2026, 10:02 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Aug 06, 2026, 10:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 12:16 PM UTC· resolved Jul 22, 2026, 02:54 PM UTC

1. identified Jul 22, 2026, 12:16 PM 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 Jul 22, 2026, 12:54 PM UTC

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

3. monitoring Jul 22, 2026, 01:58 PM 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 Jul 22, 2026, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 08, 2026, 08:12 PM UTC· resolved Jul 08, 2026, 10:28 PM UTC

1. investigating Jul 08, 2026, 08:12 PM 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 Jul 08, 2026, 10:10 PM UTC

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

3. resolved Jul 08, 2026, 10:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 05, 2026, 03:50 PM UTC· resolved Jul 05, 2026, 04:12 PM UTC

1. investigating Jul 05, 2026, 03:50 PM UTC

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

2. monitoring Jul 05, 2026, 04:07 PM UTC

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

3. resolved Jul 05, 2026, 04:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 02:10 PM UTC· resolved Jun 12, 2026, 06:22 PM UTC

1. investigating Jun 12, 2026, 02:10 PM 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 will provide further updates as more information becomes available.

2. identified Jun 12, 2026, 03:05 PM 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 Jun 12, 2026, 06:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 11:13 AM UTC· resolved Jun 04, 2026, 12:02 PM UTC

1. investigating Jun 04, 2026, 11:13 AM UTC

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

2. resolved Jun 04, 2026, 12:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 09:57 AM UTC· resolved Jun 04, 2026, 11:42 AM UTC

1. monitoring Jun 04, 2026, 09:57 AM 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 Jun 04, 2026, 11:42 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 04:33 PM UTC· resolved Jun 01, 2026, 05:22 PM UTC

1. investigating Jun 01, 2026, 04:33 PM 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 Jun 01, 2026, 04:51 PM UTC

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

3. resolved Jun 01, 2026, 05:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 20, 2026, 10:06 AM UTC· resolved May 20, 2026, 10:16 AM UTC

1. investigating May 20, 2026, 10:06 AM UTC

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

2. resolved May 20, 2026, 10:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 13, 2026, 11:33 AM UTC· resolved May 13, 2026, 01:33 PM UTC

1. investigating May 13, 2026, 11:33 AM 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 investigating the root cause.

2. identified May 13, 2026, 12:16 PM UTC

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

3. monitoring May 13, 2026, 12:25 PM UTC

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

4. resolved May 13, 2026, 01:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 12, 2026, 01:41 PM UTC· resolved May 12, 2026, 02:16 PM UTC

1. investigating May 12, 2026, 01:41 PM UTC

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

2. monitoring May 12, 2026, 01:58 PM UTC

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

3. resolved May 12, 2026, 02:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 10:55 AM UTC· resolved May 16, 2026, 07:43 AM UTC

1. identified May 08, 2026, 10:55 AM 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 May 16, 2026, 07:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2026, 08:06 PM UTC· resolved May 01, 2026, 09:37 PM UTC

1. investigating May 01, 2026, 08:06 PM UTC

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

2. identified May 01, 2026, 09:14 PM UTC

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

3. resolved May 01, 2026, 09:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 05:49 AM UTC· resolved Apr 07, 2026, 08:32 AM UTC

1. investigating Apr 07, 2026, 05:49 AM UTC

   We are currently investigating this issue.

2. monitoring Apr 07, 2026, 07:28 AM 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 expected to clear completely in 30mins.

3. resolved Apr 07, 2026, 08:32 AM UTC

   All backlog fully processed.

Read the full incident report →

Started Mar 31, 2026, 11:29 AM UTC· resolved Mar 31, 2026, 01:47 PM UTC

1. identified Mar 31, 2026, 11:29 AM 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 Mar 31, 2026, 12:25 PM UTC

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

3. resolved Mar 31, 2026, 01:47 PM UTC

   This incident has been resolved.

Read the full incident report →