We've had spectacular infrastructure outages for decades; I think that a cluster of incidents in one week doesn't establish that AI is directly responsible for declining reliability.
IMO, the issue is that AI is reducing the cost of building and modifying systems much faster than it's reducing the cost of understanding them. For example, an engineer can work on a problem or project for a week that could otherwise be done by AI in an hour or so. But, that week spent was not "wasted time"; it was understanding what it is they are building, discovering undocumented assumptions, knowing about different dependencies, developing intuitions about the system and how it works, etc.
This causes comprehension debt. Yes, the system does ultimately work, the tests also pass. But the level of comprehension goes down significantly.
That said, AI can also help reduce this debt by asking it what you need help understanding.
A good blog post on this: https://larsfaye.com/articles/ai-coding-will-prevent-experti...
Skills, metaskills, and learning by doing.
When you change a system directly you learn the underlying nature of the system and your toolset for making changes. Guide a third party toward making the changes and you learn the nature of the interaction and your toolset for evaluating the outcome of changes.
Does the distinction matter? Depends on your perspective I suppose.
I indict management, not AI. Redundancy and robustness required money and effort, neither of which add to the bottom line or get quicker to market. Cynically, it costs more to prevent failure than endure or recover from one. So business take the obvious fork.
And as far as air traffic is concerned, they’ve been trying to strangle it since at least 1980. Canada has a privatized system, so it’s possible to create such things but that is a matter of political will not money.