Annanim News
Now
CybersecurityMore stories: Apache Roller, F5 flaws, Rockwell and AGILOX, and quantum researchCybersecurityUkraine and the FBI arrest four suspects in a ransomware gang that collected more than $40 millionQuantum & precision measurementNIST shows the first complete quantum position verification: quantum physics confirms where a person isAutonomous vehiclesTesla tightens driver monitoring in its European driving system: hands on the wheel above 130 km/hCybersecurityPalo Alto Networks to acquire Applied Compute for $4.5 billion in stockModels & researchGoogle launches Gemini 4 Neon, a fast model for code, office work and agentsChinaChina Watch: Tencent raises its computing infrastructure spending sixfoldCybersecurityDecade-old NGINX flaw lets attackers run code on HTTP/2 servers without logging inRegulation & businessAnthropic prices its IPO at $83 a share, above the range, and starts trading on Nasdaq todayCybersecurityMore stories: cracking BitLocker PINs, Russian hackers and Nvidia's guaranteesSpace, satellites & commsVoyager 1 becomes the first human-made object one light-day from EarthCybersecurityIsrael's Vero Security raises $11 million to secure enterprise AI agentsAI agentsGoogle turns its Spark agent into Tasks inside Gemini and makes it free

Originally published:

Microsoft: a bug from July caused the global Microsoft 365 outage

In a preliminary report, Microsoft said an update to its networking gateway servers, deployed in July, contained a bug that knocked out more than 80% of the servers at once. The 12 November outage lasted almost a full day.

Microsoft: a bug from July caused the global Microsoft 365 outage
Image: BleepingComputer (opens the source site in a new tab)

According to the report, posted in the Microsoft 365 admin centre and quoted by BleepingComputer, three factors combined: an undetected bug, extra traffic after Teams automatically failed over to Exchange Online's infrastructure about 15 hours before the outage, and roughly 14% of server capacity already offline because of an unrelated issue. Load testing missed the bug because it ran on weaker hardware with fewer cores than the production servers.

"In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive," Microsoft wrote. Systems redirected users to other servers, which failed in turn, and safeguards between regions did not contain the spread. Teams, OneDrive and SharePoint switched to alternative infrastructure and recovered earlier, but Exchange Online could not, leaving users without access to their mailboxes.

The outage ran from 11:20 a.m. ET on 12 November to 11:10 a.m. the next day. Among other effects, it stopped a hotel safety system in Germany from sending alerts about a chlorine leak. Microsoft said it has added capacity, improved monitoring and added safeguards, with a final report expected later this week.

Sources

Topics

Install the app

In Safari: tap the Share button, then “Add to Home Screen”.