Choose Rich Live
Tech

Microsoft traces global outage to undetected July network bug

Microsoft revealed that a software defect introduced in a July update triggered a massive global outage across services including Outlook and Teams, knocking out over 80% of servers at its peak.

A Microsoft corporate sign displayed in front of a modern glass office building.
Image: @qz

Microsoft revealed in a preliminary post-incident report that a software defect lurking undetected since July triggered a massive global outage that crippled Microsoft 365 services, including Outlook, Teams, and Copilot. According to the company's disclosures, more than 80% of servers behind its networking gateway became unresponsive at the height of the disruption, knocking services offline worldwide.[1][2][4][12][13][8]

The company explained that the bug had stayed hidden during lab tests conducted on weaker hardware. The failure was triggered when routine traffic rerouting and an unexpected network traffic surge combined with reduced server capacity, unleashing a cascading breakdown across its infrastructure. Microsoft stated that no cyberattack was involved and that engineers took approximately 30 hours to diagnose the issue and begin deploying a fix.[3][7][14][16][17]

The incident disrupted access across 74 countries and lasted more than 12 hours, affecting millions of enterprise, healthcare, and government users. The outage prompted some businesses to fall back on basic alternatives such as faxes, phone calls, and Bluetooth connections, according to the Economic Times. The disruption also rippled into external platforms, breaking Microsoft 365 connectors and triggering authentication errors for AI services including Anthropic's Claude and ChatGPT.[1][7][8][10][11][15]

Key facts

  • Microsoft attributed a global outage affecting Outlook, Teams, and Copilot to a software defect introduced in a July 2026 update for network gateway servers.
  • More than 80% of servers behind Microsoft's network gateway were unresponsive at the outage's peak.
  • The bug remained undetected in lab testing on weaker hardware and triggered cascading server failures when routine rerouting coincided with a traffic surge and reduced capacity.
  • Microsoft took approximately 30 hours to identify the broader issue and begin rolling out a fix, confirming that no cyberattack was involved.
  • The outage impacted Microsoft productivity services across 74 countries for more than 12 hours.
  • The disruption forced affected businesses to turn to faxes, phones, and Bluetooth as workarounds, according to the Economic Times.
  • The Microsoft failure also broke Microsoft 365 connectors in ChatGPT and Anthropic's Claude, causing login and authentication errors for users.

