Microsoft Issues
DegradedReported Nov 13, 2026 at 3:05 AM UTC · Resolved Nov 13, 2026 at 7:30 PM UTC · Duration: 16h 25m
Affected Systems
Microsoft has been experiencing issues today, causing an inability to deliver some mail to their platform. As of the time of this message, we have seen this error from their servers 25,068 times: "421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel" This does not mean that we are exceeding a limit in connections to them, it means they are exceeding a limit of connections they can open. As of right now, this is still ongoing. However, there is one more thing you should be aware of: We retry these emails, and if they continue to fail we send mail to our backup relay provider (mail.baby) to attempt delivery again. Their outbound filters are more strict than ours, which can cause you to receive this bounce message: "550 200 This message was classified as rSPAM and may not be delivered" At this time, we cannot reliably surface to you that this was not the primary issue. The primary issue is that we sent it to mail.baby in the first place, because of our inability to deliver mail to Microsoft's servers. Your mail was not simply rejected as spam, it was just rejected from retrying a third time.
Updates
Looks like it's been resolved for a bit now.
This is still an ongoing problem. Microsoft still cannot accept email.
We've changed configuration, for now these emails will be bounced back so that you can see this error in the bounce email: "421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel" Microsoft just can't accept email right now, so you'll need to re-send the email if you want it delivered.
Microsoft has been experiencing issues today, causing an inability to deliver some mail to their platform. As of the time of this message, we have seen this error from their servers 25,068 times: "421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel" This does not mean that we are exceeding a limit in connections to them, it means they are exceeding a limit of connections they can open. As of right now, this is still ongoing. However, there is one more thing you should be aware of: We retry these emails, and if they continue to fail we send mail to our backup relay provider (mail.baby) to attempt delivery again. Their outbound filters are more strict than ours, which can cause you to receive this bounce message: "550 200 This message was classified as rSPAM and may not be delivered" At this time, we cannot reliably surface to you that this was not the primary issue. The primary issue is that we sent it to mail.baby in the first place, because of our inability to deliver mail to Microsoft's servers. Your mail was not simply rejected as spam, it was just rejected from retrying a third time.