the crowdstrike outage highlights the fact that software engineering is a slowly improving business and that the apparent gains created by closed source and shitloads of VC capital do not win honestly against open source

they only appear to be better, until the outlying factors, the long tail, shows its head - and everyone has the proof of the error of centralization and closed source and this endless parade of update patches proves to be a bad production model

meanwhile bitcoin nodes are running right now for years of uptime that were written in 2015, without being updated, built on technology and using designs that are well proven and not squeezing that long tail and inviting this kind of broad scale problem

now, where is that saturnian wannabe Dr Evil Schwab right now on the subject of the cyberpolygon?

literally we are watching what could be interpreted as a cyberattack but is probably some addled devops person who forgot to run some tests before dropping the update, who probably is going to be villified and doxxed in 3, 2, 1...

Reply to this note

Please Login to reply.

Discussion

Not to forget the stolen Azure Master Key last year!

Good morning 🦫

"a backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks hosted on impacted storage resources."

So it wasn't a person at all, according to this theory. It was a "workflow." Perhaps AI is to blame! I think your theory was right.

yeah, bad workflows lead to bad results too

like #nostr NIPs repo, which should be a wiki to make searching easier and contribution lower friction

the result of this with nostr has been a poor convergence of implemenatations

Wait. People's Windows desktops were affected? That is nuts.

i don't think so, but they could have been, it was an antivirus app right?

Are there two separate outages? One from a crowdstrike product and one from Azure? Or are they the same outage?

It appears there are two outages, from https://azure.status.microsoft/en-gb/status:

> We are aware of an issue that started on July 18, which resulted in customers experiencing unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, affecting both on-premises and various cloud platforms (Azure, AWS, and Google Cloud).

>

> It’s important to clarify that this incident is separate from the resolved Central US Azure outage (Tracking Id: 1K80-N_8). Microsoft is actively providing support to assist customers in their recovery on our platforms, offering additional guidance and technical assistance.