Oct <var data-var='date'> 5</var>, <var data-var='time'>21:12</var> CEST Resolved - This incident has been resolved. Oct <var data-var='date'> 5</var>, <var data-var='time'>21:11</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 5</var>, <var data-var='time'>20:40</var> CEST Identified - The issue has been identified and a fix is being implemented. Oct <var data-var='date'> 5</var>, <var data-var='time'>20:18</var> CEST Investigating - 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.

Bird.com Platform: Increased 5xx errors and delivery deliays

Oct <var data-var='date'> 4</var>, <var data-var='time'>18:13</var> CEST Resolved - This incident has been resolved. Oct <var data-var='date'> 4</var>, <var data-var='time'>17:41</var> CEST Monitoring - The situation has improved since 3:30 PM UTC. We are monitoring the services. Oct <var data-var='date'> 4</var>, <var data-var='time'>17:27</var> CEST Investigating - 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.

Increased delivery latency for SMS service

Sep <var data-var='date'>26</var>, <var data-var='time'>18:17</var> CEST Resolved - Thank you for your patience. We are seeing a full recovery. No more errors are being returned, and all queues have caught up. Sep <var data-var='date'>26</var>, <var data-var='time'>18:11</var> CEST Monitoring - We are monitoring the systems while they recover. All errors have stopped and all queues are recovering. Sep <var data-var='date'>26</var>, <var data-var='time'>18:06</var> CEST Identified - We have found the cause of the issue cycling the bad instances. Recovery expected soon. Sep <var data-var='date'>26</var>, <var data-var='time'>17:59</var> CEST Investigating - We are investigating an issue with the USA Bird Platform API. We are seeing increased Error codes returning.

Increased Error rates on USA Bird Platform API

Sep <var data-var='date'>21</var>, <var data-var='time'>23:36</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>21</var>, <var data-var='time'>23:30</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>21</var>, <var data-var='time'>21:09</var> CEST Identified - We have identified the issue and are testing a fix. We expect logs to be available again with in an hour. Sep <var data-var='date'>21</var>, <var data-var='time'>20:13</var> CEST Update - The current failure is in log retrieval not flow runs. Flows are running with out impact. Logs are failing to load upon request. Sep <var data-var='date'>21</var>, <var data-var='time'>20:12</var> CEST Update - We are continuing to investigate this issue. Sep <var data-var='date'>21</var>, <var data-var='time'>20:08</var> CEST Investigating - We are currently investigating an issue in EU that is causing some flows to fail.

Flow Logs failures in EU

Sep <var data-var='date'>19</var>, <var data-var='time'>01:23</var> CEST Resolved - 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. Sep <var data-var='date'>19</var>, <var data-var='time'>00:40</var> CEST Monitoring - 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. Sep <var data-var='date'>18</var>, <var data-var='time'>23:53</var> CEST Investigating - 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.

Elevated processing delays — US region

Sep <var data-var='date'>17</var>, <var data-var='time'>19:44</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>17</var>, <var data-var='time'>18:46</var> CEST Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>17</var>, <var data-var='time'>18:46</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>17</var>, <var data-var='time'>18:22</var> CEST Investigating - 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.

Elevated API errors and voice call setup failures (US)

Sep <var data-var='date'>16</var>, <var data-var='time'>13:43</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>13</var>, <var data-var='time'>17:08</var> CEST Update - 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. Sep <var data-var='date'>11</var>, <var data-var='time'>13:38</var> CEST Investigating - We are currently investigating the issue with calls to UK numbers resulting in one-way audio

Incoming calls to UK with one-way audio

Sep <var data-var='date'>10</var>, <var data-var='time'>12:27</var> CEST Resolved - 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.

SMS processing disruption

Aug <var data-var='date'>20</var>, <var data-var='time'>00:23</var> CEST Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>19</var>, <var data-var='time'>22:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>19</var>, <var data-var='time'>15:53</var> CEST Scheduled - We will perform an unexpected maintenance in order to assure continuity of our services. During the time window short delays and intermittent unavailability may occur. This maintenance doesn't impact SMS or Voice services.

Conversations, Messaging and Contacts API maintenance

Aug <var data-var='date'>14</var>, <var data-var='time'>00:17</var> CEST Resolved - This incident has been resolved. Aug <var data-var='date'>13</var>, <var data-var='time'>19:21</var> CEST Update - 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. Aug <var data-var='date'>13</var>, <var data-var='time'>19:10</var> CEST Monitoring - 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. Aug <var data-var='date'>13</var>, <var data-var='time'>19:06</var> CEST Identified - 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.

Inbox — Service Outage

Aug <var data-var='date'> 7</var>, <var data-var='time'>00:08</var> CEST Resolved - This incident has been resolved. Aug <var data-var='date'> 7</var>, <var data-var='time'>00:02</var> CEST Update - We are continuing to monitor for any further issues. Aug <var data-var='date'> 7</var>, <var data-var='time'>00:02</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 6</var>, <var data-var='time'>22:49</var> CEST Update - We identified the root cause and continuing to work on a fix for this issue. Aug <var data-var='date'> 6</var>, <var data-var='time'>20:46</var> CEST Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'> 6</var>, <var data-var='time'>19:48</var> CEST Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'> 6</var>, <var data-var='time'>19:05</var> CEST Investigating - We are noticing failures in the connector service. We are investigating to identify the root cause

