(www.theregister.com)
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.
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.
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.
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.
I mean... you can try, but unless you spend a lot of resources on it, I don't expect test load to be close enough to really practice a black start.
From experience, the best way to prepare for restoration from nasty outages is to have them frequently! The team I was on was pretty good at outage restoration, until we started regularly hitting about a year between outages. After a few years of one or maybe two outages per year, we had lost the muscle memory for protecting services that get overloaded during or after an outage and setting outage messages (which both informs customers and protects customer service queues).
Regularly starting up an isolated cluster at least lets you get ahead of sequencing issues though; hopefully it's enough if you can get the whole cluster started and then modulate inbound traffic (most complex services will need something like you mentioned so that you limit the number of sessions, but sessions that start are likely to proceed successfully).
We had to practice load pickup on a normal start at the pier often, but we likely practiced a full SCRAM to back online (including a FULL load shutdown) more.
Having predefined lists of what gets brought up at various points helps a ton, but it's still not an easy or simple operation.
It went remarkably well.
SBB just finished their project to be able to restart the grid in 5min. (There was a famous multi hour outage a few decade ago that I think motivated this work)
But load management while bootstrapping the rest of the grid is still very hard. Often the reason for really long blackout, ones measured in days rather than hours, is repeated cascading failures as operators try to reconnect parts of a the grid, and accidentally overload recovered parts of the grid, causing generators to trip off again.
I've had similar issues where backends couldn't come up due to load killing them as they came up: my solutions was to turn off the load balancers until the backends all came up before opening the door again...
I agree: no excuse.
Before Linux took over the server market in 2000, Windows server was the dominant player in mid-market (enterprise market has IBM mainframes too). But you would have be old enough to remember that decades ago.
You'd see occasional crash screens, but given the sheer number of machines out in the wild, having only a few crash once in a blue moon speaks amply to the reliability of the thing.
Typescript paused new feature development to port to a new implementation language. It's too early to see if it's going to be better or worse for TS devs, will probably need to wait a few years (at least after the easiest things to pick are gone) to see if it was worth it for anyone who isn't building vscode sized projects.
VSCode was great, until LLMs hit the scene. Now there's a new update every 2/3 days either shoving more LLM-ware to the point that the seams are breaking, or it's a security bugfix for something that should never have been added in the first place.
I use it since day 1
In 2014 Microsoft cancelled the dedicated SDET (Software Development Engineer in Test) role, triggering significant layoffs.
Better summary: https://www.neowin.net/news/microsoft-finally-explains-why-o...
Is this commonly acceptable? I'd imagine it's a costly trade-off?
But if low is 64 and high is a whole cluster, now that's a different kind of maths.
Edit: The article states the following:
> "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted."
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.
Lock contention. It was MUTEX spins in Windows 95, it's lock contention in 2026. Why this is still a thing, Microsoft?
(Man, I felt old while writing this.)
We solved that by sharding customers, so about every 1000 database clusters got their own k8s cluster; production then could run hundreds of those “orchestras”, but we could afford to load test one of them and be relatively confident the test was valid for production.
This relied on the various cloud vendors running the front-line load balancers that took traffic and moved it into the shards though. I was about to say that seemed to be the case for Microsoft here as well, but actually it seems they load tested an individual server with different specs than prod.
Tricky problem though - it seems they reasoned if a lower specced server passed the load test, a much beefier prod server would handle the load too. Wrong, but you can see why someone made that assumption.
Microsoft tests its stuff on their own employees (old citation, but still true today: https://devblogs.microsoft.com/oldnewthing/20110802-00/?p=10...), and that includes Exchange online. However, even though Microsoft is a pretty big company, it's still teeny compared to its customer base.
plus, mistakes are the essence of learning and sometimes mistakes are necessary.
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
They find QA dirty in their statement, because they don't state who set that priority, nor why the new hardware was felt to be less likely to be affected (what did their risk matrix look like for their hardware profiles i wonder)
Extent of my knowledge is nginx or traefik load balancing which at this scale is virtually equal to no knowledge. But seems like there would be systems in place to simply drop a sliding percentage of excessive traffic or block some regions once critical thresholds are reached rather than compounding the problem with forwarding the growing number of requests downstream to next victim server.
What does this mean? I didn't understand
https://www.geekwire.com/2026/microsoft-makes-new-voluntary-...
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.
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.
That's not to say their job was or is easy: nursing is far more hazardous than SWE, and significantly more physically and mentally demanding, too. But I do think many got more compensation than your $5 gift certificate implies.
But as a software engineer, if I work overtime on an outage like the above, I'll get precisely $0 of additional pay for it.
Valid only upon a qualifying transaction with a minimum purchase amount of fifty dollars ($50.00). Subject to additional terms, conditions, and restrictions. The display, wear, or possession of any "Hero" sticker shall not be construed, interpreted, or implied as an official or unofficial representation, certification, or endorsement that the wearer possesses the status, title, or attributes of a "hero".
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.
Surprised so many people are struggling with this...
Having been on incidents like this before though, yea, that aint happening.
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.
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.
Glad I'm not there anymore.
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".
And it's also possible that these normal accidents might become more frequent with all the layoffs, AI code, and AI-generated exploits. I guess we'll see.
Indeed they do deserve a long hard look.
Toss1's conjecture:
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.
(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])
[0] https://ajsignalnotnoise.substack.com/p/faa-air-traffic-cont...
"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."
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.
Cynic in me does not see any need to change anything.
can we blame it for the bug? can we credit it for the fix?
might be the most important part of the full report
Does that mean Microsoft's internal code are 100% outsourced to agents / AI and human review just won't be able to catch latent bugs like this?
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)
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.
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.
The response clearly could have been stronger though.
The opposite is true running in production for the last several months. They were runnign on big production machines with enough cores, but never quite had enough load to trigger the lock contention. But once both conditions were true, big machines and high load, due to some unrelated failover elsewhere suddently bringing more load, we then had the magic combination.
It's really not unreasonable to expect an enormous hyperscaler like Microsoft to do load testing on hardware that exactly matches their production systems.
You mean you and me? You realize pensions, institutions, and individual investors are shareholders as well?
Workers benefit much more from higher wages than higher stock prices. Simply because a significantly higher proportion of their income comes from wages.
Whenever someone says "Think about the retirees and other ordinary shareholders" in response to a suggestion to pay workers more than absolutely necessary, they're full of shit.
This "rich people will benefit so it's automatically bad" mentality is counterproductive and borne out of jealousy.
If part of your retirement income comes from rental property, workers being paid more is better for you because they can afford higher rents.
Ordinary workers would better off if they were simply paid more and could put more money into their retirement savings. There's a crossover point where investment gains outpace contributions but it takes most workers a very long time to hit it. Front-loading retirement saving and letting compound interest do its magic over a long time is the way to go. And front-loading is only possible when workers get paid good money early in their careers.
This "whatever's good for rich people is equally good for me" is a mentality born out of being bad at math, and assuming that everyone who disagrees is a raging communist (sorry).
Capitalism is great, moar stock gains are great - I enjoy both. But it's important to look at real numbers.
We all need to side with whoever makes the charts go up and to right to ensure our post-retirement lives are well funded.
Myself and many like me don't care what side that is and we don't care much for policies, groups, or programs that are counter to that.
For at least the first 11 years of a career, contributions outweigh gains. And only if you continuously contribute the same amount every month.[1] But in fact most people's contributions increase because their salary increases, so the actual crossover point is much later, such as year 20.
Being paid more, especially early career, is just more useful to the 99% white collar workers on HN. It lets you save more money for retirement. Compounding more money for longer gives you a better retirement. This is simple math. It isn't a class conflict argument.
[1] https://finance.yahoo.com/news/crossover-point-compounding-m...
All me and the other guy are saying is that it's possible to not be filthy rich and still want stocks to do well. "Think of the poor starving shareholders" implies that we commoners shouldn't care or want that. But that's false. I'm no longer working, and have no rental income, so I need my investments to do well.
That necessarily means lower profits to shareholders. The two goals are in tension with each other.
> I'm no longer working, and have no rental income, so I need my investments to do well.
Then you're still rich. Not a 1%-er but at least a 10%-er and very possibly a 5%-er. I want my investments to do well too. I don't pretend it's in the common good.
The mantra of "shareholder primacy" sounds great in theory but just becomes an excuse for short term profit boosts for a small class of shareholders usually at the expensive of the long term health and growth of the company and long term value seeking shareholders.
Sort of similar to how most countries with "people's" or "democratic" in the government's name tend to be democratic only for the ruling party.
In this case ensuring adequate engineering resources for possibly the most widely used email system in the world doesn't seem crazy. How many long term customers will they loose because of this incident? Perhaps they did have enough resources, but given the recent layoffs to chase AI I sort of doubt it.
Not for me and probably a lot of people and institutions too. We have retirement accounts, endowments, and pensions tied to index funds and the index funds have these stocks in them.
We need these companies to do well to ensure we retire and grow well.
Looks at my Windows Task Manager...
Also this is karma because Microsoft blocked in ignorance entire datacenter networks making SMBs unable to deliver messages to their networks.
Ta-ta!
- our testing didn't cover it (again, this is expected occasionally).
- this cascaded to take down more than a billion people's service (WTF; this is not how you design systems).
- it took 15 hours to deploy the fix (not good, but at this scale maybe).
Feels like they are completely missing the point of where the problem is and how to fix it?
I've definitely been in similar scale war rooms and 15 hours is not acceptable.
So, even when you fix the issue, it takes a bit to clear up, and the load gauge stays at the red zone for a while.
This lets you start at a very small amount of load and gradually ramp up. But you can’t reject randomly or goodput stays at zero and the backlog never decreases.
I believe SDN systems can do that with ease, but what would be the equivalent method on older systems? Selectively allowing IPs to go through the trickle load into the system?
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.
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.
That’s Silicon Valley fantasy, it’s not even close to reality
So to recap:
1. They did not have proper cell-based architecture to partition their system into failure domains ("In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure.").
2. They did not have proper monitoring to see the encroaching collapse.
3. Stuff just keeps falling off: "Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day"
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 any 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.
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.
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.
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.
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)
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.
Microsoft does greenfield new stuff on Linux mostly.
Here, I converted it to corporate speak for you.
Windows 10?
7?
XP?
95?