On a Thursday afternoon in mid-November, the quiet machinery that carries so much of modern working life faltered, as people across the world found their email and collaboration tools suddenly out of reach. Microsoft, whose systems have become the daily furniture of offices and homes alike, moved to halt its own changes, pull traffic away from the strained infrastructure, and restart the servers at its core. The cause remains unnamed, but the episode reminds us how far a single company's failure can ripple across borders, time zones, and the routines of ordinary people who simply wanted to sen
Microsoft Outlook Outage Hits Users Across 74 Countries as Company Investigates Email and Teams Disruptions
Fewer than 15 reports a minute on a normal Thursday. Then 19,650.
Mark
So what actually broke on Thursday?
Mimi
Outlook email stopped sending and receiving for a lot of people. Downdetector logged nearly 130,000 reports shortly after 1 PM Eastern, and Microsoft said it was investigating.
Luke
Worth saying up front: Downdetector counts user reports, not confirmed affected accounts. It's a signal of scale, not a headcount.
Mark
Fair. But the spike seems enormous.
Mimi
It is. Five Microsoft services combined hit 19,650 reports per minute, versus fewer than 15 on a normal Thursday. Outlook alone peaked at over 2,000 times normal.
Mark
And it wasn't just the US?
Mimi
No. Reports rose tenfold in the UK, India and New Zealand, and nearly 30% of reports in the 17:00 to 18:55 UTC window came from outside the US. Microsoft first said the Americas, then widened that to any region.
Luke
That revision matters. The initial scope was wrong or incomplete, so early figures deserve caution.
Mark
What did Microsoft do to fix it?
Mimi
It stopped all deployments, redirected traffic away from the affected infrastructure, and restarted impacted servers.
Luke
Notice what's missing: a cause. Stopping deployments hints at a possible change-related problem, but Microsoft hasn't said that, so it's only inference.
Mark
And the duration? One figure says nearly an hour.
Luke
That's Downdetector's account. Reports were still around 60,000 at 3 PM Eastern, so how long individual users were affected isn't established here.
Mimi
The incident number, EX1550543, is where Microsoft says more will appear.
Il Polso
- Over 130,000 reports flooded Downdetector within the first hours as Outlook users were suddenly cut off from sending and receiving email.
- Outlook complaints spiked to more than 2,000 times their normal level while Teams, OneDrive, Copilot and Azure reports jumped roughly a hundredfold.
- Microsoft halted all deployments, rerouted traffic away from the affected infrastructure, and began restarting impacted servers to restore service.
- The disruption reached 74 countries and territories, with reports in the UK, India and New Zealand rising tenfold, and the company has yet to name a root cause.
On a Thursday afternoon in mid-November, the quiet machinery that carries so much of modern working life faltered, as people across the world found their email and collaboration tools suddenly out of reach. Microsoft, whose systems have become the daily furniture of offices and homes alike, moved to halt its own changes, pull traffic away from the strained infrastructure, and restart the servers at its core. The cause remains unnamed, but the episode reminds us how far a single company's failure can ripple across borders, time zones, and the routines of ordinary people who simply wanted to send a message.
Shortly after 1 PM Eastern on Thursday, November 12, people trying to send or receive email through Microsoft Outlook began running into trouble, and the reports piled up fast. On the outage tracker Downdetector, nearly 130,000 users flagged problems. By about 3 PM Eastern, with a fix underway, that number had eased to around 60,000.
Microsoft's first public word described disruptions in the Americas, but the company soon widened the picture, confirming that the problem could touch Microsoft 365 connectivity for users in any region. Details were posted to the admin centre under incident EX1550543. The company said it had stopped all deployments, redirected traffic away from the affected infrastructure, and started restarting impacted servers. Its public statement was brief: it was investigating reports of users experiencing issues.
Downdetector's timeline shows how fast it spread. Outlook reports climbed sharply after 17:25 UTC and peaked at more than 2,000 times normal levels. Microsoft 365, Copilot, Teams and OneDrive each jumped past a hundredfold, and several users said they could not get into Teams.
The disruption crossed oceans. Downdetector logged problems in 74 countries and territories, with reports rising tenfold in the UK, India and New Zealand, and nearly a third coming from outside the US. Microsoft had not named a root cause in the material available, and the admin centre entry remains the place to watch for an explanation of what failed.
Shortly after 1 PM Eastern Time on Thursday, November 12, people trying to send or receive email through Microsoft Outlook began running into trouble, and the reports piled up quickly. On the outage tracker Downdetector, nearly 130,000 users flagged problems with the service. By about 3 PM Eastern, with the fix underway, the count had fallen to around 60,000.
Microsoft's first public word came through the Microsoft 365 Status account on X, which described service disruptions in the Americas. That framing did not hold. In a later post, the company confirmed the problem could affect Microsoft 365 connectivity for users in any region. It pointed customers to the Microsoft 365 admin centre, where details were being published under incident number EX1550543.
The company described what it was doing about it. It had stopped all deployments, redirected additional traffic away from the affected infrastructure, and begun restarting impacted servers to bring services back. Microsoft's statement to the public was brief: it was investigating reports of users experiencing issues.
Downdetector's own timeline, posted on X, gives the sequence in more detail. Microsoft said its Exchange Online incident began at 16:17 UTC. Reports of Outlook trouble started climbing around 17:25 UTC. By 18:25 UTC, reports across five Microsoft services combined had reached 19,650 per minute, against fewer than 15 per minute on an average Thursday. Outlook reports alone peaked at more than 2,000 times their normal level.
The disruption reached well beyond the United States. Downdetector recorded the outage in 74 countries and territories, lasting nearly an hour by its account. Reports rose tenfold in the UK, India and New Zealand, and nearly 30% of the reports logged between 17:00 and 18:55 UTC came from outside the US.
Outlook was not the only product affected. Microsoft 365, Copilot, Teams and OneDrive each saw reports jump to more than 100 times their usual levels, and Azure reports rose roughly 100-fold. Several users said they had trouble getting into Teams. A similar Teams problem had been reported earlier in the day in North America; Microsoft said it had resolved that one in the region.
Microsoft had not given a root cause in the material available. The admin centre entry, EX1550543, is where updates on the fix and the affected services are meant to appear, and it is the place to watch for an explanation of what failed.
Citazioni salienti
While we're working to mitigate impact, we've confirmed the issue may affect Microsoft 365 service connectivity for users in any region.— Microsoft 365 Status, on X
Vuoi la storia completa?
Leggi l'originale su Lokmat Times ↗