Connectors failing for some customers.

Jul <var data-var='date'>22</var>, <var data-var='time'>16:54</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'>22</var>, <var data-var='time'>15:58</var> CEST Update - 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. Jul <var data-var='date'>22</var>, <var data-var='time'>14:54</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>22</var>, <var data-var='time'>14:16</var> CEST Identified - 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.

Dashboard Search Indexing Issue

Jul <var data-var='date'> 9</var>, <var data-var='time'>00:28</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'> 9</var>, <var data-var='time'>00:10</var> CEST Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'> 8</var>, <var data-var='time'>22:12</var> CEST Investigating - 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.

Delay in processing Message & Contact Objects - Impact limited to customer hosted on us-west-1 region

Jul <var data-var='date'> 5</var>, <var data-var='time'>18:12</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'> 5</var>, <var data-var='time'>18:07</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 5</var>, <var data-var='time'>17:50</var> CEST Investigating - We are seeing a spike in errors in the Journeys logs right now. We are investigating the issue.

Journeys failure rate increase

Jun <var data-var='date'>12</var>, <var data-var='time'>20:22</var> CEST Resolved - This incident has been resolved. Jun <var data-var='date'>12</var>, <var data-var='time'>17:05</var> CEST Identified - We are continuing to monitor increased WhatsApp message delivery failures caused by ongoing disruptions in Meta’s services, as confirmed by Meta. Jun <var data-var='date'>12</var>, <var data-var='time'>16:10</var> CEST Investigating - 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.

WhatsApp message delivery issues

Jun <var data-var='date'> 4</var>, <var data-var='time'>14:02</var> CEST Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>13:13</var> CEST Investigating - Flows and Journeys are unable to retrieve the Message Body property for Conversation Messages. We are investigating the issue.

Flows and Journeys unable to retrieve the Message Body for Conversation Messages

Jun <var data-var='date'> 4</var>, <var data-var='time'>13:42</var> CEST Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>11:57</var> CEST Monitoring - 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.

Increase of delivery latency for SMS messages

Jun <var data-var='date'> 1</var>, <var data-var='time'>19:22</var> CEST Resolved - This incident has been resolved. Jun <var data-var='date'> 1</var>, <var data-var='time'>18:51</var> CEST Monitoring - The processing has caught up and we are monitoring to ensure it doesn't get behind again. Jun <var data-var='date'> 1</var>, <var data-var='time'>18:33</var> CEST Investigating - 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.

Conversations data processing is behind

May <var data-var='date'>20</var>, <var data-var='time'>12:16</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>12:06</var> CEST Investigating - We are currently investigating an issue where the overview pages for Journeys, Flows, Search and other products are down and unavailable.

Overview pages and Search down

May <var data-var='date'>16</var>, <var data-var='time'>09:43</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>12:55</var> CEST Identified - 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.

SMS delivery interruption - Netherlands - KPN 20408

May <var data-var='date'>13</var>, <var data-var='time'>15:33</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>13</var>, <var data-var='time'>14:25</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>13</var>, <var data-var='time'>14:16</var> CEST Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>13</var>, <var data-var='time'>13:33</var> CEST Investigating - 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.

Issues Listing Journeys in UI [EU]

May <var data-var='date'>12</var>, <var data-var='time'>16:16</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>12</var>, <var data-var='time'>15:58</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>12</var>, <var data-var='time'>15:41</var> CEST Investigating - We are currently experiencing delays in processing journeys. The team is actively working to increase processing speed and reduce delays.

Journey Processing Delays [EU]

May <var data-var='date'> 1</var>, <var data-var='time'>23:37</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 1</var>, <var data-var='time'>23:14</var> CEST Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'> 1</var>, <var data-var='time'>22:06</var> CEST Investigating - We are seeing elevated errors with conversations involving bots in the EU region and we are currently investigating this issue.

Elevated Errors with Conversations API

Apr <var data-var='date'> 7</var>, <var data-var='time'>10:32</var> CEST Resolved - All backlog fully processed. Apr <var data-var='date'> 7</var>, <var data-var='time'>09:28</var> CEST Monitoring - 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. Apr <var data-var='date'> 7</var>, <var data-var='time'>07:49</var> CEST Investigating - We are currently investigating this issue.

Wait step in automations having degraded performance

Mar <var data-var='date'>31</var>, <var data-var='time'>15:47</var> CEST Resolved - This incident has been resolved. Mar <var data-var='date'>31</var>, <var data-var='time'>14:25</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Affected customers are advised to retry their campaigns. Mar <var data-var='date'>31</var>, <var data-var='time'>13:29</var> CEST Identified - 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.

Is MessageBird down?

MessageBird status is UP

Lastest published events

Bird.com Platform: Increased 5xx errors and delivery deliays

Increased delivery latency for SMS service

Increased Error rates on USA Bird Platform API

MessageBird Services, Components and Regions

Recent MessageBird events

Bird.com Platform: Increased 5xx errors and delivery deliays

Increased delivery latency for SMS service

Increased Error rates on USA Bird Platform API

Flow Logs failures in EU

Elevated processing delays — US region

Elevated API errors and voice call setup failures (US)