MessageBird Outage History

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.

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.

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.

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.

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

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.

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

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.

Flows is missing the Message Body property for Conversation Messages. We are investigating the issue.

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.

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

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.

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

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

We are currently investigating this issue.

We are currently investigating this issue.

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

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

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.