Competent people have a look what the network can take in addition to what it carries, then shape a new thing down well below that. And make sure they can turn it off fast. Sounds a like nobody even checked. Amateurs.

I have seen this extreme level of stupidity only with IBM tech consultants before. They killed the network of a large bank were I also transferred monitoring data, pretty much the same as they did. The difference is my first question was how much data and my second how much bandwidth can I safely use. And the bank had all that very nicely. The IBM morons just built software and then pushed everything on the net and were surprised when that did not work. Fortunately the bank got their crap killed in half an hour or so. And then these idiots asked me where I got my traffic figures. 2 years into their project. Sounds like something like that happened here as well. Just with a teensy bit more damage.

You would think competent engineering and tech risk management is done of critical infrastructure. Microslop thinks differently, the all-mighty dollar is more important. And, to be fair, unless they continue to screw up this badly, nothing is going to happen to them. Their customer population is even more incompetent than they are.

That does not make it any better. It just means there is another area they are incompetent in. The main reason why you run tests like this and design and roll out any automatism that can take down a server very carefully is exactly because you may have other things that can come crashing down if you mess this up. Oh, and look, exactly that happened.

This is simply another piece of hard evidence that Microslop cannot hack reliable infrastructure. Smart people already knew that, but apparently more evidence is needed before the thick-skulled Microlop admirers notice something.

... and thinks the rules do not apply to him. What else is new?

Yes. Very much so. And all the large tech enterprises are not either.

Sure. Not a direct dependency. But if it turns out L3Harris is dependent on O364 (with some delay), that would make it an indirect one.

Sad as that is, yes. But this is a step to make regulation more likely, even if only in Europe.

Oh, and now the White House claims no connection to Microslop. With the current probability of them lying, I would call that conformation.

Usually you get the people holding it to hand it over, for example another exchange or somebody that got arrested.

Canada is apparently not affected at least that is the reporting here in Europe.

But this may well be some indirect dependency on Microslop systems. For a direct dependency (which would be illegal) the shutdown would already have happened a day earlier, hence I guess that is not it. But IT has gotten way too complex and unintended consequences wayyyyy to likely. My bet is we are seeing one here.

Indeed.

Extreme incompetence or them getting hacked again? Well. Usually I would say these people just cannot do things right, but them getting attacked would also be an instance of that, so...

The real reason is that these health checks can take down enough servers that the remaining ones get overwhelmed. This can only be called gross incompetence.

Nothing was changed and people did not learn from the previous outages. It will get worse until the mind-set and approaches get fundamentally changed from "cheapest possible" to "reliability first".

Apparently they did run some diagnostics on some authentication servers. The diagnostics was faulty and shut down the servers (as it is apparently allowed to do). The remaining ones got overwhelmed.

This is also known as "gross incompetence". You know, Microslop doing its usual thing.