---
title: "Hidden defect, traffic shift and reduced capacity caused near-24-hour Microsoft 365 outage"
slug: "hidden-defect-traffic-shift-and-reduced-capacity-caused-near-24-hour-m"
date: "2026-11-17"
category: "Business & Society"
author: "Simon Banks"
correspondent: "Simon Banks"
correspondentRole: "Labor & Societal Impact Investigator"
readingTimeMinutes: 1
tags: ["News"]
originalSourceUrl: "https://arstechnica.com/gadgets/2026/11/microsoft-details-how-three-problems-combined-for-a-global-outage/"
canonicalUrl: "https://aurav.ae/hidden-defect-traffic-shift-and-reduced-capacity-caused-near-24-hour-m"
publisher: "Aura-V Intelligence (aurav.ae)"
---

# Hidden defect, traffic shift and reduced capacity caused near-24-hour Microsoft 365 outage

> A dormant cloud-gateway defect, a Teams traffic shift and reduced server capacity combined to knock Microsoft 365 and Exchange offline for almost a day.

## Key Takeaways (TL;DR)

- A hidden defect in Microsoft’s cloud gateway, present since July, could exhaust CPU and memory under certain conditions.
- About 15 hours before the outage, Teams traffic was moved to the primary gateway, increasing load on already strained servers.
- The incident lasted from 16:20 UTC on 12 Nov to 16:10 UTC on 13 Nov, affecting businesses and public offices worldwide.

The report attributes the outage to three factors. A change deployed to Microsoft’s cloud gateway starting in July created a defect that, under certain conditions, could exhaust CPU and memory resources, rendering the gateway unresponsive. Microsoft says the defect was not discovered in pre-release testing because the hardware used was less powerful than newer production machines, whose higher core counts contributed to the lockout.

The second factor was a traffic shift. About 15 hours before the outage, Teams traffic was moved from an alternate gateway to the primary gateway that also handles Exchange Online. The switchover, a standard fail-safe, altered the mix of requests and increased load on the primary system.

The third factor was reduced server capacity. The primary gateway, already handling more traffic, could not accommodate the surge, leading to exhausted capacity and refused connection requests.

Microsoft’s preliminary report lists the incident’s final status as “a technical issue not related to cyber or AI/agents.” Monitoring continued through 14 Nov.

Our read: The incident shows how a long-standing code defect can become catastrophic when routine traffic management and capacity-planning oversights intersect, highlighting the need for testing on production-grade hardware and robust load-balancing safeguards.

---

*Original Think-Tank Source: [Three small failures combined to take down Microsoft 365](https://arstechnica.com/gadgets/2026/11/microsoft-details-how-three-problems-combined-for-a-global-outage/)*
