64 recorded Messagebird incidents since August 2025, with official updates, affected components, duration and resolution information.
We are currently pushing a fix for an issue we noticed with a some Whatsapp messages not getting sent.
The backlog has caught up. All messages have been sent. We are monitoring to ensure the fix holds.
This incident has been resolved. All messages have been sent.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The situation has improved since 3:30 PM UTC. We are monitoring the services.
This incident has been resolved.
We are investigating an issue with the USA Bird Platform API. We are seeing increased Error codes returning.
We have found the cause of the issue cycling the bad instances. Recovery expected soon.
We are monitoring the systems while they recover. All errors have stopped and all queues are recovering.
Thank you for your patience. We are seeing a full recovery. No more errors are being returned, and all queues have caught up.
We are currently investigating an issue in EU that is causing some flows to fail.
We are continuing to investigate this issue.
The current failure is in log retrieval not flow runs. Flows are running with out impact. Logs are failing to load upon request.
We have identified the issue and are testing a fix. We expect logs to be available again with in an hour.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating the issue with calls to UK numbers resulting in one-way audio
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.
This incident has been 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.
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.
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.
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.
This incident has been resolved.
We are noticing failures in the connector service. We are investigating to identify the root cause
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We identified the root cause and continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are seeing a spike in errors in the Journeys logs right now. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to monitor increased WhatsApp message delivery failures caused by ongoing disruptions in Meta’s services, as confirmed by Meta.
This incident has been resolved.
Flows and Journeys are unable to retrieve the Message Body property for Conversation Messages. We are investigating the issue.
This incident has been resolved.
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.
This incident has been resolved.
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.
The processing has caught up and we are monitoring to ensure it doesn't get behind again.
This incident has been resolved.
We are currently investigating an issue where the overview pages for Journeys, Flows, Search and other products are down and unavailable.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
