https://www.youtube.com/watch?v=aoKvn9TvBrQ
Sources for the timeline, since the post-incident report isn't out yet:
Ars Technica on failed health checks and the overloaded core process: https://arstechnica.com/tech-policy/2026/11/microsoft-blames-failed-server-health-checks-not-hackers-for-global-outage/
Moneycontrol quoting Microsoft that it started with an issue from an earlier network capacity upgrade that surfaced after a later network change, not cyber or AI related: https://www.moneycontrol.com/technology/deeply-sorry-microsoft-apologises-for-global-outage-says-network-capacity-upgrade-triggered-disruption-rules-out-cyberattack-article-14079842.html
Envoy panic threshold docs: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/panic_threshold
AWS target group health checks (fail open when all targets are unhealthy): https://docs.aws.amazon.com/elasticloadbalancing/latest/application/target-group-health-checks.html
No comments:
Post a Comment