Embargoed — hold

Ref
CM-8501
Date
November 13, 2026
Prepared by
Marcus Bennett

Outlook down for a second day as Microsoft blames 'elevated load'

Outlook entered a second day of outage Nov. 13 after 'elevated load' hit Exchange-linked services, as users mock Microsoft's vague updates and its 60,000-worker buyout plan.

Action points

  1. Outlook and Exchange-linked services went down after noon ET on Nov. 12 and were still degraded into Nov. 13.
  2. Microsoft cited 'elevated load across multiple regions' and failed server-health checks; no evidence of malicious activity.
  3. Microsoft cut ~4,800 employees in July and is offering buyouts to 60,000 workers, over 25% of its workforce.
  4. MSFT traded near $515.06 premarket, down ~1.5% from a $523 close.
  5. Microsoft is valued at nearly $4 trillion.
Microsoft’s massive Outlook outage collides with bad optics—from layoffs and buyouts to confusing updates

Monitor

Encl. AMicrosoft’s massive Outlook outage collides with bad optics—from layoffs and buyouts to confusing updates — Pexels / pixabay

Microsoft's Outlook outage stretched into a second day this morning, November 13, with millions of users worldwide still locked out of email more than 24 hours after the failures began shortly after noon ET on November 12.

Teams, which Microsoft has partially restored, and other services that interact with Exchange Online were also hit. For context: Outlook is one of the largest business email platforms on earth, so when it wobbles, a large slice of the working world's inbox wobbles with it — including government agencies, hospitals, emergency services and schools, not just corporates.

The platform's status page calls the whole affair a "service degradation." That's quite a phrase for two days of dead mailboxes at a company valued at nearly $4 trillion.

What caused it?

Nobody knows for certain yet — least of all, it seems, Microsoft.

The Microsoft 365 Status account on X posted yesterday: "We've determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors." Likely contributing. Not exactly a root cause.

A follow-up post narrowed things slightly, saying the company's "investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health." Other reports point to a possible configuration change, but that remains unverified.

The status page's current line: "Traffic is being gradually restored," with "improvements in key customer scenarios, including mailbox access and delayed email processing" — though "some users may continue to experience intermittent issues."

Microsoft has ruled out one theory explicitly: "At this time, we have no evidence of malicious activity associated with this incident," the status page states. Fast Company has reached out to the company for further comment.

What does this change for IT teams?

Practically, not much yet — there's no fix to apply, only status pages to refresh and users to placate. What practitioners actually got was a stream of updates widely judged too vague to act on. A Reddit thread on r/sysadmin speculated the foggy language means Microsoft still doesn't have a firm grip on the cause.

"Translation: We ain't got the first clue WTF is going on but it doesn't appear to be anything we have done (on purpose) and we don't know when it will be fixed," mocked Reddit user simAlity.

On X, user @esrtweet responded to one status post: "Are you fucking kidding me? Did you just say, right out in front of Goddess and everybody, that it is unpredictable when your cloud servers will stop collapsing under load? I think you did."

Are layoffs and buyouts in the frame?

The outage has collided with poor timing on the personnel front. In July, Microsoft cut around 4,800 employees. Weeks ago, it began offering buyouts to 60,000 workers — more than a quarter of its workforce — to help fund its AI infrastructure plans.

Social media has connected the dots, fair or not.

"I have no doubt there's a 60 year old engineer out there who took Microsoft's buyout offer from last month that did a bunch of undocumented work his bosses didn't know about to keep things running and could fix this in 2 minutes, but alas Microsoft needs more $$$$ for AI capex," wrote X user @OldManFay12.

"Microsoft has laid off thousands of people while pouring billions into AI. Then Outlook goes down around the world, and for 10+ hours everyone is waiting on human engineers to bring it back," noted X user @IAmSoleyman, adding: "Funny how companies keep talking about replacing people, right up until something breaks and they need people to fix it."

Whether recent departures actually contributed to the outage, or to the slow resolution, is unknown. But the optics are doing their own damage.

How has the stock reacted?

Microsoft (Nasdaq: MSFT) traded around $515.06 per share in premarket action, down roughly 1.5% from the prior close of $523. That dip may reflect the outage — or it may not. A move of a few percent is routine for big tech in a stretch when the midterm elections and the Jensen Huang Nvidia scandal have already sent the sector on a roller-coaster.

For now, the mailbox is still catching up, the status page is still hedging, and the engineers — whoever's left — are still working.

via fastcompany.com (Source)

Filed under

  • microsoft
  • microsoft-outlook
  • microsoft-365
  • service-outage
  • crisis-communication
Share this article:

More from Marcus Bennett

Marcus Bennett

Show full bio

Market editor covering regulation, policy and their impact on communications business at Comms Memo.

29 articles

Also routed

« Previous article