Microsoft CEO Satya Nadella apologizes for global Outlook outage traced to latent bug

RUKUS· · 32h ← 12d
Go Rogue

A global Microsoft outage beginning November 12, 2026 knocked Outlook, Teams, and Copilot offline for nearly 24 hours across 74 countries.

Microsoft traced the failure to a latent bug dating to July, triggered when a network gateway lost capacity and took on extra traffic.

The company ruled out a cyberattack and AI as causes, and said services were fully restored on November 14.

Governments, hospitals, courts, police, and banks worldwide were disrupted, with more than 7.4 million outage reports logged.

Chief executive Satya Nadella apologized, and Microsoft has promised but not yet published a final root-cause report.

Microsoft 365 is used by more than 430 million people, and the episode renewed debate over reliance on a single provider.

  1. Microsoft apologized and said the incident was a technical issue, introduced by an issue during an earlier network capacity upgrade that surfaced after a recent network change, not related to cyber or AI.

    Microsoft said it was deeply sorry for the disruption the incident caused its customers and partners, and that it takes the trust they place in its services extremely seriously.

  2. A widespread outage of Microsoft 365 services including Outlook, Teams, Word, and Excel hit users across the Americas on November 12, 2026, after a number of servers unexpectedly failed automated health checks.

  3. Microsoft extended the email timeout window to 48 hours so delayed messages would not be discarded.

  4. Japanese Deputy Chief Cabinet Secretary Masanao Ozaki said the outage had affected the Japanese government's IT infrastructure and that officials were keeping a close eye on developments.

  5. Microsoft began investigating Exchange Online mailbox connectivity problems in the Americas on November 12 after resolving a separate Teams incident that morning, later saying users in any region could be affected.

  6. Australian Home Affairs Minister Tony Burke said Microsoft believed it was dealing with something similar to the CrowdStrike incident, where an update had gone awry.

    US Representative Josh Gottheimer said he asked for a briefing on the outage and questioned whether something nefarious had gone on at Microsoft.

  7. Microsoft said part of its infrastructure was experiencing elevated load as more than 130,000 users reported Outlook problems, and it began redistributing traffic worldwide and restarting affected servers.

  8. Microsoft said its fixes were not taking effect as expected and opened all available pathways to restore service.

    The outage left congressional offices on Capitol Hill without email for much of November 12, stalling work during the lame-duck session.

  9. Microsoft observed that servers brought back online could become unresponsive again when returning traffic overwhelmed them, despite added traffic management.

    Outage reports came from 74 countries and territories within about an hour, and Immigration New Zealand paused all visa processing.

    New Zealand Law Society property law section chairperson Kristine King advised practitioners to call the lawyer on the other side of their transaction and use alternatives such as Gmail or WhatsApp to keep property settlements moving.

  10. Microsoft's Microsoft 365 Status account wrote that it was "aggressively pursuing all pathways to reduce impact."

  11. Australian Medical Association president Michael Bonning said, "We don't use any of these things for direct patient care... We've always got workarounds for that."

  12. Cybersecurity expert Troy Hunt said, "Microsoft is a massive part of the internet backbone and reminds us how critical email still is."

  13. Technology analyst Rupert Goodwins said the outage is very embarrassing for Microsoft, and forecast it will only increase the pressure to find alternatives to the company.

  14. Microsoft executive Charles Lamanna said technical challenges and failure modes made recovery more difficult than normal, and said Microsoft would shortly publish a post-mortem with a step-by-step timeline.

    OpenAI and Anthropic each reported problems connecting their AI tools with Microsoft 365 services.

    Yorkville tech analyst Dan Ives wrote, "Microsoft in a Friday the 13th moment as global outage [causes] a very bad day in Redmond. There will be major questions for MSFT in this global outage."

  15. Access to Exchange Online and Outlook on the web began recovering from about 12:30 MESZ on November 13.

  16. Britain's National Health Service turned to paper records as staff lost access to email.

  17. Most Microsoft services were back online by 3 p.m. ET on November 13, with Outlook reports on Downdetector down from about 130,000 at the peak.

    RSM Australia risk advisory partner Ashwin Pal said losses from the outage downtime are likely in the billions.

  18. Japanese workers and businesses turned to fax machines and other analog measures while Microsoft 365 stayed down.

  19. Internet analyst Doug Madory said traffic was returning to Microsoft's services after about 18 hours of downtime.

  20. CrowdStrike and Palo Alto Networks shares each rose 3 percent, while Microsoft stock slipped 0.8 percent.

    CrowdStrike and Palo Alto Networks shares climbed 3 percent, while Microsoft stock slipped 0.8 percent.

  21. Nextcloud co-founder Jos Poortvliet said, "Mistakes happen in the IT industry. This holds true for companies of all sizes, including us. Our heart goes out to all the admins today."

  22. Phishing messages offering Microsoft 365 outage-related password resets appeared within hours of the outage.

    University of New South Wales professor Richard Buckland observed that organizations still lack workarounds more than two years after the CrowdStrike failure of July 2024.

  23. New York City suspended evictions scheduled for November 13 after its Department of Investigation consulted the Civil Court.

    Chi Onwurah, chair of the UK parliament's Science and Technology Committee, said, "the global Microsoft outage only serves to highlight once again the lack of resilience in the UK's digital infrastructure, and the dangers that this dependency can pose to our security, economy and public services".

    Kentik director Doug Madory forecast that the outage is absolutely going to go down as one of the big ones, up there with the Facebook outage of October 2021.

  24. Small Business Charter executive director Flora Hamilton called the outage a "stark reminder" of how much firms rely on digital systems like Outlook to keep their operations running.

    AI strategist Walter Pasquarelli said the outage had "put their vulnerabilities and dependence in plain sight" for governments, businesses, and critical infrastructure.

    Former software engineer Gergely Orosz said what was unusual about the outage was the time it took Microsoft to recover, and suggested splitting services by region as Amazon's AWS already does.

  25. Microsoft promised a full post-incident report with root cause and defense-in-depth actions once service was fully restored.

    Microsoft executive Charles Lamanna wrote, "For now we can confirm that there is no indication this is the result of malicious or cyber activity. Our teams are reviewing what happened and how we can prevent similar issues going forward."

  26. House Homeland Security Committee Chair Andrew Garbarino said he is "seeking more information" on the outage from Microsoft and CISA, calling it a reminder of the concentration risk that comes when critical infrastructure relies on a small number of providers.

    The United Kingdom's National Cyber Security Centre warned there may be "a rise in scam calls or approaches impersonating IT help desks or Microsoft" in relation to the outage.

    Florian Druckenthaner, spokesperson for Germany's Federal Ministry for Digital Transformation and Government Modernisation, said his office anticipates the German economy will be significantly impacted by the outage.

  27. Microsoft said more than 7.4 million outage reports had been logged worldwide, making the disruption one of the longest in its history.

    GMB union public services head Rachel Harrison said NHS staff who received emergency calls were "unable to refer patient details in the normal way", creating a massive backlog.

  28. European exchange operator Euronext told listed companies to communicate corporate information by phone during the outage.

  29. On an overnight video conference, Scott Guthrie, the most senior executive over Microsoft's computing infrastructure, told teams to prioritize restoring Outlook as employees debated how to prevent returning demand from overwhelming restored servers.

    Microsoft said, "Given the scale of demand, we restored services gradually, validating stability at each stage," adding that while this took longer, it helped ensure a stable restoration.

    Analysts at William Blair wrote that the outage could prompt enterprises to reassess their dependence on Microsoft's infrastructure.

  30. In Britain, a criminal trial in Manchester was suspended for the day and jurors were sent home.

    The British government said it was "working closely" with Microsoft to assess any impact on public services, with "robust contingency plans" in place.

  31. Microsoft said on November 14, 2026 that it had restored service to the remaining affected customers and regions.

  32. Microsoft's preliminary Post-Incident Report said a change deployed to its cloud gateway from July created a bug in which CPU and memory resources could become exhausted.

    The report said the bug escaped pre-release testing because the test hardware was less powerful than some production machines.

    The report said the gateway fleet was running 14 percent below optimal capacity when a standard maintenance switchover shifted traffic, freezing more than 80 percent of affected gateways.

    Microsoft said restarts and rollbacks failed because queued requests retriggered the exhaustion, recovery required a targeted update, and Exchange Online could not be rerouted like Teams and OneDrive.

    Microsoft said it added capacity and traffic-distribution guardrails, and expected to publish its final report on November 20.

  33. Microsoft could not simply roll back the changes the bug caused, and servers briefly became unresponsive again when returning traffic overwhelmed them after service resumed.

    Charles Lamanna wrote, "We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations."

  34. A source said the outage began in Switzerland and spread to Mexico and then worldwide as Microsoft's failover systems shifted email traffic.

    Within a couple of hours, more than 80 percent of Exchange Online servers were unresponsive.

    Microsoft internally marked the incident as sev0, its highest incident level, and hundreds of engineers worked from crash reports, trace logs, and kernel dumps to restore service.

  35. On November 18, 2026, Microsoft chief executive Satya Nadella told a business conference in New York he was extremely sorry to the people affected by the outage.

    Nadella described the failure as a rare combination of conditions: a hidden bug that sat in the system until a particular traffic pattern triggered it.

    In a television interview, Nadella said Microsoft should have done the testing in advance and built bulkheads so a local failure could not spread into a global outage.

    Microsoft had not published a final root-cause report on the outage and reported no customer credits, refunds, or lost contracts tied to it.

    Microsoft chief executive Satya Nadella told a business conference in New York he was "extremely sorry" to the people affected by the outage.

    In a television interview, Nadella said Microsoft should have done the testing in advance.

    Microsoft says it will act on the architectural and operational lessons from the outage, with no timeline and no budget attached.

  36. Walayat Hussain, an associate professor at Australian Catholic University, said there is no sign of a hacker in the outage, which looks like Microsoft's own systems tripping over themselves, and that the accident being an accident is the real warning.

Sign in with subscription

Free during the beta.

Clear all notifications?

Your bells stay on. Only this list empties.