On a Thursday afternoon in November, the familiar hum of workplace email faltered across much of the world, as people who depend on Outlook, Teams and Microsoft's newer AI assistant found their connections failing one after another. It is the kind of quiet fragility that modern life rests on without thinking: a single company's infrastructure, carrying the correspondence of millions, briefly reminded its users how much they have entrusted to a distant system. Microsoft traced the trouble to strained capacity in part of its network, and is shifting traffic to restore balance, though the full re
Microsoft 365 Outage Disrupts Outlook, Teams and Copilot for Users in India and the US
A restoration notice and a working inbox are not always the same thing.
Mark
Start with the number. Why does 130,000 reports matter?
Mimi
It shows the scale of complaints at one moment, around 1:27 pm ET Thursday. Outlook is how many people run their workday, so that many reports means a lot of stalled inboxes.
Luke
But it's reports, not users. Downdetector gathers them from several sources, and the source itself says the true number may differ.
Mark
So it's a signal, not a headcount.
Mimi
Right. The Outlook, Microsoft 365 and Teams figures, roughly 130,000, 46,000 and 3,000, show relative pain, with Outlook clearly the worst.
Mark
What did Microsoft say caused it?
Mimi
Elevated load on part of its infrastructure, likely contributing to connectivity errors with Exchange Online mailboxes in the Americas. It began redistributing traffic to balance that.
Luke
Note the word likely. That's Microsoft's working explanation, not a confirmed root cause, and nothing says how long the fix will take.
Mark
And India?
Mimi
Users there reported disruption too, and Microsoft said other regions could see Microsoft 365 connectivity effects. The official wording focuses on the Americas.
Luke
Also, Microsoft announced Teams was restored in North America earlier, yet some users still reported problems. Whether those were lingering effects or something new, we don't know.
Mark
What should a reader watch for?
Mimi
A clear all-clear from Microsoft, and whether the reports on Downdetector actually fall.
Der Puls
- Over 130,000 Outlook problem reports flooded Downdetector around 1:27 pm ET, and the alarm spread well beyond American inboxes into India and elsewhere.
- Users could not send or receive messages, or met stubborn connectivity errors when simply trying to open their accounts.
- Teams and Copilot faltered alongside email, with tens of thousands more complaints about Microsoft 365 and thousands about Teams.
- Microsoft is rerouting traffic away from an overloaded section of its infrastructure, yet some Teams users reported trouble even after an earlier all-clear, so full restoration is still unconfirmed.
On a Thursday afternoon in November, the familiar hum of workplace email faltered across much of the world, as people who depend on Outlook, Teams and Microsoft's newer AI assistant found their connections failing one after another. It is the kind of quiet fragility that modern life rests on without thinking: a single company's infrastructure, carrying the correspondence of millions, briefly reminded its users how much they have entrusted to a distant system. Microsoft traced the trouble to strained capacity in part of its network, and is shifting traffic to restore balance, though the full reach of the disruption and the reliability of its promised recovery remain for the coming hours to reveal.
By early afternoon Eastern time on Thursday, complaints about Microsoft Outlook had piled up. Around 1:27 pm ET, Downdetector had logged more than 130,000 reports of email problems, according to Reuters. The trouble was not confined to the United States. Users in India and other countries also found their email unreliable, and the disruption stretched into the early hours of Friday.
The failures took many forms. Some people could not send or receive messages, while others faced delays or connectivity errors whenever they tried to open their accounts. Microsoft 365, the Teams messaging platform and the Copilot AI assistant were drawn in as well. Downdetector also recorded more than 46,000 reports about Microsoft 365 and roughly 3,000 from people struggling to reach Teams. These figures reflect user complaints gathered from multiple sources, so they gauge the scale of the problem rather than counting affected people exactly.
Microsoft acknowledged the trouble in social media updates, saying users in the Americas were having difficulty reaching Exchange Online mailboxes through several connection methods. A later update pointed to elevated load on part of its infrastructure as a likely cause. The company began redistributing traffic to balance that load and clear the errors, and warned that the effects could reach Microsoft 365 users in other regions.
Earlier in the day, Microsoft had announced that a disruption affecting Teams in North America was resolved. Yet users kept reporting connectivity problems afterward, a sign that the fix had not reached everyone.
The open questions are whether traffic redistribution restores normal service and whether the regional spillover materializes. For now, the explanation rests on Microsoft's own account, and the Teams users who struggled after the all-clear are a reminder that an announced recovery and a working inbox are not always the same.
By early afternoon Eastern time on Thursday, the complaints about Microsoft Outlook had piled up. Around 1:27 pm ET, the outage-tracking site Downdetector had logged more than 130,000 reports of problems with the email service, according to Reuters. The trouble reached beyond the United States. Users in India and some other countries also found their email unreliable, and the disruption carried into the early hours of Friday.
The reports described a range of failures. Some people could not send or receive messages. Others saw delays or connectivity errors when they tried to open their accounts. The problems were not confined to Outlook: Microsoft 365, the Teams workplace messaging platform and the Copilot AI assistant were also affected.
Downdetector's other numbers showed how widely the trouble was spread. Beyond the Outlook figure, it recorded more than 46,000 reports of problems with Microsoft 365 and about 3,000 from users struggling to reach Teams. The tracker collects reports from multiple sources, so the figures are a gauge of user complaints rather than an exact count of people affected, and the real number could differ.
Microsoft said it was investigating. In updates on social media, the company said it was aware of users having trouble reaching Exchange Online mailboxes through multiple connection methods in the Americas. A later update gave a possible cause: a portion of its infrastructure was experiencing elevated load, which the company said was likely contributing to the connectivity errors.
The company's stated response was to begin redistributing traffic to balance that load and clear up the errors. It also warned that the disruption could affect Microsoft 365 service connectivity for users in other regions, not only the Americas, where it first identified the problem.
The day had already included a separate episode. Earlier, Microsoft said it had successfully restored a disruption affecting Teams users in North America. Some users nonetheless kept reporting connectivity problems after that announcement, which suggests the claimed fix had not fully taken hold for everyone.
The open questions are whether traffic redistribution brings Outlook and Microsoft 365 back to normal, and whether the regional spillover Microsoft flagged materializes. For now, the cause rests on Microsoft's own description of elevated load, and Teams users who saw problems after the earlier all-clear are a reminder that a restoration notice and a working inbox are not always the same thing.
Bemerkenswerte Zitate
Microsoft said a portion of its infrastructure was experiencing elevated load, likely contributing to the connectivity errors, and that it would begin redistributing traffic.— Microsoft, in social media updates
Möchten Sie die ganze Geschichte?
Das Original lesen bei News18 ↗