Outlook Stays Down for a Second Day as Microsoft Fights Optics Storm
Outlook entered a second day of outage on November 13 after a November 12 service degradation hit Exchange Online, Teams and other Microsoft 365 services worldwide.
By Grace Kim
4 min read

What's News
- Outlook and related Microsoft 365 services went down shortly after noon ET on November 12 and were still degraded into November 13.
- Microsoft cited 'elevated load across multiple regions' and failed health checks in a component that processes server health.
- Microsoft said it has 'no evidence of malicious activity' tied to the incident.
- The company cut about 4,800 employees in July and is offering buyouts to 60,000 workers — over 25% of its workforce — to fund AI infrastructure.
- MSFT traded near $515.06 in premarket trading, down about 1.5% from the previous close of $523.
Microsoft's Outlook outage stretched into a second day on November 13, leaving millions of users worldwide without email and dragging shares of the nearly $4 trillion company down roughly 1.5% in premarket trading.
The disruption began shortly after noon ET on November 12, when users around the world reported they could not access Outlook or other Microsoft 365 services that interact with Exchange Online, including Teams. By the morning of November 13, Microsoft had restored some services, such as Teams, but Outlook remained largely offline.
For the first few hours, social media users joked the blackout was a welcome break from work. The mood soured as the hours mounted. Outlook is one of the largest business email platforms in the world, and when it goes dark, a large chunk of an employee's workflow goes with it. The damage spread well beyond corporations: government agencies, hospitals, emergency services, and schools all reported impact.
A service interruption this long is rare for a platform as critical to global communications as Outlook — especially one run by a company with nearly unlimited technical resources at its disposal.
What caused the outage?
There is no definitive answer yet. In a post on X, Microsoft's Microsoft 365 Status account stated: "We've determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors."
That explanation is not conclusive. Other reports point to a potential configuration change as the source of the issues, though that claim is also unverified. In a follow-up post, Microsoft 365 Status said the company's "investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health."
Microsoft's Service Health Status page classifies the event as a "service degradation" and confirms that multiple Microsoft 365 services "that interact with Exchange Online and email services are impacted." The page says the current status is that "Traffic is being gradually restored" and that "improvements in key customer scenarios, including mailbox access and delayed email processing" are being made. It cautions, however, that "some users may continue to experience intermittent issues."
The company has pushed back on one theory: a cyberattack. "At this time, we have no evidence of malicious activity associated with this incident," the status page states.
Why are users frustrated with Microsoft's updates?
Microsoft has communicated regularly, mainly through its Microsoft 365 Status account on X. But many users say the updates are so vague they're nearly useless. A Reddit thread in r/sysadmin speculates that the foggy language means Microsoft may still not know the exact 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 Microsoft update: "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 the layoffs and buyouts connected to the outage?
Critics have linked the outage to Microsoft's recent workforce decisions. In July, the company let go of around 4,800 employees. Just weeks ago, it began offering buyouts to 60,000 workers — more than 25% of its workforce — to help fund its massive AI infrastructure plans.
"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," criticized 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."
It is currently unknown whether recent departures contributed to the outage or to the length of the recovery.
How has MSFT stock reacted?
Microsoft shares (Nasdaq: MSFT) traded around $515.06 in premarket trading on November 13, down roughly 1.5% from the prior close of $523. Still, a few percentage points of swing is normal for big tech right now — the midterm elections and the Jensen Huang Nvidia scandal have sent tech stocks on a roller-coaster in recent weeks.
The verdict on causation is still out. But a two-day outage at the world's dominant business email platform, landing weeks after buyouts covering a quarter of its staff, is exactly the story Microsoft doesn't want attached to its AI spending spree.
Original: x.com
More from Grace Kim
Show full bio
Market editor covering people, launches and day-to-day practice in entrepreneurship, startups and venture funding at Business Bearings.
2,006 articles