From The Next Web · Ana Maria Constantin · · 1m 50s
TL;DR: Microsoft traces 365 outage to dormant July bug
A defect in July's network gateway update lay hidden for three months before a surge in load triggered a cascade failure across Microsoft's services.
Microsoft blamed last week's global outage on a July bug that lay dormant for three months before load and capacity loss triggered a cascade affecting over eighty percent of gateway servers. A defect in July's network gateway update lay hidden for three months before a surge in load triggered a cascade failure across Microsoft's services.
- July update hid a latent defect
- Testing missed the flaw in the code
- Three conditions collided at once
- Cascade failure spread across servers
Read the story version — the same reporting as a swipeable deck of 7 cards.



