The historic disruption originated in Switzerland and Mexico before sweeping through the company's worldwide cloud infrastructure. While engineers initially feared a coordinated cyberattack or denial-of-service strike, log analysis confirmed the culprit was an internal software defect. The latent bug had sat dormant on Microsoft 365 gateway servers since July and was exposed when Microsoft Teams shifted traffic to the primary gateway supporting Exchange Online. Server recovery stalled repeatedly because newer, high-core machines experienced severe internal lock contention under the resulting load spikes.
Key points
Shifting traffic from Microsoft Teams into the Exchange Online gateway exposed the latent…: Shifting traffic from Microsoft Teams into the Exchange Online gateway exposed the latent flaw by altering normal system loads.
Internal testing failed to detect the defect earlier because simulations were conducted o…: Internal testing failed to detect the defect earlier because simulations were conducted on weaker hardware with fewer cores.
Recovery efforts were delayed for hours as rebooted servers suffered immediate traffic su…: Recovery efforts were delayed for hours as rebooted servers suffered immediate traffic surges that caused continuous reboot loops.
Sources checked by our analysis pipeline: 1
At 9AM last Thursday, everything seemed normal. Microsoft employees were arriving on campus, ready for a regular day of emails and meetings. But barely an hour later, one of Microsoft’s worst outages in history started to unfold, leaving employees, businesses, and many governments without access to Outlook emails for nearly 24 hours.
Inside Microsoft’s giant Outlook outage
A bug took down Microsoft’s email services for millions around the world.
A bug took down Microsoft’s email services for millions around the world.
It all started in Switzerland, according to a source familiar with the outage. Exchange Online servers that power Outlook started to fall offline. The problem quickly spread to Mexico, and then to other countries around the world, as Microsoft’s failover systems tried to shift email traffic elsewhere. Within a couple of hours, more than 80 percent of Exchange servers were unresponsive.
Sources tell me that Microsoft marked the outage as “sev0” in its internal incident tracking system, the highest level, which indicates a catastrophic level of service disruption. Hundreds of engineers began trying to figure out what had gone…
Hardware constraints on foldable displays prevent the inclusion of traditional TrueDepth sensor arrays, leaving users without full biometrics. To improve everyday navigation, engineers are testing an alternative camera-based authentication system to speed up standard lockscreen access. This option provides a half-second entry point for the device, though it operates under deliberate security restrictions.
Attackers leveraged an account signup vulnerability in a major web optimization vendor to covertly alter client scripts across hundreds of organizations. This supply chain compromise allowed the delivery of payloads capable of harvesting credentials, capturing sensitive user sessions, and altering digital asset transactions. The incident demonstrates how third-party development tools can become direct distribution vectors for multifaceted web-skimming and device-targeted threats.
Critical government infrastructure has been hit by a disruption affecting secure transmissions across the defense and intelligence landscape. This event contributes to an intensifying wave of system crashes that have repeatedly paralyzed both public and private sectors in recent times. The pattern highlights persistent vulnerabilities spanning essential operational systems nationwide.