Microsoft Outlook Outage Leaves Office Workers Stranded Across the United States

No outlook, no teams.... how about we all just go home.
One X user's reaction captured the mood as the outage stretched through the workday.
Mark

Why does an email outage count as news? People lose Outlook sometimes.

Mimi

Because of the scale. Downdetector reports peaked above 130,000, and the outage hit Teams, SharePoint and Copilot as well. A lot of workplaces depend on those tools at once.

Luke

Keep in mind that Downdetector counts user reports, not confirmed affected accounts. It's a useful signal, but it isn't Microsoft's own tally.

Mark

What did Microsoft say caused it?

Mimi

Failed health checks, possibly from a component on the servers that processes them. Later it said it was restarting servers that had become unresponsive.

Luke

That's a description of symptoms and a possible origin, not a confirmed root cause. The word "may" matters in the company's statement.

Mark

And the mood among workers?

Mimi

Some seemed relieved. One X user suggested everyone just go home.

Luke

That's one post. It's color, not evidence of how workers broadly reacted.

Mark

What's still unknown?

Luke

When full service returns, and why the servers failed. About 31,000 reports were still open at 8 p.m. Eastern, so the story wasn't finished.

  • Shortly after noon, inboxes across America went dark and office workers were cut off from the email that runs their days.
  • Reports on Downdetector surged past 130,000, a wave of frustration washing through offices and home screens alike.
  • Microsoft shifted its explanation from failed health checks to unresponsive servers, restarting machines and pursuing every available path to recovery.
  • The damage spread from Outlook to Teams, SharePoint and Copilot, and by evening roughly 31,000 users were still stuck, with full restoration not yet confirmed.

On a Thursday just after noon, the quiet machinery of corporate correspondence faltered across the United States, as Microsoft's Outlook stopped opening for a large share of office workers. The disruption, traced to the Exchange Online service that carries mail for Microsoft 365, lingered through the afternoon and spread to the collaborative tools that depend on it. Microsoft's own account, still incomplete, points toward servers that failed their routine self-checks and had to be restarted, and the full story of why remains for the company to tell.

Shortly after noon on Thursday, email stopped working for a large share of office workers across the United States. Outlook, the inbox that much of Corporate America depends on, refused to open for them, and for most of the afternoon it stayed that way.

Microsoft acknowledged the problem on X, saying it was investigating trouble reaching Exchange Online mailboxes through several connection methods in the Americas. The scale was visible in Downdetector figures, where reports peaked above 130,000 before easing to about 31,000 by 8:00 p.m. Eastern.

Microsoft's explanation shifted during the day. First it pointed to failed health checks, the routine tests that show whether a server is working, possibly tied to a component responsible for processing them. Later it said it was restarting servers that had become unresponsive, and it described an effort to pursue every pathway to reduce the impact.

By evening the disruption reached Outlook, SharePoint, Teams, and Copilot. Not everyone treated it as a crisis; one X user summed up the mood with a wry suggestion that everyone simply go home.

When service will be fully restored, and what caused the servers to fail, remain open questions. A full root-cause account from Microsoft is what to watch for next.

Shortly after noon on Thursday, email stopped working for a large share of office workers across the United States. Microsoft's Outlook, the inbox that much of Corporate America runs on, would not open for them, and for most of the afternoon it stayed that way.

Microsoft acknowledged the problem on X that afternoon. The company said it was investigating reports of users having trouble reaching Exchange Online mailboxes through multiple connection methods in the Americas. Exchange Online is the service that sits behind Outlook mail in Microsoft 365.

The scale showed up in the outage-tracking figures from Downdetector. Reports of Outlook problems peaked at more than 130,000 earlier in the afternoon. By 8:00 p.m. Eastern the count had fallen, but roughly 31,000 users were still reporting issues. The outage appeared to have started just after noon, so it covered much of the workday.

Microsoft's explanations changed as the day went on. An earlier update pointed to failed health checks, the routine tests that tell the system whether a server is working. The company said the failures might have come from a specific component on the affected servers that is responsible for processing those checks. Later it said it was restarting those servers because they had become unresponsive. At one point it said it was aggressively pursuing all pathways to reduce the impact.

By 8:00 p.m., Microsoft said the damage reached beyond mail. Microsoft 365 services that interact with Exchange Online and email were affected. The company listed Outlook, SharePoint, Teams, 365 and its Copilot AI tool.

Not everyone treated the outage as a crisis. CNN's Ramishah Maruf noted that many in Corporate America didn't seem to be in much of a hurry. One X user wrote, in a post that captured the mood, "no outlook, no teams.... how about we all just go home."

The reporting so far leaves open when service will be fully restored and what exactly caused the servers to fail. Microsoft has described health-check failures and unresponsive servers, but it has not yet published a full account of the root cause. That explanation, and a restoration timeline, are what to watch for next.

We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas.
— Microsoft, on X
Contattaci Domande frequenti