On a Thursday afternoon in November, the working day of much of North America was interrupted when Microsoft's email service and a cluster of its productivity tools stopped responding for users across the Americas. The company, which has built much of modern office life on its cloud, found itself explaining a strain on parts of its own infrastructure, a reminder that the systems carrying our shared work are only as steady as the invisible machinery beneath them. For now the cause remains a careful hypothesis, and the people waiting on their inboxes are left to wait as the company rebalances th
Microsoft Outlook Outage Hits Users Across North America as Teams, SharePoint and Copilot Also Go Down
A failure in one place can quickly turn into a failure of the whole workday.
Mark
Start with the basics. What actually broke on Thursday?
Mimi
Outlook first. People couldn't get into Exchange Online mailboxes, both personal and enterprise users. Teams, SharePoint Online, Microsoft 365 apps and storage, and Copilot 365 were affected too.
Mark
And how big was it?
Mimi
Downdetector logged more than 129,000 error reports by 1:09 p.m. Eastern, with the spike starting around 12:39.
Luke
I'd be careful with that number. Downdetector counts user-submitted reports. It isn't a headcount of affected people, and it isn't a Microsoft figure.
Mark
Fair. What has Microsoft said about the cause?
Mimi
That a portion of infrastructure had elevated load across multiple regions, which it said was likely contributing to the errors. It began shifting connection traffic across its wider worldwide infrastructure.
Luke
Note the hedge. "Likely contributing" is not a confirmed root cause. And the company is separately examining an unexpected rise in one type of service traffic, without saying what type.
Mark
So users noticed before Microsoft said anything?
Mimi
By about fifteen minutes, going by Downdetector's spike at 12:39 and the status post at 12:54.
Luke
That's the gap between the two timestamps, yes. What we don't know is when service was fully restored, whether the reach extended beyond the Americas, or what triggered the load. Those are open.
Der Puls
- Outlook, Teams, SharePoint and Copilot 365 went dark for individual and enterprise users at the height of the working day.
- Downdetector reports surged past 129,000 within half an hour, a sign of how quickly the disruption spread.
- Microsoft acknowledged elevated load across multiple regions and said it was only likely the cause, not yet confirmed.
- Engineers are redistributing connection traffic across the global network while investigating an unexpected spike in one type of service traffic.
- No restoration timeline has been given, and the full geographic reach and root cause remain open questions.
On a Thursday afternoon in November, the working day of much of North America was interrupted when Microsoft's email service and a cluster of its productivity tools stopped responding for users across the Americas. The company, which has built much of modern office life on its cloud, found itself explaining a strain on parts of its own infrastructure, a reminder that the systems carrying our shared work are only as steady as the invisible machinery beneath them. For now the cause remains a careful hypothesis, and the people waiting on their inboxes are left to wait as the company rebalances the flow of traffic and searches for its origin.
At 12:54 p.m. Eastern on Thursday, Microsoft's 365 Status account on X posted a brief notice that it was investigating trouble reaching Exchange Online mailboxes across the Americas. By then, a large portion of North America's workday had already been disrupted. Users found themselves locked out of Outlook, whether on personal accounts or within large organizations, and the trouble quickly spread to Microsoft Teams, SharePoint Online, the Microsoft 365 suite and the Copilot 365 AI service. For many offices, these tools are the workday itself, so a single failure becomes a stalled organization.
Downdetector recorded the surge before Microsoft said anything publicly. Reports began climbing around 12:39 p.m. Eastern, and by 1:09 p.m. more than 129,000 error reports had been logged. These are user submissions rather than a count of confirmed victims, but they show how fast the problem traveled.
At 1:35 p.m. Eastern, Microsoft offered its first explanation: a portion of its infrastructure was under elevated load across several regions, which it said was likely behind the connection errors. The company has begun shifting traffic across its wider global infrastructure to ease the strain. Its Service Health Status page added that Teams engineers were examining an unexpected rise in a specific type of service traffic, though it did not say what that traffic was, where it originated, or whether it was the cause or merely a symptom.
Variety has asked Microsoft for further detail. So far, no timeline for full restoration has been offered, and the reach of the outage beyond North America remains unclear. What comes next is the rebalancing of traffic, the identification of its source, and whether Microsoft offers a full account once the lights come back on.
At 12:54 p.m. Eastern on Thursday, the Microsoft 365 Status account on X posted a short notice: the company was investigating reports of users having trouble reaching Exchange Online mailboxes through multiple connection methods in the Americas. By then, a large part of North America's working day had already been interrupted.
The trouble centered on Outlook, Microsoft's email service. Both individual users and people on enterprise accounts reported being unable to log in. Variety described the outage as massive, affecting users across North America and potentially other regions, though the full geographic reach has not been established.
Outlook was not the only service affected. Microsoft Teams, the Microsoft 365 suite of productivity tools and cloud storage, the Copilot 365 AI service and SharePoint Online were also hit. Those products sit at the center of daily work for many organizations, which is why a failure in one place can quickly turn into a failure of the whole workday.
The monitoring platform Downdetector gave a sense of the timing and scale. User reports of Outlook problems began spiking at around 12:39 p.m. ET, roughly a quarter of an hour before Microsoft's first public acknowledgment. By 1:09 p.m. ET, more than 129,000 error reports had been logged. That figure counts reports submitted by users, not the number of people actually affected, but it shows how fast the problem spread.
At 1:35 p.m. ET, Microsoft offered its first explanation. The company said a portion of its infrastructure was experiencing elevated load across multiple regions, which it said was likely contributing to the connectivity errors. The word "likely" matters: Microsoft did not say it had confirmed the cause. It also said it had begun redistributing connection traffic across its broader worldwide infrastructure to help balance the load.
Microsoft's Service Health Status page added another detail. Teams were reviewing an unexpected increase in a specific type of service traffic, to determine whether it was contributing to the elevated load. The company did not say what kind of traffic it meant, where it came from, or whether it was the root cause or a symptom.
Variety said it had contacted Microsoft for more information. As of the latest available reporting, the company had given no timeline for full restoration. What to watch next: whether the traffic redistribution brings services back, what Microsoft identifies as the source of the unexpected traffic, and whether it publishes a fuller account of the failure afterward.
Bemerkenswerte Zitate
A portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors.— Microsoft 365 Status account on X
Möchten Sie die ganze Geschichte?
Das Original lesen bei Variety ↗