All Newz
Breaking Newz

Microsoft Outlook and 365 Services Hit by Massive Multi-Hour Outage Linked to Server Failures

A widespread Microsoft Outlook outage stretched beyond eight hours on Thursday after servers kept failing automated health checks and crashing after being brought back online. The disruption affected Exchange Online, Teams, and multiple workplace tools, leaving organizations and institutions scrambling as engineers worked to deploy automated fixes.

By Kulture Newz StaffNovember 13, 20262 min read
Breaking Newz — Kulture Newz
Microsoft Outlet

A major disruption to Microsoft Outlook and associated Microsoft 365 services extended past eight hours on Thursday, cutting off access to work inboxes and enterprise communication tools across North America and other regions, according to reporting by Baller Alert.

The widespread disruption began shortly before 1 p.m. Eastern Time on Thursday, November 12. At 12:54 p.m., Microsoft announced that it had launched an investigation into connectivity failures preventing users in the Americas from reaching their Exchange Online mailboxes. Because Exchange Online manages email infrastructure for schools, companies, and major institutions, the breakdown halted outgoing messages, prevented incoming deliveries, and blocked users from opening their email accounts. Microsoft quickly issued a follow-up warning that the connectivity issues could spread to Microsoft 365 customers globally.

According to tracking data from Downdetector cited by Baller Alert, user-submitted incident complaints peaked above 130,000 shortly after 1 p.m. While reports declined throughout the afternoon, they remained above 30,000 well into Thursday night.

The service breakdown extended beyond Outlook. Baller Alert reported that Microsoft Teams, SharePoint Online, and Microsoft 365 Copilot were quickly pulled into the disruption. By late afternoon, Microsoft expanded its list of compromised platforms to include Intune, Defender for Office 365, Purview, and Power BI.

Microsoft disclosed that the failure originated when several servers abruptly became unavailable, forcing surviving systems to shoulder excess traffic across multiple regions. The company emphasized that the crash was not caused by an unexpected traffic surge. Rather, critical servers began failing their automated health checks and dropped offline. In an initial bid to contain the damage, Microsoft paused system deployments, diverted network traffic, and restarted affected infrastructure. Although the company initially noted that no recent administrative change aligned with the outage's onset, officials later shifted course, confirming that engineers are investigating a small set of configuration updates as potential factors.

Attempts to stabilize the platform faced immediate setbacks. Around 6 p.m., Microsoft reported that a portion of the offline servers had returned to service. However, those machines quickly became unresponsive again once live traffic hit them. Microsoft acknowledged that its earlier actions had failed to provide anticipated relief because an overwhelmed core process caused servers to shed operating capacity.

The operational impact rippled across multiple sectors. In Canada, a Toronto hospital network issued a Code Grey emergency alert for critical infrastructure failure, while rail operator VIA Rail encountered system issues. Higher education institutions, including the University of Toronto, Seneca Polytechnic, and George Brown Polytechnic, reported that student and staff email networks were compromised. AI providers OpenAI and Anthropic also suffered connection disruptions tied to Microsoft infrastructure.

By 9 p.m. Thursday, Microsoft indicated that repair operations were underway, including an automated recovery mechanism to detect and reboot unresponsive servers, though it declined to provide a firm timeline for full system restoration.