Microsoft's Outlook meltdown: a July bug, a Teams failover and a 1,000-person call
A dormant bug on Microsoft 365 networking gateway servers helped knock out Outlook for nearly 24 hours, starting in Switzerland and spreading worldwide. More than 80 percent of Exchange servers went unresponsive, and Microsoft's own failover systems spread the pain. Redmond now promises a full review later this week.
- Original source: theverge.com.
- The source published it on Nov 17, 2026 at 5:00 PM.
- No second outlet has reported it yet. Treat it as a single-source claim.
The trouble began in Switzerland. Exchange Online servers that power Outlook started dropping offline, and the failure raced through Mexico and on to the rest of the world. Within a couple of hours, more than 80 percent of Exchange servers were unresponsive, and it took Microsoft nearly 24 hours to get email flowing again for employees, businesses and governments.
Inside Microsoft, the incident was tagged "sev0" — the company's highest severity level, signaling catastrophic disruption, according to The Verge. Hundreds of engineers scrambled through crash reports, trace logs and kernel dumps. The bridge call they ran for the duration maxed out at 1,000 participants. Microsoft's failover systems worked as designed, but that design pushed the sickness outward: traffic got shuffled toward servers that were about to break too.
Some machines fell into maintenance mode under unusually heavy CPU loads, and reboots backfired. Restarting servers flooded the monitoring systems with traffic, trapping them in a loop where they kept trying and failing to come back. Even Microsoft's usual trick of reverting recent changes didn't help.
Engineers quickly ruled out an attack after reviewing crash reports and logs, and worked with DDoS specialists to check whether someone had hit them. Instead they found a bug that had been sitting quietly on Microsoft 365 networking gateway servers since July. "A latent defect caused servers to become overwhelmed and unresponsive under certain load conditions," wrote Charles Lamanna, who leads Microsoft's Copilot, Agents, and Platform team. Office, Outlook and Teams all started reporting to Lamanna last month, after Office and Teams chief Ryan Roslansky left the company.
A preliminary post-incident report describes the flaw as one affecting select Windows servers "due to lock contention inside an internal Windows process" — a fix built specifically for those gateway machines, so regular Windows was never exposed. Microsoft's test labs never caught it. "The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores," Lamanna wrote.
Three things had to line up. Fifteen hours before the Outlook failure, Teams switched over from an alternative networking gateway to the main one behind Exchange Online, changing traffic patterns and adding load. Roughly 14 percent of that gateway's server capacity was already out of service from an unrelated problem the day before. Add the dormant bug, and the gateway tipped. "Our normally automated recovery processes were not designed to restore service from this broad unresponsive state," Lamanna wrote. Microsoft says a final post-incident review lands later this week.
TopicsMicrosoft · Outlook · Exchange Online · Microsoft Teams · Microsoft 365 · Charles Lamanna · Ryan Roslansky · The Verge
Source: theverge.com
Written by AI from verified reporting.
More stories
- Tech & AI cryptobriefing.com 0 viewsAnthropic IPO order book shuts at 4 p.m. ET, reportedly six times oversubscribed
- Tech & AI breakingthenews.net 0 viewsNvidia Taps Heidrick & Struggles to Run Its CEO Search
- Tech & AI x.com 0 viewsOpenAI launches GPT-6.2 Astra and Sol, billed as its most powerful models yet
- Tech & AI x.com 0 viewsAnthropic eyes IPO price above $80 as demand blows past range

