No big surprises here. Big outages at big firms seem to always look like this.<p>The electricity industry has this notion they call a black start, where they bring the grid online from zero. It's a very difficult operation because you can't start a generator straight into an offline grid otherwise it gets hit with full demand and can't keep frequency in the right range, which can damage equipment. So they have to start by disconnecting all the loads and then bringing load blocks back in sequence, trying to roughly balance available generation with the size of the next block. In practice black starts are extremely rare, but they can happen after a cascading failure in which something causes some generating stations to trip, redirecting load onto the remaining stations which can't handle it causing them to trip in turn. The entire grid can collapse in just 60 seconds or so once that kind of runaway failure starts.<p>This kind of outage is very analogous to a black start. A few servers get into trouble - maybe they're in a crash loop or maybe their caches are cold - the load balancers shift traffic onto the remainder which then can't handle the load either and so the failure cascades. Once a service is in this state sometimes the only remedy is to disconnect all load, bring the servers back to stability, then bring load blocks back online in small chunks, making sure to never hit anything with the full load immediately to ensure any caches or JIT compilers have time to warm up.<p>It's the sort of thing that requires a bit of preparation because naive ways of doing it like just randomly dropping 90% of requests will yield a broken service for everyone. Ideally your LB can drop traffic by modulus of the session cookie or similar, so users are let back in atomically.<p>Black starting a service is obviously quite hard to practice, but is probably something that sufficiently well resourced SRE teams should try once a quarter or so on a test cluster. I used to be an SRE at Google and although we regularly started up new clusters and moved traffic around between them, actually starting an isolated service instance entirely from scratch was never something we practiced. I remember in a few cases teams discovered devs had introduced circular dependencies by accident, i.e. starting service X required service X to already exist, or it depended on service Y that in turn depended on X. Sometimes you can only find these things by practicing.
It's more testing theater on their end; it's just perfunctory rubber stamping. There was and is no real performance testing under simulated near-real world conditions.
Well stated.
In software servers this is called the “thundering herd” problem. It is why clients are coded do not just exponential backoff but random offsets too.
Original source information: <a href="https://x.com/clamanna/status/2122209697226948729" rel="nofollow">https://x.com/clamanna/status/2122209697226948729</a><p>Better summary: <a href="https://www.neowin.net/news/microsoft-finally-explains-why-outlook-went-down-worldwide-and-it-all-started-in-july/" rel="nofollow">https://www.neowin.net/news/microsoft-finally-explains-why-o...</a>
They talk about their relatively low-end testing environment PASSing the July code, and being different from their high-end production environment machines, sadly hiding the concurrency bug during the test phase.<p>Is this commonly acceptable? I'd imagine it's a costly trade-off?
Depends on what low/high end are. If low end is 4 core and deployment is 128 cores, this is not acceptable.<p>But if low is 64 and high is a whole cluster, now that's a different kind of maths.<p>Edit: The article states the following:<p>> "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted."<p>So, it's more the former. The testing machine is probably a 8 year old server on an office shelf, and prod machines are 64-128 core cutting edge Xeons/EPYCs.<p>Lock contention. It was MUTEX spins in Windows 95, it's lock contention in 2026. Why this is still a thing, Microsoft?<p>(Man, I felt old while writing this.)
Testing at production scale is extremely difficult. It’s also financially expensive. In my experience, you balance the two where big changes are tested with some simulation setup to gain confidence. Though, the ci/cd pipeline never has close to full scale automated testing.
...and many times you test to experience, and experience cannot possibly build interferences that simulate the instances you have not experienced nor what has been imagined based on that experience.
some ways of precipitating the demons that are in the ontology of not knowing what you don't know are monte carlo, or perhaps noise injection, but those are time consuming, quite wasteful, and truly hated by people used to working with deterministic machines. that makes finding corner cases very difficult<p>plus, mistakes are the essence of learning and sometimes mistakes are necessary.<p>likewise, we are a very efficient world and efficiency hates redundancy, and hates nonconformity...of which those are two of the features that make exploits widely successful and failures massively impactful
> The engineers who worked feverishly to restore services deserve commendation and will hopefully never have to buy their own beverages in Redmond again (or at least escape the next round of firings).<p>What does this mean? I didn't understand
I think it means that people will hopefully buy them beers as thanks
People should buy them drink, as for the firings side note Microsoft recently had a "voluntary exit" offer mailed to a fourth of their workforce:<p><a href="https://www.geekwire.com/2026/microsoft-makes-new-voluntary-exit-offer-to-more-than-a-quarter-of-its-workforce-including-some-execs/" rel="nofollow">https://www.geekwire.com/2026/microsoft-makes-new-voluntary-...</a><p>How long until Microsoft fires key people to the point that outages become more common? All in the name of AI, which I don't believe for a second, they're just trying to maintain stock market profitability math by firing enough, they'll just hire more people when they make more.
The opportunity/command to exit is not always negative. In many of my career moves, it turned out that the next job was better and came far sooner than the severance calculation had allowed for. Some within weeks. Hardly had time to relax. It seems like for talented individuals opportunity always pops up.
> How long until Microsoft fires key people to the point that outages become more common?<p>Already happening. Granted, not a global outage like this one, but there's not a single day without a service degradation or advisory on the admin portal for 365. The "It's now called Microsoft 360" memes are well earned, and their support is atrocious. I get the feeling that everyone who knows how it works is gone.
An artistic way of saying the engineers should get praised and rewarded.
In sysadmin speak this is hoping that Microsoft gives them free beverage credits (or give them some kind of bonus because of their efforts) and don't fire them as soon as the fix is deployed to scapegoat them.<p>In a rare occurrence, The Register sides with the Microsoft developers. Not that they're anti-developers, but they are anti Microsoft because of its well-earned reputation for EEE and Halloween Documents.
It means they deserve "Thanks" (buying a beer/coffee is a token Thank You) and hopefully they are removed from the pool of candidates for the next layoff.<p>Surprised so many people are struggling with this...<p>Having been on incidents like this before though, yea, that aint happening.
> Having been on incidents like this before though, yea, that aint happening.<p>Been there, through that, and sadly you're right. The bitter part is I didn't want extra compensation or anything. Just a thank you and a day off is more than enough for me, so to recharge and ride the wave of what we (not I, we) have accomplished, so I can work with extra motivation for some time.<p>Instead, got a 5 minute coffee break and dived to the next non-urgent ticket. Yeah, great way to thank and motivate the people who spent 24 hours in an underground office cutoff from the world, trying to save a system from melting down.<p>Glad I'm not there anymore.
> Having been on incidents like this before though, yea, that aint happening.<p>Yeah, instead what will happen is their manager will ask them why they didn't get as many story points done this sprint as they did last sprint and their performance will be marked "degraded".
It kind of feels like they are saying, look, we know we caused the problem, but we fixed it. So we're good, right?
So maybe we shouldn’t be putting all our eggs in one basket?
Hmm, the best I can do is offer you a larger basket
No, no, i think we can and should still load all the eggs into a single basket...we simply have to do so at random frequencies and speeds in order to avoid cracking the eggs, plus when contention inevitably happens, we ask that the egg loaders simply hold off a little...to avoid such traffic, and until egg loading can resume! /s
>> "the processes that led to an update with a latent defect reaching production deserve a long, hard look. "<p>Indeed they do deserve a long hard look.<p>Toss1's conjecture:<p>We are now seeing the beginning of an era of latent technical debt brought about by too rapidly firing developers and switching to AI code generation (nevermind vibe-coding). Even well-prompted and well-monitored by top expert coders and architects, there is latent technical debt, and it is more diffuse, harder to find, and harder to fix, and will start showing up in outages like this.<p>(It first seemed the ATC outage was another example, but it now seems it was merely the usual management incompetence if not an outright manipulative ploy to 'justify' more spending for a single-bid contract [0])<p>[0] <a href="https://ajsignalnotnoise.substack.com/p/faa-air-traffic-control-money-peraton-veritas?r=83255l" rel="nofollow">https://ajsignalnotnoise.substack.com/p/faa-air-traffic-cont...</a>
Suggested reformulation of the conjecture:<p>"Complex systems are kept stable by organisational knowledge of their weaknesses and how to compensate for them. Organisational change erodes this knowledge while the underlying weaknesses remain. A previously stable system thus becomes increasingly vulnerable to failure."<p>When it is said that software is a solved problem, what is ment by that is really that programming, typing up the code, is a solved problem. Software engineering, systems architecture and the complexities in distributed systems are not, while leads to confusion when not being mindful of the difference.
Seems like a pretty standard big company severe outage to me. These things happen!
what role did ai play in all of this?<p>can we blame it for the bug? can we credit it for the fix?<p>might be the most important part of the full report
Poor Microsoft can't afford more than one low-end testing environment.
This is what happens when you burn billions for no reason.<p>Github copilot had INSANE usage. Cursor switched away from per request plans in 2025, Copilot did it this year with all the reasoning and more expensive models. It was insane, you could write out a whole page of features, and have it run on one request for hours depending on the loopholes you exploited (some models were discounted for some time, basically free in some cases, and shenanigans around switching in betwen agents)<p>We talk about opus et. al being heavily subsidized at like 1-2k for $30-$100. I remember seeing figures in the 10s of thousands in subsidizations for GHC. There's no way they weren't losing just massive piles of money.
Doesn't the article state the opposite? The low end was not the problem. It was high end that was the problem.<p>I like ragging on Microsoft as much as the next guy, but honestly this problem sounds complex & hard to predict. AI or not, this feels like the type of bug that would have slipped by me as well.<p>The response clearly could have been stronger though.
The point they were making is that had Microsoft used high-end equipment in testing they may have found this issue before it hit production.
I read "more than one low end" as "more testing environments than one low end" rather than "more low end environments than one". It's a snarky way of saying they should have been testing high end environments for no more reason than they had the money to do it, rather than saying they should have been testing the low end more.
Think of the poor starving shareholders and CEO pay packages.
Pretty interesting that testing was aimed the worry: low spec boxes, and missed a different problem: concurrency contention for high spec boxes. Gotta be covered by someone's rule of testing, I imagine. Also, woof.
These kinds of incidents should inject healthy dose of techno-skepticism in the larger conversation. The world is teetering on the edge of turning over all our processes to LLMs and retiring human labor for good.<p>But at the end of the day these are servers strung together sending packets over copper wires. They are extremely reliant till they are not.<p>When crisis strikes you can only hope there is a squad of well trained humans who can step in to untangle these messes. But as more of the labor force is stripped out of responsibilities, the longer these outages will take to resolve. Imagine being jolted out of your year-long UBI-funded vacation to login and resolve a multi-continent server outage that you only have a vague memory of.
- we added a bug (yes, everyone does).<p>- our testing didn't cover it (again, this is <i>expected</i> occasionally).<p>- this cascaded to take down more than a billion people's service (WTF; this is not how you design systems).<p>- it took 15 hours to deploy the fix (not good, but at this scale maybe).<p>Feels like they are completely missing the point of where the problem is and how to fix it?
>> "an update that returned the code path to the previously known good state in Windows."<p>I know I shouldn't be surprised, but I still struggle to imagine such high-capacity servers running with windows. Part of me wonders why <i>any</i> important server would be running windows. And I do chuckle at the "update" that returned windows to a previous state. Never admit a rollback. Never admit a previous update was less than perfect. Hold the line MS. Hold that line.
But if they wouldn't do it, Windows will be even worse.<p>Moreover, my current switch to Linux shows that Linux is not so much better in stability as it is in public imagination. Once a month or two, I have KDE freeze so hard I barely can recover without reset (sometimes can't). Still can't find the reason. Hardware seems to be okay, it is an expensive gaming laptop.<p>Also, out of RAM can lead to GUI crashing even with swap enabled. True, this is unrelated to servers, which run without GUI, but still weird that it happens.<p>Also, when my laptop runs for weeks without reboot, it has issues with VRAM being occupied and not freed for some reason, which causes game crashes. With all the talk about Linux infinite uptime I expected better.<p>However, I almost can't complain about my homelab server. If there is enough disk space, it can run for months. Unfortunately, lately there are so many patches, I need to reboot almost each day (at least podman-hosting VM, if not proxmox host)<p>For the last half a year I run my homelab, I only had one suspicious shutdown, for which I am not sure I understand the reason well.
Alot of 365 is using Exchange/Sharepoint/Skype for Business code bases which were Windows specific. With Exchange, there was specifically role called "Client Access" which clients connect, the system looks up which backend server has your mailbox and proxies your connection there. Reading between the lines, my guess is this system was reused for Sharepoint/Teams/Office and they could swing off of it to secondaries but Exchange is hard locked on it.<p>Microsoft does greenfield new stuff on Linux mostly.
Yeah it's pretty crazy that Microsoft, a company most well known for it's Windows operating system, would use that same operating system on its servers.
It's is crazy. Given the fact they are running Linux on their cloud. <a href="https://azure.microsoft.com/en-us/products/azure-linux/" rel="nofollow">https://azure.microsoft.com/en-us/products/azure-linux/</a>
Those guys are psycho-fanatics of dogfooding their own services. In the last decade or so, they have hesitantly entertained Apple ecosystems.
They just postponed an improvement temporarily to reevaluate it later, in fact.<p>Here, I converted it to corporate speak for you.
This MS rando on X just leaking his 'abridged' version instead of letting the official account post the report/blog later or whatever? Gotta be 'first' right bro, and now the source of every rabid tech blog for the rest of the day. bah