(Resolved) Office365 looks to be down with "PRX3 NextHop: substrate-int.office.com" and other non-connection SMTP Responses

Date/Time:  2026 12 Nov, 17:20 GMT:

Office 365 Email Delivery Delays 
Looks like for about the last hour, Microsoft M365 is not accepting mail.

We are seeing a lot of SMTP Responses like the following:

451 4.7.0 Temporary server error. Please try again later. PRX5 NextHop: substrate-int.office.com. RemoteHost: YT4PR01CA0040. Network Error: 10054 [BN5PEPF00046988.namprd02.prod.outlook.com 2026-11-12T19:10:01.241Z 08DF40E72E786C13]

The messages are not being lost / rejected, but deferred, and we will retry the messages periodically.


Official Microsoft Announcement:
Microsoft service health status

Also

Microsoft 365 down? Current problems and outages | US



Unfortunately, since it looks like M365 can't accept mails, there isn't any other action accept to wait.



Update:  20:00 GMT

From: Microsoft service health status
----
Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service. 

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC (about 2 hours from now)

----

Update: 21:55 GMT

From:  Microsoft service health status
----

Current status: We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.


Previous status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

----

Note:  Other MS services are also affected, not just EOL/Mail.


Update: 23:10 GMT

From:  Microsoft service health status
---

Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

 

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

---
What we are seeing:  The vast majority of messages to Office365 are not getting accepted


Update: 13 Nov, 1:15 GMT


From:  Microsoft service health status (last update: 13 Nov, 1:06)
---

More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.
** there are a lot of feature affected ** 

Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery. The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

---

What we are seeing:  The vast majority of messages to Office365 are not getting accepted, there are many different errors, including but not limited to the following:

451 4.7.0 Temporary server error. Please try again later. PRX9 RemoteHost: YT3PR01CA0036. ErrorCode 10054
451 4.7.0 Temporary server error. Please try again later. PRX3 NextHop: substrate-int.office.com. Last IP: 2603:10b6:930:1e::5:25
421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel
451 4.3.2 Temporary server error. Please try again later ATTR55
421 4.3.2 The maximum number of concurrent connections per resource forest has exceeded a limit, closing transmission channel. pod51097ehf.outlook.com. PRX8
451 4.3.2 Temporary server error. Please try again later ATTR1 [Name=TenantAttributionAndInboundConnectorAgent][AGT=ATR][MxId=11BE824EDFD76975]
451 4.7.700 PFA agent busy, please try again. [Name=Protocol Filter Agent][AGT=PFA][MxId=11BE82544CC4DAE0]

As well as just straight up timeouts:
connect to redacted-com.mail.protection.outlook.com[52.101.9.4]:25: Operation timed out


Update: 13 Nov, 10:00 GMT
==> M365 looks to be accepting more mail now


From:  Microsoft service health status (last update: 13 Nov, 1:06)
---

More info: User impact: Users may be unable to connect to multiple Microsoft 365 services. More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

- Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed.

-  and many other features are affected.

Current status: Recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure. Global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline. 

Network and traffic-management actions remain active. To protect email during recovery, we’re continuing to prioritize queue and backlog processing, and the email timeout window has been extended to 48 hours to preserve delayed messages. 

At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.

---

What we are seeing:  The vast majority of messages to Office365 are not getting accepted, there are many different errors, including but not limited to the following (changed since last update):

451 4.7.0 Temporary server error. Please try again later. (PRX3|PRX4|PRX5) NextHop: substrate-int.office.com. ...
451 4.3.2 Temporary server error. Please try again later ATTR2
421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel
421 4.3.2 The maximum number of concurrent connections per resource forest has exceeded a limit, closing transmission channel

As well as just straight up timeouts:
connect to redacted-com.mail.protection.outlook.com[52.101.9.4]:25: Operation timed out



Update: 13 Nov, 12:36 GMT


Microsoft hasn't updated Microsoft service health status yes, but we are seeing -a lot- more mail successfully being delivered now. On the SpamTitan Cloud/Skellig servers, we have already:
-- flushed the deferred queues and 
-- stopped and started postfix to clear the Dynamic Recipient Verification cache.

SpamTitan Gateway and Private Cloud customers, you can do the same in
--- Reporting > System Information > Services
Stop Postfix
Stop Amavisd / Start Amavisd
Start Postfix

-- Reporting > System Information > Tools > Flush Mail Queue

Flush Mail Queue takes all the Deferred messages and puts them in the Active queue for immediate attempted redelivery.


Update: 13 Nov, 15:30 GMT
--- looks like the last of the M365 problems were resolved around 13 Nov, 13:30 GMT