Microsoft Experiences Global Outlook Outage
Microsoft's Outlook email service experienced a severe disruption on Thursday morning, affecting users worldwide.

Microsoft employees began their day as usual on Thursday morning, unaware of the chaos that was about to unfold.
However, within an hour, the company's Outlook email service started experiencing severe disruptions, marking one of its worst outages in history.
The outage originated in Switzerland, where Exchange Online servers powering Outlook suddenly went offline, according to a source with knowledge of the incident.
As Microsoft's failover systems attempted to redirect email traffic to other servers, the problem quickly spread to Mexico and then globally.
Exchange servers across various countries began shutting down, leaving over 80 percent unresponsive within just a couple of hours.
Microsoft internally classified the outage as "sev0, its highest level for service disruption, indicating a catastrophic failure.
Engineers sprang into action, scrambling to diagnose the cause of the problem and devise a solution to restore Outlook services.
The team's efforts were hindered by the fact that Microsoft has multiple systems designed to reroute traffic towards healthy servers in case of server failures.
Engineers were analyzing crash reports, trace logs, and kernel dumps in the early hours of the outage to pinpoint the cause of the giant failure.
Servers that had entered maintenance mode due to unusually high CPU loads became unresponsive, adding to the complexity of the situation.
In an effort to restore services, engineers attempted to bring servers back online but were quickly overwhelmed by a massive influx of traffic waiting to access the servers.
The reboot process for Exchange servers involves booting up and running an OS over a network through a Preboot Execution Environment, allowing Microsoft's support staff and engineers to manage updates remotely.
As engineers tried to identify the root cause, they found that the sudden surge in traffic from servers being rebooted was causing a reboot loop where systems kept trying and failing to come back online.
The initial investigation into the Outlook outage quickly eliminated the possibility of a cyberattack as the cause, according to insiders familiar with the matter. Engineers turned their attention to the servers' networking stack after recent rollbacks failed to resolve the issue.
They soon discovered an unusual bug that had been present on Microsoft 365 networking gateway servers since July without causing any problems. A latent defect caused servers to become overwhelmed and unresponsive under certain load conditions," wrote Charles Lamanna, leader of Microsoft's Copilot, Agents, and Platform (CAP) team, in a post on X.
The teams behind Office, Outlook, and Microsoft Teams had been experiencing issues for some time, with reports first coming in last month. The departure of Ryan Roslansky, head of Office and Teams, may have contributed to the delay in identifying the root cause of the problem.
The bug itself was a result of a fix prepared specifically for Microsoft 365 networking gateway servers, which did not affect regular versions of Windows. Microsoft's testing labs played a role in the oversight, with engineers admitting that the traffic mix and hardware used there masked the issue until it was too late.
The Outlook outage was exacerbated by two other incidents that occurred in the preceding hours. Fifteen hours before the Outlook crash, Microsoft Teams unexpectedly switched from an alternative networking gateway to its main one, which supports Exchange Online. This sudden shift increased the load on the gateway and altered its traffic patterns, as noted by Lamanna.
The combination of a latent bug, the Teams failure, and reduced server capacity proved catastrophic for the network gateway. The trio of factors triggered the problem that had been lurking since July, causing widespread disruptions to Outlook services.
Microsoft's engineers were engaged in a marathon effort to restore stability to their Exchange servers, which took nearly 24 hours to accomplish. The intervention efforts from multiple teams sometimes overlapped, complicating coordination and communication among the participants.
As Lamanna observed, the recovery process was protracted due to the sheer volume of waiting traffic that overwhelmed the returning servers, rendering them unresponsive once again. This situation led to a prolonged period of instability for Outlook users during its peak usage hours in the US.
Microsoft's automated recovery processes were not equipped to handle the widespread unresponsiveness that occurred during the Outlook outage. The company is currently conducting a thorough post-incident review, which will be published later this week, to identify areas for improvement.
The review's findings are likely to highlight the need for enhanced testing procedures to prevent similar outages in the future. This would enable Microsoft to detect and address issues before they cascade into widespread disruptions, as was seen during the peak usage hours of Outlook in the US.
The incident serves as a rare opportunity for Microsoft to learn from its mistakes and implement changes that will minimize the impact of such events on users.
Facts based on reporting originally published by The Verge.
You may republish this story, in full or in part, if you credit Noti Group and link to it (licence CC BY 4.0). Photos are not included.











