Monday , November 16 2026
outage

Months-old flaw led to a global Microsoft outage: said Microsoft

Microsoft says a software bug introduced in July caused last week’s worldwide Microsoft 365 outage, triggering a cascading failure that left more than 80% of its networking gateway servers unresponsive.

The almost 24-hour outage on November 12 stopped Microsoft 365 services around the world. This affected Outlook, Exchange Online, Teams, and Copilot, making it hard for users to access their email and slowing down message delivery.

Months-old flaw led to a global Microsoft outage: said Microsoft

Microsoft says a software bug introduced in July caused last week's worldwide Microsoft 365 outage, triggering a cascading failure that...
Read More
Months-old flaw led to a global Microsoft outage: said Microsoft

OWASP Top 10 Neocloud & AI Data Center Security Risks

A new OWASP Incubator Project shows a missed area in AI security: servers, networks, and data centers for AI systems...
Read More
OWASP Top 10 Neocloud & AI Data Center Security Risks

Six 0-Days Discovered by Researchers Allow Unauthorized Access to Supermarket Fridge Systems

Six remote code flaws were found in the Danfoss AK-SM800A supermarket fridge controller. These flaws let someone take control from...
Read More
Six 0-Days Discovered by Researchers Allow Unauthorized Access to Supermarket Fridge Systems

Daily Cyber security update for 14.11. 2026

Cyberattacks are rising around the world, including ransomware, malware, data leaks, and hacked websites. These events show how complex and...
Read More
Daily Cyber security update for 14.11. 2026

Huge European telecom leak exposes clients of Swedbank, SEB, airBaltic, and other companies

The Latvian part of CSCTelecom,  a telecommunications provider, made a database with over 125 million SMS messages public. The leaked...
Read More
Huge European telecom leak exposes clients of Swedbank, SEB, airBaltic, and other companies

PHP2Shell attack exploited a Check Point 0-day to deploy malware

Hackers used Check Point firewall flaws to get root access, insert backdoors, and install harmful malware on a VMware ESXi...
Read More
PHP2Shell attack exploited a Check Point 0-day to deploy malware

North Korean hackers steal more than $400 million using video images, FBI says

The United States Justice Department said Thursday it had seized cloud infrastructure used by North Korean hackers in a video-call...
Read More
North Korean hackers steal more than $400 million using video images, FBI says

Microsoft’s November 2026 Patch Tuesday addresses 1,093 flaws, with Outlook zero-day

Microsoft has shared its updates for November 2026. These updates fix 1,093 new flaws in Windows, Office, SQL Server, SharePoint,...
Read More
Microsoft’s November 2026 Patch Tuesday addresses 1,093 flaws, with Outlook zero-day

Barracuda ESG flaws exploited, gaining root access

Barracuda has confirmed active exploitation of security flaws affecting its Email Security Gateway (ESG), warning that attackers could combine two...
Read More
Barracuda ESG flaws exploited, gaining root access

Apple, SAP, and Ivanti Patch Critical flaws Affecting Messaging, Bluetooth, and Enterprise Systems

Apple, SAP, and Ivanti have published security updates that fix several flaws with messaging, Bluetooth, enterprise servers, and endpoint management...
Read More
Apple, SAP, and Ivanti Patch Critical flaws Affecting Messaging, Bluetooth, and Enterprise Systems

In a preliminary post-incident report shared in the Microsoft 365 Admin Center, the company said the outage was caused by three problems: a previously undetected software bug, increased traffic after a Microsoft Teams failover, and reduced server capacity.

The event started at 11:20 AM ET on Thursday, November 12, and went on until 11:10 AM ET the next day, when Microsoft said that services were fully restored.

According to Microsoft, the software bug was introduced in July through an update developed for Microsoft 365 networking gateway servers.

While the update had been deployed for more than three months without issues, it contained a bug that could overwhelm servers under certain traffic conditions, causing them to stop responding.

Microsoft says its tests of the update did not detect the bug as it used less powerful testing hardware than the production servers.

“Our normal load testing did not detect the latent issue because the traffic mix and SKUs used in our labs,” Microsoft explained in its preliminary report.

“The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores.”

The bug happened after Microsoft Teams switched to the network used by Exchange Online about 15 hours before the outage, which made those servers busier.

Microsoft Teams had another outage earlier that day, but it’s not clear if the two problems are connected.

Microsoft says almost 14% of the gateway’s server capacity was already down because of a different problem. The system had enough capacity to handle the drop, but the mix of more traffic and less capacity caused the software bug.

As servers stopped working, Microsoft’s systems sent users to other servers. Those servers also got too much traffic and failed.

“In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive,” explained Microsoft.

Microsoft says safety measures meant to stop problems from spreading between areas also did not work, letting the outages spread globally.

Other Microsoft 365 services, such as Teams, OneDrive, and SharePoint, could change to different systems and recover faster. However, Exchange Online could not do this, so users couldn’t access their mail.

Microsoft says recovery was difficult because restarting affected servers caused them to be quickly overwhelmed again by backed-up traffic.

After identifying the bug, Microsoft engineers developed a fix and deployed it across affected servers, allowing services to stabilize throughout Friday.

Microsoft confirmed that active customer impact had ended by 11:10 AM ET on November 13.

The company says it has increased its capacity, improved its monitoring, and added protections to stop traffic redirection from causing similar failures. In another statement on X, Charles Lamanna, Microsoft’s executive vice president of Copilot, Agents, and Platform, said sorry for the disruption.

“We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations,” Lamanna said.

Microsoft says its investigation is continuing, with a final post-incident report expected later this week.

Check Also

948

OpenAI AI Pipeline Discovers 948 Linux Kernel Privilege Escalation Flaws in 30 Hours

OpenAI says that an automated system found and confirmed 948 different Linux kernel security issues …