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.
azure.status.microsoft/en-us/s

> 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" – of was caused by a tenant changing their config? 👀

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mstdn.social/users/rysiek/statuses/115462135933911614 on your instance and quote it. (Note that quoting is not supported in Mastodon.)