Internet Status — September 1, 2026: Microsoft 365 Recovering
A large Microsoft 365 outage that began on August 31 is still working through its backlog this morning. Core internet infrastructure — global routing, DNS, and the major cloud networks — is stable, and there is no internet-wide disruption. Microsoft 365 / Exchange Online — recovering. Microsoft began investigating Exchange Online failures at about 17:30 UTC on August 31, tracked as EX1464935 and later broadened to MO1465074. Users saw delayed or failed email delivery, authentication errors, and mailbox operation failures, and the impact spread to OneDrive for Business, SharePoint Online, Microsoft Teams, Microsoft Purview, and Microsoft Defender XDR. Microsoft attributed it to a misconfiguration in a core authentication configuration shared by several internal Exchange Online services, which prevented authentication components from deploying as expected to part of its infrastructure. Downdetector logged more than 5,000 reports around the peak. As of Microsoft's update early on September 1, mailbox connectivity has largely returned to normal, while search functionality and queued email backlogs are still catching up. Our August 31 report was filed before this incident began. Details: https://www.bleepingcomputer.com/news/microsoft/microsoft-exchange-online-outage-causes-email-failures-auth-issues/ Cloudflare — three minor incidents open. HTTP errors on API calls affecting D1 and Workflows, opened 08:38 UTC today and under investigation. An incorrect HTTP/3 advertisement causing delayed or failed asset loads on R2 custom domains for some Firefox users, open since August 31. And incorrect geolocation for WARP users, open since August 27 with a fix in progress. A handful of edge locations are in partial outage or maintenance, which is normal background re-routing. Source: https://www.cloudflarestatus.com OpenAI — recovering. Elevated latency on the Responses API, identified August 31. Mitigation applied, with recovery being monitored as of 01:46 UTC. Source: https://status.openai.com Twilio — degraded on carrier routes. Voice call failures between Twilio and multiple networks in Malaysia and Thailand, SMS delivery delays to H3G United Kingdom, MMS delays and failures from AT&T to Twilio toll-free numbers, and SMS delays to C-Spire, Dish, and Telefonica El Salvador. Most are showing recovery and all are rated minor. Source: https://status.twilio.com Slack — long-running incident still open. The issue that began August 13 affecting access to historical messages on workspaces with custom data retention policies remains active. Slack says custom retention processing has been re-enabled for affected active workspaces while message, edit, and file restoration continues. Source: https://slack-status.com Operating normally: AWS, Microsoft Azure, Azure DevOps, Google Cloud, GitHub, Akamai, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere, and Stability AI. Infrastructure layer: no BGP hijacks, route leaks, submarine cable faults, or DNS root-server problems were reported in the past 24 hours. Stripe has a scheduled TWINT payment-method maintenance running until 15:00 UTC today. One gap to note: Meta's status page returned no machine-readable detail on this run, so our read on Facebook, Instagram, and WhatsApp comes from third-party reporting only. We found no credible reports of a Meta outage in the last 24 hours. Recently resolved, past 72 hours: a Google Cloud us-west1 networking incident on August 20 caused by fiber maintenance is long closed, and no further cloud-provider incidents were opened between August 29 and 31 apart from those listed above. Overall status: incidents detected. One large single-vendor SaaS outage in recovery, plus several minor provider issues. The internet itself is up.