ON
← Back to feed
Microsoft failure: undetected program error was the cause
Austria💻 Technology

Microsoft failure: undetected program error was the cause

A previously undiscovered software bug in Microsoft's system caused a global outage of services like Outlook and Teams last week. According to Microsoft, three factors combined to create a chain reaction: during the peak of the disruption, more than 80% of responsible computers failed to respond. The error originated from a software change in a central digital gateway for Microsoft 365 traffic, which had been deployed in July but went unnoticed for over three months. Previous lab tests did not detect the issue because they used older equipment, while the problem primarily affected newer, more powerful servers. The failure occurred on Thursday during peak usage hours in the U.S., compounded by two additional stressors: Teams had recently switched to the same main infrastructure, increasing data traffic, and nearly 14% of server capacity was temporarily unavailable due to another technical issue. As some servers failed under heavy load, Microsoft’s automatic control redirected user requests to remaining servers, triggering the same error there. Within less than two hours, this domino effect nearly brought down the entire system. Digital barriers between regions also failed, spreading the outage globally. Repair efforts were delayed because email systems like Outlook could not easily reroute traffic, unlike Teams or OneDrive. It took until Saturday to fix the issue after Microsoft developed a special repair update and gradually restarted servers in groups.

4 reports

Kleine Zeitung logoKleine ZeitungParty-alignedCenter
Microsoft failure: undetected bug triggered chain reaction

A previously undiscovered software bug in Microsoft's system triggered a global outage affecting services like Outlook and Teams last week. According to Microsoft, the issue originated from a software change made to a central gateway for data traffic in Microsoft 365 back in July. The error remained undetected for over three months until it caused a chain reaction during peak usage hours in the U.S. Additional stressors, including a planned switch of Teams to the main infrastructure and a temporary loss of 14% server capacity due to another technical problem, contributed to the failure. As servers began to fail under high load, Microsoft’s automated system rerouted traffic, inadvertently causing the same error across remaining servers. This created a domino effect that spread globally due to failed digital barriers between regions. The repair process took several days because the email system Outlook could not easily redirect traffic, unlike other services such as OneDrive. The outage impacted more than 70 countries, disrupting businesses, courts, schools, and government agencies, with particularly severe effects on healthcare systems.

Bias read (Center): The article provides a balanced account of the technical causes and consequences of the Microsoft outage without apparent ideological framing or biased language.

Kurier logoKurierParty-alignedCenter
Microsoft failure: undetected program error was the cause

A previously undiscovered software bug in Microsoft's system caused a global outage of services like Outlook and Teams last week. According to Microsoft, three factors combined to create a chain reaction: during the peak of the disruption, more than 80% of responsible computers failed to respond. The error originated from a software change in a central digital gateway for Microsoft 365 traffic, which had been deployed in July but went unnoticed for over three months. Previous lab tests did not detect the issue because they used older equipment, while the problem primarily affected newer, more powerful servers. The failure occurred on Thursday during peak usage hours in the U.S., compounded by two additional stressors: Teams had recently switched to the same main infrastructure, increasing data traffic, and nearly 14% of server capacity was temporarily unavailable due to another technical issue. As some servers failed under heavy load, Microsoft’s automatic control redirected user requests to remaining servers, triggering the same error there. Within less than two hours, this domino effect nearly brought down the entire system. Digital barriers between regions also failed, spreading the outage globally. Repair efforts were delayed because email systems like Outlook could not easily reroute traffic, unlike Teams or OneDrive. It took until Saturday to fix the issue after Microsoft developed a special repair update and gradually restarted servers in groups.

Bias read (Center): The article provides a balanced account of the technical causes and effects of the Microsoft outage, using neutral language and focusing on factual explanations without apparent ideological framing.

Die Presse logoDie PresseParty-aligned🔒Center
Undetected program error caused Microsoft to crash

A previously undiscovered software bug in Microsoft's system triggered a global outage affecting services like Outlook and Teams. According to Microsoft, three factors combined to create a chain reaction: an undetected programming error introduced in July, increased data traffic due to a planned switch of Teams to a central infrastructure, and temporary server capacity loss caused by another technical issue. When servers began failing under high load, Microsoft's automatic rerouting system exacerbated the problem by triggering the same error across remaining servers. The failure spread globally due to failed digital barriers between regions. Repair efforts were delayed because Outlook could not be rerouted easily, requiring a special update and gradual restart of servers.

Bias read (Center): The article provides a balanced account of the technical causes and effects of the outage without ideological framing or biased language.

ORF News logoORF NewsState / PublicCenter
Program error and chain reaction behind Microsoft failure

A previously undiscovered software bug in Microsoft's system caused a global outage of services like Outlook and Teams last week. According to Microsoft, three factors contributed to the chain reaction: during the peak of the disruption, more than 80% of the responsible computers failed to respond. The error originated from a software change in a central digital gateway for Microsoft 365 traffic, which had been implemented back in July. The issue went unnoticed for over three months because previous lab tests used older technology, while the problem primarily affected newer, more powerful servers. The error occurred during peak usage hours in the U.S., compounded by two additional stressors: Teams had recently switched to the same infrastructure, increasing data traffic, and another technical issue temporarily rendered nearly 14% of server capacity unavailable.

Bias read (Center): The article provides a balanced account of the technical causes and contributing factors without ideological framing or biased language.

How each side covered it

The same event, grouped by the political lean of the outlets covering it.

How each side covered it

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Covered around the world

The same event as reported in other countries.

Covered around the world

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Claims check

Key factual claims, and how many sources assert vs dispute each.

Claims check

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Keep the news honest.

ObjectiveNews is reader-funded and ad-free — we show you the bias instead of hiding it. Support independent journalism for €4/month.

Become a Supporter

Related stories