Sources · 14 sources

  1. QU

    Quartz@qzPost on X ·

    A 4-month-old bug took down Microsoft's global network in hours: A patch quietly sitting in Microsoft's servers since July was all it took to knock out Outlook, Teams, and Copilot across 74 countries — and the company's own safeguards made… dlvr.​it/TWMbFQ #Microsoft #Outlook https://t.co/9X2FDMC48s

    Open source
  2. TE

    Techmeme@TechmemePost on X ·

    Preliminary report: Microsoft attributes a major 365 and Exchange outage to a software defect introduced in a July 2026 update for network gateway servers (@richard_speed / The Register) (Visit Techmeme dot com for the link and full context!)

    Open source
  3. BU

    businessline@businesslinePost on X ·

    A software bug that crippled Microsoft's productivity services last week had remained undetected since July. The company says routine traffic rerouting triggered cascading server failures, disrupting Outlook, Teams and Copilot worldwide. https://t.co/6UmE1294Mu

    Open source
  4. TE

    TechmemeArticle ·

    Preliminary report: Microsoft blames a major Microsoft 365 and Exchange outage on a software defect introduced in a July 2026 update for network gateway servers (Richard Speed/The Register) Richard Speed / The Register : Preliminary report: Microsoft blames a major Microsoft 365 and Exchange outage on a software defect introduced in a July 2026 update for network gateway servers — Microsoft has blamed last week's epic outage on a change it made in July that lurked in the network gateway servers until a surge …

    Open source
  5. 9T

    9to5Mac@9to5macPost on X ·

    Microsoft outage saw 80% of servers fail – here's what happened https://t.co/xp6iUev7j2 by @benlovejoy

    Open source
  6. WC

    Wccftech@wccftechPost on X ·

    Microsoft reveals root cause of massive Microsoft 365 outage, as months-old Windows bug crippled over 80% of servers. 🔗 https://t.co/wcJjiDyMFN https://t.co/EyME4n2VSK

    Open source
  7. MN

    Mario Nawfal@MarioNawfalPost on X ·

    🚨 Microsoft users are reporting MORE problems with Outlook, Teams and Microsoft 365 This just DAYS after a massive global outage. And Microsoft has now revealed what caused that earlier meltdown. A software bug dating back to JULY, combined with networking failures and reduced server capacity, triggered a cascading breakdown across its infrastructure. Millions of users were affected, with businesses, hospitals and government agencies struggling to access essential services. Microsoft says the major outage has been resolved and there was NO cyberattack. With fresh complaints emerging, the question is whether these are lingering issues or an entirely new disruption. Source: @InsiderWire, Reuters / Writer: Oliver

    Open source
  8. NE

    NeowinFeed@NeowinFeedPost on X ·

    Microsoft has published its preliminary post-incident report explaining the November 12 global outage that knocked Outlook, Exchange Online and other services for more than 12 hours. #Microsoft365 #Outage #Report https://t.co/3DBTZp7tFF

    Open source
  9. AI

    Analytics Insight@analyticsinmePost on X ·

    𝐌𝐢𝐜𝐫𝐨𝐬𝐨𝐟𝐭 𝐑𝐞𝐯𝐞𝐚𝐥𝐬 𝐇𝐨𝐰 𝐎𝐯𝐞𝐫 𝟖𝟎% 𝐨𝐟 𝐒𝐞𝐫𝐯𝐞𝐫𝐬 𝐅𝐚𝐢𝐥𝐞𝐝 𝐃𝐮𝐫𝐢𝐧𝐠 𝐆𝐥𝐨𝐛𝐚𝐥 𝐎𝐮𝐭𝐚𝐠𝐞 One software glitch took down more than 80% of Microsoft's servers! The company has revealed what triggered the massive global outage that disrupted Outlook, Teams, OneDrive, and other services. A hidden defect, unexpected traffic surge, and reduced server capacity combined to create a cascading failure. How did a months-old bug bring services to a standstill? #Microsoft #MicrosoftOutage #TechNews #Microsoft365 #AnalyticsInsight #AnalyticsInsightMagazine Read More 👇 https://t.co/wncanPs5fU

    Open source
  10. ET

    Economic Times@EconomicTimesPost on X ·

    Claude fixes login outage as Microsoft 365 disruption keeps users on alert | Claude code status today: After a major outage affecting Microsoft services, Claude AI reported significant issues with user authentication and access. Users of Claudeai and Claude Code have experienced disruptions, preventing login and service accessibility. Anthropic has acknowledged ongoing investigation into these authentication problems and has deployed fixes to restore functionality. As Claude's services faced increased user complaints, the company worked to resolve connection issues with Microsoft 365. Full Story Here 👉 https://t.co/NLfwuk87I1 #Claude #Anthropic #AI #Microsoft365 #TechNews

    Open source
  11. AG

    AGTP@AGTPinsightsPost on X ·

    Claude just went down for users worldwide today, November 13. Here's what you need to know. Reports of problems started piling up on X around midday. Users said Claude Code logged them out mid-session, and /login would not run. Others saw "OAuth request failed" when signing in, and the https://t.co/n9TokQatv1 page would not load. Some saw Cloudflare errors, and some said the web app was buggy and the desktop app and Claude Code would not start. Anthropic's status page ties the trouble to a Microsoft outage, now in its second day. The incident is titled as elevated errors affecting the Microsoft 365 connector. It began at 17:52 UTC (12:52 p.m. ET) and was still unresolved. Claude for Outlook remained affected, and Anthropic pointed users to Microsoft's status page for progress. One report said the Claude API, Claude Code and Claude Console were listed as operational. That means the status page shows the problem as limited to Microsoft-dependent features, even though many users could not log in to the app or Claude Code. Another report put the start at 1:33 p.m. PT, affecting https://t.co/xpmg9zlmv4 and the API. The same Microsoft outage also broke the Microsoft 365 connectors in ChatGPT. Key numbers: - Nov 13, 2026: date of the outage - 17:52 UTC: start time logged on Anthropic's status page - 2nd day: how long the Microsoft outage has run - Microsoft 365 connector and Claude for Outlook: services Anthropic listed as affected Anthropic says it will update its status page when service is restored.

    Open source
  12. BU

    businessline@businesslinePost on X ·

    More than 80 per cent of servers behind Microsoft’s networking gateway were unresponsive at the peak of last week’s global outage of Outlook and other Microsoft 365 services, the company has said on Monday, blaming a hidden software defect introduced in July. https://t.co/vqQXY8KgHc

    Open source
  13. BL

    Bloomberg@businessPost on X ·

    The bug that crippled Microsoft productivity software last week had been lurking undetected in the company’s data centers since July https://t.co/3ZaXYAvqC9

    Open source
  14. MI

    Mint@livemintPost on X ·

    Microsoft has explained the technical failures behind the global Microsoft 365 outage on November 12, saying a combination of a software defect, increased network traffic and reduced server capacity triggered a cascading failure across its networking infrastructure. https://t.co/KcPoZRxpnN

    Open source
  15. ET

    Economic Times@EconomicTimesPost on X ·

    Faxes, phones and Bluetooth: Microsoft outage forces businesses to find fixes https://t.co/afxN1GoQj9

    Open source
  16. *B

    *Walter Bloomberg@DeItaonePost on X ·

    $MSFT - MICROSOFT REVEALS MONTHS-OLD BUG BEHIND GLOBAL OUTAGE Microsoft says a software bug undetected since July triggered last week's worldwide disruption affecting Outlook, Teams, Copilot and other services. The failure began on November 11, when routine traffic rerouting overloaded servers and caused cascading system failures. At the outage's peak, more than 80% of Outlook servers were unresponsive. Microsoft took approximately 30 hours to identify the broader problem and begin deploying a fix. The incident raises fresh concerns over cloud infrastructure resilience and enterprise dependence on Microsoft.

    Open source
  17. QU

    Quartz@qzPost on X ·

    Microsoft traced its global outage to a software bug lurking since July: The company said the flaw stayed hidden in lab tests that used weaker hardware, then failed when traffic surged and server capacity fell dlvr.​it/TWMd96 https://t.co/EpBPapIhJ5

    Open source