Nearly 130,000 Reports of Outlook Outage as Microsoft Investigates Connection Errors
Key Facts
A widespread outage hit Microsoft platforms, including Outlook, on November 12, with nearly 130,000 reports of email access problems logged after 1 p.m. Eastern time, according to the Associated Press, citing Downdetector. Microsoft said it was investigating customer reports involving email and Teams after users reported errors in the company’s apps and difficulties using email. The Downdetector figure indicates the volume of user reports; the company did not provide its own count of affected users. The initial notice described difficulties accessing Exchange Online mailboxes through multiple connection methods in the Americas. The breadth of reports suggested the issue affected tools users rely on for email, communication and daily work.
Users described Outlook problems including being unable to send or receive messages, as well as difficulty loading inboxes, according to AP. These symptoms point to disruptions in core email functions, both when exchanging messages and when opening an inbox to check incoming mail. Downdetector logged nearly 130,000 reports after 1 p.m. Eastern time on November 12, according to the tracker as cited by the news agency. That tally reflects users who reported Outlook access problems to the tracker, not an official estimate of the number of accounts or people who lost service. Microsoft did not provide a comparable figure for the impact on its customers in the information cited.
Reports were not limited to email; thousands of users reported problems with Teams, the Copilot assistant and broader Microsoft 365 services, according to AP. This places the outage in a broader context than the Outlook app, while the services users cited differed from the scope of the company’s initial notice. Microsoft said it was investigating customer reports involving email and Teams, and initially described difficulties accessing Exchange Online mailboxes through multiple connection methods in the Americas. AP cited reports about Copilot and other Microsoft 365 services as user reports. Complaints thus covered messaging tools, the AI assistant and office services, alongside the core problem accessing email.
Microsoft said connection errors were likely due to heavy load on part of its infrastructure. The company said that part was “experiencing heavy load,” which was “likely contributing to connection errors.” It offered the load as a possible explanation for the difficulties users reported, without identifying the infrastructure component involved or the extent of the load in the information cited. Microsoft said it would reroute traffic to balance the load, a step aimed at easing pressure on the infrastructure and reducing connection errors. The company did not specify the expected improvement or when the rerouting would be complete.
The Microsoft 365 Status account on X said the company was working to use all available paths to reduce the impact, writing: “We are aggressively pursuing all available paths to reduce impact.” The statement adds to the traffic rerouting plan and indicates the company was working on more than one path to mitigate the issue, according to AP. Earlier in the day, Microsoft said it had successfully resolved Teams-related issues in North America. Some users continued to report connection problems after the recovery announcement, however, leaving complaints unresolved for some users. The statement about restoring Teams did not link that step to resolving the Exchange Online problem.
Microsoft defines a “service degradation” as a confirmed issue that may affect use of a service or feature. The company says the impact of this classification may appear as slow performance, intermittent outages or a feature failure, according to a Microsoft Learn document. The definition provides context for interpreting service-status classifications when the company confirms a problem affecting use, but on its own does not establish how many users are affected or how long the disruption will last. While its investigation and traffic rerouting plan continued, Microsoft said it was pursuing available paths to reduce the impact. The information cited gave no timeline for restoring Outlook or for a subsequent update.