Microsoft’s Outlook email service went down for thousands of users on Thursday afternoon, with more than 130,000 failure reports flooding in as workers found they could not open their inboxes.
Key Points
- Outlook and Microsoft 365 went down on Thursday afternoon, 12 November, with failure reports for Outlook passing 130,000 at the peak.
- Microsoft confirmed connection errors in Exchange Online and said it was working to reduce the impact.
- Users in the Americas were hit hardest, with reports also coming in from Canada, the UK and elsewhere.
- A separate Teams problem earlier in the day was fixed around noon; the email outage is a different incident.
- Microsoft now says servers unexpectedly became unavailable after failing health checks; the surge was not caused by extra traffic, and the outage has not been blamed on a cyberattack. No time for full restoration has been given.
What happened in the Outlook outage
The trouble started shortly after midday on the east coast of the United States. Reports of problems with Microsoft’s email and office software began spiking just after 12 p.m. ET on Thursday, 12 November, and climbed fast. By 12:55 p.m. ET, outage tracker Downdetector had counted 22,323 reports about Microsoft 365. Outlook reports were just short of 83,000 just before 1 p.m. ET, and by 1:27 p.m. ET they had passed 130,000, according to Reuters. Microsoft 365 itself drew more than 46,000 reports, while about 3,000 people reported trouble with Teams and 4,400 with Copilot.
Microsoft confirmed the problem publicly just before 1 p.m. ET. Its Microsoft 365 Status account on X said the company was investigating reports of users having trouble reaching their Exchange Online mailboxes through several different connection methods in the Americas. In its service-health notice, tracked as incident EX1550543, Microsoft put the start of the trouble at 11:17 a.m. EST and said it had found connectivity errors in the part of Exchange Online that receives and processes requests to open a mailbox. Engineers were reviewing networking logs to pin down the source of the errors.
For users, the failure showed up in several ways. The web version of Outlook would not load, desktop apps dropped their connection, and some people could not sign in at all. Complaints came in from across the United States and Canada, and from the UK and other countries as well. Microsoft later warned that the problem could affect Microsoft 365 connections in any region, not only the Americas.
Microsoft later said the load was not driven by more traffic: a number of its servers had unexpectedly become unavailable after failing automated health checks, straining the rest of its infrastructure. It has not blamed the outage on a cyberattack. By 4 p.m. ET it said it had validated a different way of checking server health, which had brought some failed servers back into service, and it was applying the change more widely while restarting the rest. Outlook reports had fallen to 32,513 by 6:25 p.m. ET — about 33,000 by the evening — down from a peak of more than 130,000 at 1:27 p.m. ET, but Microsoft has still not given a time for full restoration.
The outage followed a separate problem earlier in the day. Microsoft had posted at 10:40 a.m. ET about trouble with Teams in North America, but said in the same thread that the issue was resolved around noon. The email outage is a different incident, centred on Exchange Online.
Why it matters
Email is the backbone of the working day. When Exchange Online fails, meetings stall, invoices wait, deadlines slip and whole offices are left refreshing an inbox that will not open. Thursday’s failure landed in the middle of the American working afternoon, at the moment when the most people were trying to use it.
It is also the second email problem in a week. Microsoft only fixed a separate Outlook.com fault on 11 November, after a change to its spam rules wrongly blocked legitimate messages. That fault, tracked as EX1545193, was rolled back and mail flow was restored. Two different email failures in three days will sharpen questions about how much of daily work now depends on a single cloud provider, and what happens when it stops.
Microsoft has been pushing deeper into business software, pitching its cloud tools as the place where companies run their working day. Read our report on the IBM and Microsoft enterprise push: https://worldpulsewire.com/2026/11/11/ibm-microsoft-imagine-enterprise/
Cloud tools now run the working day, from email to AI helpers that draft and summarise. Read our report on Google’s Gemini Decisions API launch: https://worldpulsewire.com/2026/11/12/gemini-decisions-api-launches/
What happens next
Microsoft’s update at about 6:59 p.m. ET said servers brought back into service initially remained healthy, but could become unresponsive again once they began receiving traffic, so the recovery so far is limited and gradual as apps reconnect. The company has still not named a root cause, and its next update was due by 8 p.m. ET. Business customers can follow incident EX1550543 in the Microsoft 365 admin centre for the company’s own status.
The second is the Downdetector count. Reports did fall through the evening, to 32,513 by 6:25 p.m. ET, so the outage is fading. If they climb again, the recovery has stalled and a longer disruption is likely.
The third is the full root cause. Microsoft has now said the load came from servers unexpectedly going offline after failing health checks, not from a surge in traffic, and it has not blamed a cyberattack. Until it explains the full chain of events, users will not know whether this was a one-off fault or a weakness that could strike again. World Pulse Wire will update this story as Microsoft confirms more.
Source: Reuters, USA Today, Microsoft 365 Status, WCIA/Nexstar, The National, Swikblog | 13 November 2026



