AdvertiseDonate
☰ SectionsThe latest from the cities that shape the country.
Wire Authority · 3970 Post Road, Warwick, RI 02886

Hidden gateway bug and traffic shift caused massive Microsoft 365 outage, Microsoft says

A preliminary Microsoft report says a latent defect, shifting traffic and reduced server capacity combined to knock Microsoft 365 and Exchange offline for nearly 24 hours last week.

By News Media House Staff ·

Illustration for: Hidden gateway bug and traffic shift caused massive Microsoft 365 outage, Microsoft says
Illustration generated for this article, not a news photograph.

Microsoft says a hidden defect in its cloud gateway, dormant since July, was at the center of one of the largest outages in the company's history last week, when much of Microsoft 365 and Exchange infrastructure went offline for nearly a full day.

In a preliminary Post-Incident Report, the company said the disruption ran from 16:20 UTC on November 12 to 16:10 UTC on November 13, just under 24 hours in total. Additional monitoring of affected systems remained in place through November 14.

The report lists the incident's final status as "a technical issue not related to cyber or AI/agents," ruling out an attack as the cause of the outage.

The failure, tracked under Microsoft incident IDs EX1550543 and MO1550821, quickly rippled through businesses and public offices that depend on the company's cloud and email exchange services. Viewing the full report on Microsoft's status pages requires Microsoft 365 admin credentials, but Office Watch has reproduced the preliminary document, and the University of Pennsylvania maintains an archive of Microsoft's service-health updates.

According to Microsoft, the outage resulted from three factors coming together. The first was a change deployed to the company's cloud gateway starting in July, which introduced a bug that, under certain conditions, could leave CPU and memory resources exhausted and unresponsive.

The company said the defect was never caught in pre-release testing because the hardware used for that testing was less powerful than some systems already running in production. Higher CPU core counts on the newer production machines apparently contributed to the lockout.

The second factor was server load. Microsoft said that "Traffic shifts during standard network maintenance and upgrades exposed a latent bug." The company operates two independent gateway systems for accessing Microsoft 365, so that if one runs into trouble the other can be opened to keep traffic flowing.

About 15 hours before the outage began, traffic from Teams was moved from the alternate gateway to the primary one, where Exchange Online access is maintained. The switchover was a standard fail-safe, but it left the gateway handling more traffic and a different mix of requests than before. As requests piled up, affected servers exhausted their capacity and began refusing new connections.

The report also cites reduced server capacity as the third element in what amounted to a perfect storm, with the combined effect of the bug, the shifted load and the thinner capacity proving enough to take much of the productivity suite offline.

Originally published by News Media House

More News · National news · Report a business · Got a Story?

Get Wire Authority in your inboxThe latest from the cities that shape the country. Free, a few times a week, unsubscribe any time.

Related stories

Latest stories

  1. MLB Teams Face Deadline for Non-Tender Decisions on 10 Key Players
  2. Ava DuVernay Returns to Political Doc Format With New Film '14th'
  3. Microsoft Email Outage Leads to Chlorine Incident at German Hotel
  4. ESPN experts project 2026 college football playoff and bowl matchups
  5. 2027 Baseball Hall of Fame Ballot Features Buster Posey and Chase Utley as Key Candidates
Get Wire Authority in your inboxThe latest from the cities that shape the country. Free, a few times a week, unsubscribe any time.