Microsoft blames monster email outage on software defect introduced in July fix
theregister.com
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'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.
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)
If the outage involves damage to transformers then all bets are off. In those cases some areas of the country might become uninhabitable for months.
It went remarkably well.
The initial start up (of the cold start plants) took the double of time expected. The "cold start" capacity is being increased due to some of the issues found.
Portugal was able to recover in 12h (still a lot) without any external assistance.
> By 07:00 CEST (05:00 UTC) on 29 April, electricity had been restored to 99% of energy demand, and full restoration was achieved by 11:00 CEST (09:00 UTC) that same day.
The wikipedia references seem valid for this precise timeline, which is more informative than your remark.
https://en.wikipedia.org/wiki/2025_Iberian_Peninsula_blackou...
I'm not trying to win a pissing match, just trying to counter the very common miserabilist notion that Portugal did worse than Spain.
This specific problem was (1) caused in Spain, (2) fixed faster in Portugal, and (3) with little external help.
Portugal could've been the cause, and could've done better, for sure.
But it's just not balanced to write "In Portugal it didn't go that well" as a response to "It went remarkably well [in Spain]." Makes it sound much worse than it actually was.
Do you have any engineering insight on why a hydropower plant was used, and not, say, a gas-fired power plant?
Once the hydro station is back online the power it generates can be used to provide house load to the other stations.
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.
Typically <5% afaik
They should have that and they typically pay substantially more for it. Unfortunately it's also the case that the private companies providing said black-start capability may have just not bothered to tell anyone they haven't been able to do it for a few months\years.
A properly run network will require those facilities to be tested multiple times a year to ensure it actually works, and make payment for the facility contingent on passing those tests.
So you need a hydro plant that is either small enough that it’s using turbines with at least some permanent magnets (you get turbine varieties that basically have a mini turbine inside using permanent magnets to the energise the larger primary electromagnets), or has dedicated infra to produce power to energise the coils in their turbines before they’re producing enough power to energise themselves.
The process is called islanding.
This is very much like trying to jump onto a train from another train moving alongside it.
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.
You need a temporary source of power to start the water pumps and it takes a while for the water to flow all the way through the system and for the coal to saturate all the belts and power plants, if you hook it up to the main grid before all the plants are operational then it shuts down again.
Factorio makes this fairly easy for the most part, a cold start isn't really some massive engineering challenge, but still, worth guarding against. By the time you get solar and / or nuclear power is basically solved, at least on Nauvis, but it's "overengineering the game," so... we overengineer.
In Factorio, solar is an easy source of cold start. In the real world, I think hydropower is a commonly designated choice and the solar farms have to wait for a grid to sync against.
Cold starts are a constant in Aquilo until you research and build fusion power. And whatever you do by hand to handle them, there's a device in the game that does it automatically too.
Once we’ve restored power to the substations, we can carry out what are known as voltage restoration operations.
At a nuclear power station, if all goes well, there will be at least one nuclear reactor unit that has managed to operate in island mode. They have their own sub station and can restart the others units.
We restart as many units as possible on a virtually empty section of the grid (serving only essential and vital consumers such as hospitals). We then reconnect consumers in a predefined order to avoid significant fluctuations that could trigger further cascading failures.
The most difficult part is often identifying the exact cause of the blackout with certainty, so as to prevent it from repeating it.
“Ready? 10 seconds to power on server alpha-romero-one-o-four!”
“Load—at five percent, check! All systems stable!”
It's chaotic and stressful in a slow asynchronous way.
"Rabbit, flu shot, someone talk to me!"
(I have no experience with H1Bs nor beef, I'm a German who's merely had the joy of seeing failed offshore projects.)
All of it is documented through a unified catalog of services and their associated metadata.
Source: Worked in MSR and shipped services through Azure / CoreAI.
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).
Incidentally, the best way to make sure load shedding works is to have to use it frequently! In my last job, the seemingly unchangeable client settings that resulted in load spikes every hour on the hour were super annoying, but also provided hourly confirmation that basic automatic load shedding worked.
This is one of those beautiful engineer understatements. Rotational speed is fundamentally linked to voltage by the motor velocity constant: https://en.wikipedia.org/wiki/Motor_constants
Although it's fundamental for all motors, the actual constant is arbitrary for each motor. Voltage is still proportional to change in field is proportional to speed; at zero voltage you have zero speed.
A large dead AC load has its own speed- zero. It's connecting the engine without a clutch, but the engine makes hundreds of megawatts. The 6' wide generator wants to go from 3600 RPM to a standstill in a few inches. A full speed rotor can have up to 5 gigajoules of rotational inertia; over a ton of TNT.
On a live grid you've got a synchronoscope: https://youtu.be/LVozbX9Mn1c?si=RhRPIkuTVxh4Wseq&t=181
Which is great, because connecting it backwards would cause a slow motion explosion. On a dead grid the only thing saving you is the resistance in the wires; it would be LOUD if you connected to it and you would very likely increase the ventilation through the walls of the plant.
That we often bypass local field control and tie large industrial synchronous and asynchronous (induction) motors directly to grid is narrow and quirky special case that is common for historic raisins but really quite awful, with staged delta-star or dahlander winding relay tricks to go from insane start currents down to just absurd.
Brushed motors are just synchronous motors with a primitive mechanical field control attached, allowing them to reduce the field rate in response to load.
How long do you need to dry a grape for it to not only become a raisin but a historic one?
In a synchronised power grid, machine speed is connected to electrical frequency, that's it.
Voltage and reactive power are controlled by the strength of the rotating field, not speed.
(It might be better not to use CIDR ranges, but use the lower bits instead if possible. For example starting to unblock all IPs that end with .80 until .90, to get more random geographical distribution)
Which leads to my suspicion it was internal load that brought the system down. Communication between the servers (like delivering queued up messages from one O365 account to another), and not external access from users and apps.
If the load balancer already does some connection tracking, it can just keep serving existing connections and only drop new ones. If connection tracking is not available, the IP blocklist would be a suitable option.
IP blocking is generally not what you want though.
Okay, they get different IPs during the day, fine. But it's still kind of randomized. Stepping through IP ranges will reduce load and give access to more people.
I really don't get the issue you are seeing with this.
IIRC Microsoft posted a comment around 10pm where they discussed rate-limiting external connections, and many reactions on last week's HN thread were like "wait, you so didn't even drop load before now?" So internal load may have been a contributing factor, but it's by no means certain given that they didn't stop serving clients.
This is absolutely terrifying knowledge to know given the competency of the current administration and their attitude/response to recent "black swan" outages.
Readers who know about distributed systems and their failure modes already understand the thing being explained. They (and you) are not the target audience. Let people who are not already experts learn something by analogy.
But the analogy is useful in another way. The electricity industry plans and rehearses for this kind of thing, even though it's impossible to simulate. I used to be rather skeptical that these rehearsals would be effective but Portugal black started last year after a solar plant in Spain malfunctioned and took down the whole Iberian grid. It took almost exactly 24 hours despite the grid collapsing several times during the process, which is the usual estimate for how long things will take. So it seems they have this stuff well under control.
I won't slam Microsoft too hard for this outage because this type of scenario has played out at many companies over the years. Yet I never encountered an ops team that has written procedures for how to recover when the entire service has entered a crash loop under peak load.
The exact analogy we use for this doesn't matter much as they are all pretty evocative, but using black start has the advantage of reminding us that there's another branch of engineering where this necessity is taken seriously and rehearsed. They also engineer for it ahead of time so they can prioritize customers like hospitals and airports under overload conditions. I think it would be a good feature for cloud LBs to be routinely differentiating between e.g. customers on paid plans vs free so they can serve paid customers first if there aren't enough live backends.
this is an interesting observation, since this should be table stakes for running a high scale distributed system. there are plenty of companies that do this and write about this extensively. it definitely becomes less important until you get to certain levels of scale though - a random app with 10k users has a different standard than, e.g., google cloud storage.
At the time Iberia was relying >50% on renewables which is very dangerous. The operators tried to recall gas power plants to provide inertial stability, but the plants were cold as they'd been taken offline in the morning to make way for solar (prioritized due to green politics), and even though gas plants can spin up very fast compared to other kinds they could not warm up fast enough to rescue the situation as it was all over thirty seconds later.
So it depends how you define "fault" but yes the starting point was a broken solar plant. Thermal/hydro plants stay locked together through physics because there's a prime mover connected to a generator, but solar plants rely on computer-managed simulations of the rotation that tries to follow the rest of the grid. When you have more simulation than reality it can get tricky fast.
Less neutrally, there have been far too many years of people pretending that you can build a grid out of 100% renewables. It was a false claim from the beginning, but engineering was overridden by ideology. The Iberian outage was one of the consequences - unfortunately merely a preview of coming attractions, as our political class is in denial and would rather believe lies than address the truth that it's caused by their own laws. Now it's only a matter of time until the entire UK or European synchronized grids experience a collapse of their own, with a similar root cause. We can't say we weren't warned.
For instance, a generator failure that cannot be mitigated by dropping load will probably result in islanding the grid: circuit breakers trip some lines and your network becomes several sub-networks. The sub-network that failed can then be re-powered without a black start.
That a large computer system trips like that without circuit breakers is an issue, because the larger your system grows, the more likely it is for one piece to fail.
An important part is that clients pre-fail most requests and don't send them if the server is overloaded. They just assume the server would return an overload error and fake it on the client. For Google, this is an effective circuit breaker.
Which reminds me, someone, maybe Netflix or Google, already discussed circuit breakers much earlier than that. You have to cut off the misbehaving part of the system so the failure doesn't propagate.
It's also something in Golang philosophy. Every channel (queue) has a maximum capacity and you can wait to send on a channel, just like you wait to receive from one. A trivial use case I've written is to coalesce status updates - if the status changes again while the network writer thread still hasn't accepted the old one yet, then a buffer thread just silently drops the older update and keeps trying to send the newer one, and this is trivial in Go.
Practical Engineering has a great video on the topic: https://youtu.be/uOSnQM1Zu4w?is=asXdq74a1f-d6lqc
Without a functioning intuition, discovering the causes to initiate recovery effort in a high-stress, unfamiliar situation with catastrophic dimensions could be significantly hampered.
They are valid questions and of particular interest in the age of AI. Productive, highly specialized skills could degrade faster than one imagine once we start rely too much on external helps.
Self hosting is not a viable option for a serious multi million dollar business. They will lose a few email hobbyists or early startups like myself at worst.
And the savings in labor is astronomical.
I will still get sent to junk 70% of the time, especially to Microsoft Exchange
I'm an IT admin at my company (though I don't often actually admin the MS parts), so I regularly receive e-mails from Office365Alerts@microsoft.com that almost always end up in the junk folder. The mail is legitimate. But it's typically about such-and-such doing something that's against some policy, so we get notifications. Since I'm not in charge of either side of the policy violation, I could never be bothered to look into why these messages end up in the junk folder.
They’ll also be self-aware if this, and know the conclusions that people will draw.
Why would AI be at fault ? We are talking about Microsoft here.
Throwaway account, I work at Microsoft, everything was AI's fault.
I think the deafening silence of "nobody asking" the question speaks for itself.
Seeing AI "fix" the code makes everyone just turn off the brains and move on.
Those here who program know - no one reads code or PRS.
Seeing AI "fix" the code makes everyone just turn off the brains and move on.
Those here who program know - no one reads code or PRs.
For example just accept connections from specific (random) IP ranges. They could even cycle through different ranges every 5 minutes to give clients a chance to sync at least once every hour.
The reduced load could be used to gradually bring up servers again without failing, add additional capacity, and gradually restoring access. Completely without fixing the bug at all. The system managed to handle usual load even with the bug, it just hit some critical point that made it collapse. Adding more resources would also fix that.
Restricting external access wouldn't solve this issue.
I guess adding a config option for throttling queue processing is something any distributed system should have.
Most big cloud services operate several layers of load balancing. The first is a smart DNS server that turns a lookup of mail.outlook.com or whatever into an IP address of a datacenter roughly nearby to where the user is, to a datacenter that's not too overloaded. But because DNS lookups are cached and sometimes cached too long by clients this is a very rough and ready form of LB.
The second layer are routers that spread requests to a single IP address over "hardware" LBs that take raw TCP/IP connections from the internet. Then those machines do some basic health checking and forwarding to the frontend web servers. At that level the machines aren't aware of what service or customer the connections are for, they're just doing some flow hashing to pick a "backend" (another frontend).
Then the cloud/service level machines terminate the TCP/IP connection and often TLS as well. They're reverse proxies that do URL matching and forward traffic on to the app specific servers. This is the first layer at which you can start to intelligently inspect or drop traffic.
No one person in a big org has the ability to limit traffic to a service across every layer of load balancing that exists. If the reverse proxies start dying, reducing traffic would mean changing the configuration of the hardware LBs which is usually a different team.
I'm guessing there must be some deeper issue at play making it too risky or not possible. Maybe the hardware LB's were too intertwined with customer Azure loads or something?
But when you are hitting hour 12 of a global outage of one of your most central services I would assume even quite exotic solutions would be considered (e.g standing up dedicated hardware LB's with load shedding and pointing some of the DNS resolution to those)
This looks like a potential weak point against a cyber attack. A big number of distributed bots in one geographical area can send their requests to one data center and overload it.
In 2014 Microsoft cancelled the dedicated SDET (Software Development Engineer in Test) role, triggering significant layoffs.
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.
I use it since day 1
How would you say it has degraded?
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.
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.
"The FDIC OIG is alerting banks about an increase in a type of fraud known as “ATM Jackpotting.” ATM Jackpotting involves criminal actors accessing ATMs and placing malware software on the system, enabling them to illegally dispense cash from the bank’s cash supply. The process is often run by sophisticated and organized crime rings at both the physical location (accessing machine and hard drive) and operating in foreign jurisdictions (transmitting malware codes).
The FBI estimates 700 instances of ATM Jackpotting and losses totaling more than $20 million in 2025."
An ATM is actually simpler than a fruit machine. The latter has more reasons to refuse a payout!
Unfortunately, as I understand it, it basically needed to pretend to be Win 9x on release due to Microsoft's (understandable and smart) focus on backwards compatibility, so there's effectively a layer on top of NT that hides its most powerful capabilities and makes it pretend to act like its drooling older brother. Then probably three more layers on top of that, depending on which strata of Microsoft history your program is talking to.
Finally there's all the dreadful UX that Windows layers on top, so one could be forgiven for missing the gem hidden beneath the mound of manure.
https://blogsystem5.substack.com/p/windows-nt-vs-unix-design
From what I've read, Windows NT does have a good design underneath while Unix is simpler, but I don't think any windows version has offered the capabilities in a straightforward manner and easy to administrate. Too much awful layers as the parent comment says. While Unix has been mostly the kernel => the service manager => your service surrounded by a few concepts like users, unix sockets, file permissions,...
These technologies are battle-tested, and were adopted or replicated in Linux-land . Fore example, systemd does event logging and service management. Likewise, Linux file permissions haven't really stood the test of time, enterprise-grade systems use ACLs, which again, are a retrofit into Unix/Linux, but native to windows. For Linux, you have a choice of these implementations, but most are built on top of the OS, and each have their fanbases.
The 'traditional way' of sysadmin-style semi-custom Linux boxes, each with their own permissions setups and init scripts have thankfully gone out of vogue.
The creators of UNIX inherited the hierarchical file system of Multics, but they have abandoned ACLs, considering that they are too complicated for small mini-computers with a few users, and they have replaced the ACLs with the well known UNIX file permissions.
So ACLs are not some Windows or Microsoft innovation. Both the POSIX ACLs and the Windows NT ACLs have resurrected the Multics ACLs.
Regarding system logs and service scheduling, Windows has made only negligible improvements over UNIX.
Neither are really recognizable from their "roots" these days. The only certainty is that updating Windows still takes bloody ages.
Today I took an Ubuntu VM from 24.04 to 26.04 - it took about 10 minutes (that includes downloading the updates). It was a fairly simple system and I didn't have to repair anything. The service was actually up for most of the update.
I've run Exchange updates that have lasted most of an evening and night and that was on a single box Exchange on prem deployment.
On Gentoo Linux an emerge -Uva --deep --newuse @world can take a little longer than a Windows update sess but you are compiling the OS from source 8)
DEC even sued Microsoft and Microsoft settled (sound familiar? DOS? Can't Microsoft invent anything of their own?).
Hey, they got it quite reliable eventually (Windows 2000 timeframe), but still.. To say Linux is 1970s tech and WinNT ISN'T seems a real stretch.
And if other more modern kernels offer significant improvements over them, I wonder why we are not seeing them. Should be easy enough to add a Linux or Windows syscall layer to a modern kernel like that.
In the beginning, the NT kernel API was a mixture a functions taken from VMS (mostly for asynchronous I/O and thread/process management) with functions taken from UNIX (mostly for classic I/O), where most functions had various corrections or enhancements in their lists of parameters in comparison with their models from VMS and UNIX.
The later Windows NT versions added some innovations, e.g. I/O completion ports in Windows NT 3.5, waitable timers in Windows 4.0, and so on, but there were not many such innovations and most were not very important.
Around 2000, one could claim that Windows NT is a much more modern OS than Linux, mostly because of the asynchronous I/O inherited from DEC RSX-11M and DEC VMS (Dave Cutler had been a major contributor to both).
However, after 2000 Linux started to add a lot of innovations over what is specified by POSIX. Today, any high-performance application running on Linux that uses the POSIX API instead of using only Linux-specific syscalls, makes a big mistake.
Nowadays, for many applications the Linux kernel has a better API than Windows, but the Microsoft developers are not stupid, so in recent years they began to incorporate into the Windows kernel some of the more important Linux kernel innovations, like futexes and io_uring.
Somehow it manages to be slower in uncontended cases so maybe in hindsight it wasn't that good. But on Linux you get permanently stuck threads if your NFS server is down. There's no "request" object which you can cancel, there's only a thread stuck in uninterruptible wait.
Consider: exclusive file locking for almost everything. UNIX lets you delete or move an open file, the Windows kernel doesn't and this creates enormous complexity at higher levels of the userspace stack especially for any kind of auto updater. It's also one reason Windows updates are so painful.
Windows has pathetically low performance in the filesystem layer, largely thanks to its filter driver design. It's not uncommon to find apps written originally for Linux are basically un-portable to Windows because they assume fast file IO and Windows just can't provide it. This was also a major motivator of the WSL2 effort. Windows actually has a feature called Dev Drive. It's a whole alternative filesystem that's faster than NTFS. They call it Dev Drive because they assume only devs need good filesystem performance (gah). You can't run Windows itself on a Dev Drive though, because of tech debt-y "reasons".
This ridiculous approach of assuming developers are special is carried over to other things too. The Windows kernel supports symlinks but this support is nearly useless because it's disabled out of the box for security reasons (symlinks play a role in some kinds of attack on UNIX). So you have to turn on Developer Mode in the control panel to be able to use them. Hard links do work but only for directories, iirc.
Sometimes you'll see the Windows approach to security be praised (SIDs, object manager etc). It does have a more principled design than Linux, that's true, but the standard here is macOS/XNU not Linux and the Windows kernel's sandboxing support is far worse than macOS.
Windows processes are extraordinarily heavy compared to a Linux process. They take more RAM, start up much slower, and context switching is slower. Again, this difference often renders Linux software un-portable because they assume they can fork and exit processes very fast, but on Windows you just can't. You pretty much have to replace a multi-process design with threads.
Despite the Windows kernel not being a competitive advantage to Microsoft (IMHO), and despite that they run public symbol servers, they keep it closed source. If you really want to understand the Windows kernel you can do so down to the level of individual function calls with public information, but you can't actually read them. The reason is probably security-through-obscurity for DRM, Warbird and other such things, not that it seems to help much. This makes it frustrating to figure out what's going on.
Relatedly, the Windows kernel is an absolute war zone. It's nothing like Linux, which is a conventional textbook OS design. On Windows the kernel is riddled with deliberate traps, code obfuscation engines and "tilt sensors" designed to try and block attempts to hook internal functions by malware or other kinds of malicious software. This shows up in other places too: for example, the API to Linux is the system call instruction. On Windows the kernel theoretically doesn't have a stable syscall interface and you're supposed to go via public APIs like kernel32.dll, which in turn just forwards to ntdll. In practice it does have stable syscalls because MS never randomized the system call interface, so apps trying to detect hooking in userspace do invoke system calls directly (often for anti-cheat purposes). The result is there are like three different ways to invoke NT system calls, all of which are extremely overlapping and duplicative (kernel32, ntdll, system calls), all of which are used by apps in reality but only one of which is documented.
- File locking is a convention on Windows, not a necessity and you don't pay for it if you don't lock files (which is an unfortunate default btw).
- By filter drivers being slow, I think you mean antivirus and security stuff, which are an unfortunate reality of daily windows use, but aren't really caused by filter drivers being a thing. If you needed antivirus on Linux, I think you might incur a similar penalty
- I think symlinks would be nice, but I haven't ever really missed them on Windows. The things linux uses it for, like linking libraries are done differently on Windows
- Devs are special in some sense. You can't afford to break existing workflows on users machines. Just recently, the EU decided to replace Windows with Linux, discovered that stuff doesn't work, then promptly went back
- I appreciate that you call out Windows security as a positive, but as with many other subsystems, Windows has shipped with many systems that were production grade and built in, like security, ACLs, event logs, etc. etc. which are not part of Linux by default, and are the subject of endless debates as to how to implement them (some of them, like systemd, mirror Windows functionality)
- A concept of a Windows process doesn't really map to a Linux process. Linux processes are isolated threads, while Windows ones are containers (and don't even necessarily have a main thread). And afaik Windows processes aren't that heavy any more. Their heaviness came from loading gdi32 and user32 dll, as they expected to host GUI apps, on new Win versions, that's no longer necessary. But fork() style process management is foreign to Windows, and the one place where its useful in Linux, cli apps, Powershell has an entirely different design, where its more like a JITed scripting language, and ls or cp are not separate processes.
- I don't think heavily multiprocess designs are in vogue anyways (at least not how Linux does them), but in terms of RPC, COM multi-process RPC was much more efficient in Windows compared to things like eventfd. Android even added binder, which is a similar mechanism
Many of Windows' mechanisms are a bit long in the tooth, but arguing that Linux is better, then adopting a very similar mechanism in Linux years to decades later doesn't really show that engineering superiority.
I'm not a Linux hater btw, except in one thing - the fact that there's no good standard way to build and distribute binaries that can be expected to work on any reasonable Linux install is criminal.
IIRC it's more that the filter architecture itself is slow, but yeah Windows comes with some slow filters out of the box that don't help. There's a writeup somewhere about this from a Windows kernel engineer but it was years since I read it. AV is indeed the worst offender but Windows always has one, so <shrug>.
systemd is inspired by macOS Launch Services. I guess svchost is the closest equivalent in Windows, but it didn't play any role in the systemd design process.
Linux processes do contain threads, I didn't quite understand what you meant by saying they're not containers. There is now the concept of a Windows picoprocess but it can't do much and isn't used after WSL1 was removed, if I understand correctly. I agree that Windows doesn't really need cheap processes architecturally and native apps don't rely on them without that imposing much cost.
[D]COM isn't a kernel feature but the closest equivalent on Linux would be DBUS, not eventfd. I don't know how they compare in terms of efficiency, I'd expect about the same, although in a past life I actually worked on an open source implementation of DCOM!
I didn't argue Linux is better, I have plenty of beefs with how Linux works too :) The Windows kernel is rightly very popular because it offers a stable driver API, which in turn enabled a huge gaming and hardware ecosystem, for instance. But architecturally I don't see big differences between them tbh.
Now Midori, on the other hand... that really was different!
I see that in general Windows takes a "big monolith" approach to things that Linux can handle as a large array of small pieces. An app can be a few files on Windows, a help database is one file, a source code repository would be one file if all the VCSes weren't imports from Linux.
This might be Conway's law in action. On Windows you were more likely a proprietary shop writing software that just does what it should do - if you needed to change it then you changed the software. On Linux because it's a bazaar you have a lot more of trying to tinker with the things that are already there, or add on small pieces. The average unit of deployment on Microsoft platforms is (or was) Turbo Pascal or Visual C++ 6 or QuickBooks or Microsoft Office; the unit of deployment on open-source platforms is grep or sed.
But that's MY perception of that period of time. I intentionally avoided working for Windows-based places because it sucked so bad.
I agree. We're talking web servers here, not SMB file and print servers, which were mostly WindowsNT based and the contrasting vendor would be Novell until sometime in the late 90s.
The vendor of popular web server software over time is well documented thanks to 30 years of Netcraft. Unfortunately, we don't see the platform, but most uses of Apache were either Linux or Sun based, and Microsoft shops tended to use IIS and rarely anything open source. My own experience at the time was that things that ran on Sun was mostly java based, WebLogic.
https://www.netcraft.com/blog/march-2026-web-server-survey
According to the graphs:
Microsoft's share of the top 1 million busiest sites was never above 20% and has been steadily declining for the last 15 years. If you were serving a lot of traffic, you weren't (and aren't) using Windows to do it. And the majority of traffic has always been served by something other than Microsoft.
Microsoft reached over 50% in 2017 in marketshare of all sites, but traditionally has been limited to below 40% and has really dropped off since 2020. And (based on the graphs), that traffic probably migrated to nginx.
There was a period in here where Netcraft had to make a distinction between sites and servers. Cheapo web hosting services via virtual hosting was on the rise, and a massive number of domains/sites were all served from the same server, and it skewed the numbers in terms of vendor market penetration (think shared-hosting offerings like GoDaddy, the hosting industry was lousy with them). The back and forth churn was notable when some big hosting company switched their web server software and then hundreds of thousands of sites changed software vendors. I remember Microsoft making a big deal about this with marketing copy like "The most popular web server software on the Internet", which may have been true based on domains/sites, but not based on installed instances or most-served-traffic.
IME Microsoft was never a big vendor of web server software, unlike how they are a big vendor of desktop. People were aware of IIS as an option if you were a Microsoft shop, and I know some people who ran it (I once crashed my buddy's site using the perl WinNuke one-liner to put him in his place after bragging about his NT and IIS setup -- hi Noel!) but Sun dominated and where it didn't, it was open source solutions.
> I intentionally avoided working for Windows-based places because it sucked so bad.
Same.
The problem is making all the moving parts from all those people work together well. Weakest link is almost never the people but the complexity of everything.
I'm surprised companies used Linux for critical network infrastructure before eBPF finally stabilized. Before eBPF Linux did not offer efficient async I/O primitives.
Better summary: https://www.neowin.net/news/microsoft-finally-explains-why-o...
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.
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.
I doubt this very much.
The load testing env is the Office 365 load testing environment. I'd be surprised if it is less than 10,000 cores, and the machines are probably good but older; possibly 50 core Xeons instead of 128 core EPYC or something.
It seems likely that the test env was setup to mirror one of the smaller 365 regions a few years ago and the only updates were when machines were replaced.
I've seen NUMA cache line contention affecting us for real (on Windows, for our game tools). Limiting certain tools to run locked under one NUMA node helped a lot. It's real.
The updated CoreInfo https://learn.microsoft.com/en-us/sysinternals/downloads/cor... shows this well
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
We need to teach queuing theory in school. Intuition about how much redundancy you can squeeze out if a system and still handle hiccups is woefully inaccurate. So we under provision and are surprised when traffic jams take hours and hours to clear. Despite that being completely predictable.
If you get 990 with a capacity of 1000, it takes 99 minutes to clear that same disruption. And if you get 1000 with a capacity of 1000, average time to recover from a little random fluctuation is infinity.
I believe normal practice is to upgrade fiber-optic lines when they're somewhere between 50% and 80% utilisation.
Also “9 minutes to clear” only tells how long the congestion is, NOT what the customer experiences. On a typical response time of .6s, after the delay the first customer sees 101x the usual response time tapering off to 2x almost 9 minutes later. That is a very different story than, “things will be slow for 9 minutes”. It’s everything will be an absolute shitshow for 9 minutes.
Professor made a simple statement, pointed to the local (I405) freeway in Irvine and stated that traffic is incompressible flow similar to water. Flow problems are only solved by a bigger pipe and whenever you see its manifestations (flow memory, slowing at chokepoints, etc.) remember that fact. Also remember: there will always be a single slowest point in a network unless you can somehow manage to cause the flow to accelerate past and away from obstructions.
The first guy I knew who was write-a-book invested in Agile was working out Fluid Dynamics analogies with me when we got talking shop. We stopped working together before I made the queuing theory connection.
Awareness, if we can maintain it, is more valuable than gold
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.
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)
We saw with our own tools back when an artist were given a low-core "server" like machine with many CPUs (good we thought), and 2 NUMA nodes, and suddely the level editor for our game was running much slower. We could blame std::shared_ptr<> all day long, or similar but it's there and it was real.
Tried the 4kb interleaved paging, but then everything was equally slow. At the end we simply blocked the App to run only on one NUMA node (still using memory from the other one), and things were back to "normal". "Normal", because promises were not kept - we could not use all CPUs.
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.
What does this mean? I didn't understand
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.
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".
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.
If your company does not have Overtime policy, it's a shitty one.
(Not that, however — having worked many times in the middle of the night — that I disagree with your moral assertions about that.)
Surprised so many people are struggling with this...
Having been on incidents like this before though, yea, that aint happening.
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".
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.
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.
SOMETIMES the company was being prepared for sale...THEN you can only hope you get let go in the first few rounds BEFORE the money for severances runs out
I am sorry that somehow society is beginning to sell the idea that the American workforce does not or need not include rough and ready individuals.
I am aged out of the workforce at this point and find it hard to re-enter due to different problems
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.
The easiest, and the default choice when I worked at Google, was exactly what you said: a sliding scale.
You could target racks, data centers, clusters, regions, etc. And “drain” the unit. For instance, stop routing traffic to cluster foo.
Then you could increment up stepwise 10%, 20%, etc.
Obviously we didn’t use nginx, and sure there’s interesting engineering involved. But it’s not like these systems are magic. There’s just a lot of clusters and a lot of load balancers. But at the end of the day, it’s just a load balancer.
As another Xoogler in this thread pointed out, there’s two problems:
1) Sometime teams accidentally introduce circular dependencies. Service foo might require service bar to boot and vice versa. Typically that’s fine, but from a rare cold start where both foo and bar are down, you’re in a pickle.
2) Load balancing is “easy”. But the services need to be designed with the aforementioned load balancing strategy in mind. Stuff gets tricky if there’s any pollers, process affinity, multiple components that need to process parts of the same user’s request in tandem. Given that outlook is ancient, I would not be shocked to learn that the system doesn’t respond well to naive “slowest ramp up traffic to a cluster” approaches. For big distributed applications, it takes a lot of meticulous design to build a system that responds well to simple SRE techniques like that.
That is one thing my team at Google would actually consider. We would make the code and architecture more complicated to accommodate the types of naive mitigations one would want to apply in an outage.
Does anyone know why the situation got worse on better machines? Normally it is the other way around when it comes to test coverage of hardware specs
I don't think anyone would be astonished by this bug - lock contention is hard. https://www.itnews.com.au/news/kernel-crashing-noisytcp-bug-... is a recent example in the Linux kernel.
This is one of the areas that provably correct software can make a big different and is worth the cost (even before AI)
That whole series reads like sour grapes by someone bitter about how they left.
To put in a car analogy: if you have a ferry that can carry X cars per crossing, increasing either the number of lanes to the ferry (more cores) or increasing the maximum driving speed (faster cores) will only result in longer queues at the water's edge.
Stuff like this also happened prior to AI. One of reasons it happens more frequently now is just now timelines of product development are compressed. So let's say we get 3x outages, but at 10x the speed of new features.
To me it sounds like Outlook team do not have proper gradual rollout for service of this size. Like rollout the new version to 10% servers, let it soak, compare metrics before rolling up higher. Most of "bigtechs" have something like this nowadays.
Cynic in me does not see any need to change anything.
The amount of time, energy, money it would take to have an objectively bad fallback option is crazy.
And then what? Most of the rest of the world is still down...
If I go with Microsoft and they have an outage, everyone is down and we can all commiserate about how it’s Microsoft’s fault and outside our control.
That only scales until stuff takes 2 weeks to come up again. That already happened for us with Atlassian. That was our fault as well, apparently.
can we blame it for the bug? can we credit it for the fix?
might be the most important part of the full report
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.
Here, I converted it to corporate speak for you.
Microsoft does greenfield new stuff on Linux mostly.
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.
Windows 10?
7?
XP?
95?
You mean you and me? You realize pensions, institutions, and individual investors are shareholders as well?
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.
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 fact that you can't apply logical reasoning is your own limitation and you shouldn't presume it applies broadly to everyone.
For example in my country the previous extreme right wing government lowered taxes to high earners. That includes me. I did pay slightly less in taxes, while people who make much more money than me had a much bigger reduction.
So I also had an advantage? LOL NO.
I did not because they also doubled the cost to go and see a doctor so my slight tax reduction wasn't even enough to pay for that.
Of course people who can't do math think "uh good less tax! I vote for them again!", but people who can do some 3rd grade mathematics might realise that they actually paid more.
And we aren't even including the increased health risk in going around when the less wealthy people will naturally tend to go less to the doctor because they are being priced out and infect everyone.
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.
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.
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?
- 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?
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?
Distribution of users by /8 isn't very even and the order that customers will get online wouldn't be an order anyone would pick, but it should be reasonable to implement and synchronize (if needed) and it lets you make progress.
You could do similar in IPv6, start allowing IPs under 2001::, and bump it up little by little... probably each increment would be the 2nd byte, but you do need to increase the first byte too ... or you could be a terrible person and drop ipv6 while you modulate ipv4 and only let ipv6 in when ipv4 is at 100%.
Works better the earliest you can apply it... if your whole stack passes through requests and the origin is looking at X-Forwarded-For (or similar) headers to drop requests, your whole stack worked on it for nothing... Which could be ok, but your frontends might be much happier if they just dropped SYNs from IPs when the request will fail.
Another idea is to have different clients use different ports (enterprise customers on one port, SMB on another) and turn up in the order of SLA.
You probably could do work ahead of time to measure traffic proportions, so you could more accurately modulate and indicate the proportion of traffic allowed. It's nice to be able to increase traffic in measured steps, but it's hard to guess how much traffic will increase for each /8 you add, other than ones that should be zero.
Kind of a hammer approach but "some stuff blackholed" seems better than "everything timing out"
I've definitely been in similar scale war rooms and 15 hours is not acceptable.
The thing with plain outages vs. say, partial degradation of services, you can roll out fast because you're already at worst case scenario *[1].
Here's an interesting one to compare to that I'm very familiar with:
https://status.cloud.google.com/incidents/xVSEV3kVaJBmS7SZbn...
Another really bad one I did not have any involvement in but studied extensively post hoc:
https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1S...
*[1] - I suppose data loss is worse but let's assume most services are stateless.
What's not acceptable to me is a bug of this impact going undetected in production for 6+ months.
You can't even say "but managing fleet/cells is harder": they make software for that, too!
Also this is karma because Microsoft blocked in ignorance entire datacenter networks making SMBs unable to deliver messages to their networks.
Ta-ta!
Perhaps Microsoft will learn from this now they see the direct financial cost themselves of sloppy code.
Looks at my Windows Task Manager...
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