Published Nov 16, 2026, 3:54 AM EST Simon is a Computer Science BSc graduate who has been writing about technology since 2014, and using Windows machines since 3.1. After working for an indie game studio and acting as the family's go-to technician for all computer issues, he found his passion for writing and decided to use his skill set to write about all things tech. Since beginning his writing career, he has written for many different publications such as WorldStart, Listverse, and MakeTechEasier. However, after finding his home at MakeUseOf in February 2019, he would eventually move on to its sister site, XDA, to bring the latest and greatest in Windows, Linux, and DIY electronics. Summary A July patch hid a bug that overwhelms Microsoft's servers under high load on newer, multi-core hardware. Gateway shifts and reduced capacity created a traffic surge that repeatedly tripped the latent bug. Engineers patched the months-old flaw, rebooted servers in batches, and restored services. If you rely on Microsoft's productivity suite even slightly, there's a good chance you remember when all of its services died seemingly out of nowhere and stayed down for about a day. People were quick to point fingers at potential sources, including artificial intelligence and a cybersecurity attack. Well, as far as Microsoft's statements go, it turns out that it was a bug that had been lurking in the code since July. Microsoft explains why its services died last week A bug was waiting for the right time to strike The EVP of Copilot, Agents, and Platform at Microsoft, Charles Lamanna, took to X to reveal why the company's services went down last week. As it turns out, there was a problem that crept into the code months ago, and the conditions it needed to strike didn't materialise until recently. So, here's what happened. Back in July, a patch Microsoft rolled out contained a bug that "caused servers to become overwhelmed and unresponsive under certain load conditions." It didn't sniff out the problem at first, because Microsoft tests patches on older hardware to see its impact, while the bug only happens when it runs on newer hardware with more cores. Then, the perfect storm happened. 15 hours before the outage, Microsoft Teams traffic failed on the alternative networking gateway and had to move over to the primary gateway, where Exchange Online lives. At the same time, 14% of the networking gateway's capacity had been taken down for maintenance due to an unrelated issue from the previous day and was planned to come back later that day. This severe load triggered the latent bug from July, which brought the server down. Microsoft's systems then redirected traffic to another server. Unfortunately, this also promptly overloaded the server, triggered the latent bug, and it went down. This would redirect traffic to yet another server, triggering the bug, and the process repeated. Lamanna claims that, at its lowest, 80% of the servers were down. Every time a server went back up, users flooding it with traffic would trigger the bug again. Microsoft engineers had to dive into the code, identify the months-old bug, and then create a patch to fix it. Once the patch was ready, they took servers offline, applied the patch, then booted them up again. And thus, all was good again.
Microsoft reveals why its services went down last week, and the problem had been hiding since July
Full Article
Original Source
Read the full article at Xda-developers →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.