Microsoft traces its email outage to a July bug and a recovery cascade

Text
iHOLYSHITVISUAL / TECHUnexpected technology eventsiHOLYSHIT / ILLUSTRATION
iHolyShit illustration

A preliminary review links the failure to a latent defect, shifted traffic and reduced gateway capacity.

Automatic traffic redirection helped spread, rather than contain, the November 12 Microsoft 365 outage. Microsoft's preliminary report dated November 15 says more than 80 percent of the affected networking gateway servers became unresponsive at the worst point.

A defect introduced in July emerged when Teams traffic moved onto the gateway also serving Exchange Online while an unrelated problem had removed nearly 14 percent of its capacity. Requests shifted to the remaining machines, which encountered the same problem. The report says its testing emphasized less powerful hardware, although the defect was worse on newer machines with more cores.

The Register reported that the age of the faulty change frustrated a quick rollback. Engineers instead prepared a corrective update and restored servers in groups. Microsoft's final review is scheduled for November 20. The preliminary findings concern its Microsoft 365 gateway infrastructure.

Share this article

What do you think of this story?

Anonymous feedback, up to 5 reactions per article.

Reader comments

Comment without signing in, or sign in to display your member name.

Discuss the technology and the story. Hate, politics and war, threats, abuse, personal accusations, sexual content, ads, links and personal information are not allowed.

0/500

No comments yet. Be the first to share.

Sources