Michał "rysiek" Woźniak · 🇺🇦You will not believe the trick-or-treat trick Microsoft just pulled! 
Choose your fighter!
DNS
BGP
Poll ended at .
Before anyone mentions how reliable Google Cloud is, here's a massive outage from June this year:
https://www.cnbc.com/2025/06/16/google-cloud-outage-apology.html
And from October last year:
https://status.cloud.google.com/incidents/e3yQSE1ysCGjCVEn2q1h
Oh don't worry, Azure is not having a *global* outage, just a "non-regional" one.
If you're a journalist writing about this Azure outage, don't forget to ask Microsoft how much of their code is "AI-generated".
Satya Nadella claims 30%:
https://www.cnbc.com/2025/04/29/satya-nadella-says-as-much-as-30percent-of-microsoft-code-is-written-by-ai.html
Microsoft Azuren't
> We have confirmed that an inadvertent configuration change was the trigger event for this issue.
Folks, it's all okay! It was just an inadvertent configuration change [that happened to bring loads of services for millions of users down]. No biggie.
Look, this is the level of professionalism we should expect of Microsoft at this point.
They had a separate global outage of Office 365 (or whatever it's called this week) *this month* already:
https://www.bleepingcomputer.com/news/microsoft/microsoft-365-outage-blocks-access-to-teams-exchange-online/
And then there was the one from February this year:
https://www.upi.com/Top_News/US/2025/03/01/microsoft-outages/3061740867107/
Not to mention smaller ones, like the one in US-East that prevented admins from accessing the admin center:
https://www.bleepingcomputer.com/news/microsoft/microsoft-investigates-outage-affecting-microsoft-365-admin-center/
I wonder if firing 15.000+ employees just this year had any impact here. 
https://www.windowscentral.com/microsoft/microsoft-continues-layoffs-with-42-more-roles-cut-for-the-fifth-month-in-a-row
While Azure was down and you could not use your Office 365 for 8 (eight) hours yesterday, Microsoft was gloating about record profits:
https://www.theguardian.com/technology/2025/oct/29/microsoft-earnings-azure-outage-xbox
After all, Office 365 price has increased at least twice over the last 12 months, massively:
https://www.tomsguide.com/computing/microsoft-365-gets-massive-45-percent-price-hike-and-its-all-to-do-with-ai-tools
https://techcommunity.microsoft.com/blog/publicsectorblog/upcoming-changes-office-365-g1-price-increase-effective-march-2025/4385970
Price hikes were due to "AI", obviously. It's what users crave.
Your Microsoft Tax dollars at work! 
Two price hikes, three major outages…
Microsoft will have to hike the price again just to keep the ratio at 1:1!
This might be a good time to consider deploying, contributing to or otherwise supporting @nextcloud:
https://nextcloud.com/
And before anyone says that Nextcloud's UI/UX is lacking: of course it is! Nextcloud has several orders of magnitude less money to throw at UI/UX.
But guess what:
1. this is fixable if they get more resources to work with;
2. every single Nextcloud instance I know of or use (there are many) stayed up and running yesterday.
Cascading failure. It cascaded.
> As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy.
https://azure.status.microsoft/en-us/status/history/#incident-history-collapse-YKYN-BWZ
> An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption…
> The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations.
Am I reading this right? Global – pardon, "non-regional" – #outage of #Microsoft #Azure was caused by a tenant changing their config? 👀
Can't have a snow day without cloud. 🌨️
These massive "cloud" outages will continue to happen, inevitably, because they are "normal accidents":
https://en.wikipedia.org/wiki/Normal_Accidents
Any system that:
- is complex,
- is tightly coupled, and
- has catastrophic potential
…can be expected to experience catastrophic failures. AWS, Google Cloud, #Microsoft #Azure check all these boxes.
Fun fact: Internet was specifically designed to *not* be like that. It was designed to be loosely coupled.
But that's not as good for maximizing shareholder value!
Allan Svelmøe Hansen@rysiek I know I'm only an average 'in the trench' type developer, and my interests have always been code over servers/hosting........
But I cannot express how much I miss the "old days" of normal web-servers and where focus was on delivery of (customer/user) value and optimisations and not just bloating everything with external services sold into a cloak of 'critical infrastructure' and 'pass/sass' cloud stuff.
bovaz@svelmoe @rysiek and now, saying "we do the code, and build it. I can go as far as a container image, but someone else has to take care of all the steps after that." brands me as someone difficult to work with.
Used to be we could just deploy stuff on a server. Now we are supposed to encode every aspect of the infrastructure, and are considered mad if we point out that's several additional jobs on top of what we do.
Used to be we could just deploy stuff on a server. Now we are supposed to encode every aspect of the infrastructure, and are considered mad if we point out that's several additional jobs on top of what we do.