All Systems Operational

Bird Platform Operational
Site bird.com Operational
Engagement Platform / CRM Operational
Dashboard - app.bird.com Operational
AI Hub - Europe Operational
AI Hub - US (West) Operational
AI Hub - Asia (India) Operational
Analytics - Europe Operational
Analytics - US (West) Operational
Analytics - Asia (India) Operational
Campaigns - Europe Operational
Campaigns - US (West) Operational
Campaigns - Asia (India) Operational
Channels - Europe Operational
Channels - US (West) Operational
Channels - Asia (India) Operational
Content (Products, Templates) - Europe Operational
Content (Products, Templates) - US (West) Operational
Content (Products, Templates) - Asia (India) Operational
Connectors - Europe Operational
Connectors - US (West) Operational
Connectors - Asia (India) Operational
Contacts - Europe Operational
Contacts - US (West) Operational
Contacts - Asia (India) Operational
Chat Widget - Europe Operational
Chat Widget - US (West) Operational
Chat Widget - Asia (India) Operational
Flows - Europe Operational
Flows - US (West) Operational
Flows - Asia (India) Operational
Inbox - Europe Operational
Inbox - US (West) Operational
Inbox - Asia (India) Operational
Journey - Europe Operational
Journey - US (West) Operational
Journey - Asia (India) Operational
Organizations (Billing, IAM, Settings, Wallets) - Europe Operational
Organizations (Billing, IAM, Settings, Wallets) - US (West) Operational
Organizations (Billing, IAM, Settings, Wallets) - Asia (India) Operational
Payments - Card - Europe Operational
Payments - Card - US (West) Operational
Payments - Card - Asia (India) Operational
Payments - Pay - Europe Operational
Payments - Pay - US (West) Operational
Payments - Pay - Asia (India) Operational
Connectivity Platform Operational
Dashboard - dashboard.messagebird.com Operational
SMS - Connectivity - APAC Operational
SMS - Connectivity - EMEA Operational
SMS - Connectivity - LATAM Operational
SMS - Connectivity - NORAM Operational
Voice - Connectivity - Global Operational
SMS - API Operational
SMS - SMPP - EU - SMPP01 Operational
SMS - SMPP - EU - SMPP02 Operational
SMS - SMPP - EU - SMPP03 Operational
SMS - SMPP - APAC Operational
SMS - API V1 Operational
SMS - Mail to SMS Relay Service Operational
Voice - API Operational
Voice - SIP Trunking Operational
Inbox Operational
Flow Builder Operational
Omnichannel Chat Widget Operational
Numbers - API Operational
Conversations - API Operational
Messaging - API Operational
Email Channel Operational
WhatsApp Channel Operational
24sessions Operational
Instance Operational
Data API Operational
Keeper API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Nov 14, 2026

No incidents reported today.

Nov 13, 2026

Resolved - This incident is resolved, and delivery to Microsoft mailboxes is back to normal.

From about 17:30 UTC on 12 November, Microsoft's mail service returned temporary errors for most delivery attempts. The cause was an incident on Microsoft's side (Microsoft incident EX1550543), and delivery to other mailbox providers was not affected. Microsoft's errors dropped sharply from about 13:30 UTC on 13 November. Delivery was back to normal rates by 14:35 UTC, and Microsoft's error levels have been normal since about 15:10 UTC (09:10 CST).

We queued all affected mail and retried it automatically. Most of it has now been delivered, and the rest of the retry queue will finish over the next few hours. You don't need to do anything, and you don't need to resend.

If your messages use a short expiration (TTL) setting, some may have expired before Microsoft accepted them. Those messages were returned as bounces and appear in your bounce events. You may want to resend any time-sensitive messages that expired.

Thank you for your patience while Microsoft resolved this issue.

Nov 13, 17:20 CET
Update - Delivery to Microsoft (Outlook.com, Hotmail and Office 365) has recovered

Delivery to Microsoft mailboxes is back to normal. Starting around 17:30 UTC on 12 November, an incident on Microsoft's side (Microsoft incident EX1550543) caused delivery delays. The errors from that incident have now returned to normal levels, and new mail to Microsoft is being accepted at normal rates and speed.

We are finishing the automatic retry of mail that was delayed during the incident. Most of it has already been delivered, and the rest is draining steadily. Some older delayed messages may still arrive over the next while. You don't need to do anything, and you don't need to resend.

If your messages use a short expiration (TTL) setting, some may have expired before Microsoft accepted them. Those messages were returned as bounces and appear in your bounce events.

Nov 13, 16:27 CET
Monitoring - Delivery to Microsoft (Outlook.com, Hotmail, Microsoft 365) is recovering

Microsoft is still recovering from its service incident (Microsoft reference EX1550543). The problem was on Microsoft's side. Our platform has run normally throughout, and delivery to other mailbox providers was not affected.

Since about 11:30 UTC (5:30 AM US Central), delivery to Microsoft recipients has improved a lot. Delivery volume is back in its normal range. We're also working through the backlog of mail that was queued during the outage, and those retries make up a large share of what Microsoft is accepting right now. About 3 in 10 delivery attempts to Microsoft are still being deferred, compared with more than 9 in 10 at the worst point. That's still above normal, so some messages to Microsoft recipients may take longer than usual to arrive while Microsoft finishes recovering.

Microsoft reports that recovery is moving forward across Europe, Asia Pacific and North America, and that some users may still see intermittent issues.

What this means for you: You don't need to do anything. We'll keep retrying any deferred mail automatically. If you set short expiration windows on your messages, some messages to Microsoft recipients may have expired before Microsoft accepted them.

We'll keep watching delivery to Microsoft closely and will post again once it's fully back to normal.

Nov 13, 13:49 CET

Nov 12, 2026

Resolved - Microsoft has confirmed an incident affecting Exchange Online and Microsoft 365 connectivity in all regions. It’s tracked as EX1550543, and you can follow Microsoft’s updates at https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect.

Since about 17:30 UTC on November 12, Microsoft’s mail servers have been answering a large share of delivery attempts with temporary errors. This affects Outlook.com, Hotmail, Live, MSN and Office 365 recipients. The errors include “451 4.7.0 Temporary server error”, “421 4.3.2 The maximum number of concurrent server connections has exceeded a limit” and “451 4.7.700 PFA agent busy”. The problem is on Microsoft’s side and affects senders across the industry. SparkPost’s own systems are working normally.

Affected messages are not lost. SparkPost queues them and keeps retrying automatically, and many are already going through on a retry. You’ll see these attempts as delay events in your event data. Recipients at Microsoft may get mail later than usual until Microsoft resolves EX1550543. Delivery to other mailbox providers is not affected.

You don’t need to do anything, and please don’t send these messages again. Resending creates duplicates once the queued mail goes through. If you’ve set a short message expiration (for example on one-time passcodes), those messages may expire before Microsoft recovers.

We’re watching this closely and will post an update as soon as things change.

Nov 12, 21:00 CET

Nov 11, 2026

No incidents reported.

Nov 10, 2026

No incidents reported.

Nov 9, 2026

No incidents reported.

Nov 8, 2026

No incidents reported.

Nov 7, 2026

No incidents reported.

Nov 6, 2026

No incidents reported.

Nov 5, 2026

No incidents reported.

Nov 4, 2026

No incidents reported.

Nov 3, 2026

No incidents reported.

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.