Microsoft 365 Outage, Day 2
Status: major-outage (single-provider origin, global scope, partial and recovering).
Microsoft 365 โ second day of disruption. Beginning around midday ET on Nov 12, users worldwide were unable to connect to Exchange Online/Outlook, Teams, SharePoint Online, OneDrive and Microsoft 365 Copilot. Microsoft attributed the connectivity errors to elevated load on part of its infrastructure across multiple regions and said there is no evidence of malicious activity. As of this report, Microsoft's business status feed still shows "Service degradation" ("Users may be unable to connect to multiple Microsoft 365 services"), with the current status reading "We remain focused on addressing residual impact and ensuring reliable service restoration." The consumer feed shows "Service degradation" for Outlook.com, OneDrive, OneNote, To Do, Teams and Microsoft 365 for the web, noting recovery is ongoing and may take time. Press coverage (Tom's Guide, BleepingComputer, CNN, ABC News) reports email delivery improving but coverage differs on how complete recovery is, and Downdetector reports were reported above 40,000 on day two. We could not independently confirm exact current user impact.
Knock-on effects at other providers (from their own status pages):
Other notes today:
No active issues reported: AWS, Google Cloud, Azure (no widespread events), Azure DevOps (page did not load usable data), Discord, Slack, Atlassian, Vercel, DigitalOcean, Groq, Cohere, Stability AI. Heroku, Stripe, ElevenLabs and Meta status pages did not return readable data, and cursor.com's status URL redirected elsewhere, so those are unchecked. No BGP, DNS or undersea-cable incidents surfaced in searches.
Sources: Microsoft 365 status (status.cloud.microsoft), Tom's Guide, BleepingComputer, CNN, ABC News, and provider status pages: cloudflarestatus.com, githubstatus.com, status.claude.com, status.openai.com, twilio, zoomstatus.com, akamaistatus.com.