Downdetector recorded an Outlook outage on August 31, 2026, with more than 2,500 user reports tied to Microsoft services. The report spike pointed to a real customer-facing problem for some users, even as Microsoft’s Service Health page still listed its products as operational.
Microsoft 365 and Microsoft Store
Downdetector also logged reports for Microsoft 365 and Microsoft Store. That puts the issue beyond a single app and into a wider service pattern that affected multiple parts of Microsoft’s consumer and productivity stack.
The practical takeaway for users was simple: if Outlook failed, the reports suggested they were not alone. A problem showing up across Microsoft 365, Microsoft Store, and Outlook usually means the complaint volume is broad enough to warrant attention rather than a one-off local glitch.
Service Health page vs reports
The mismatch matters because Microsoft’s official Service Health page and service status page still showed its products as operational. That left two live pictures of the same moment: user reports climbing past 2,500 while Microsoft’s own status view did not show a widespread outage.
Microsoft 365 also had several active service incidents listed through Microsoft’s service communication data on August 31, 2026. For affected users, that means the first check should be whether their problem is isolated to Outlook or tied to a broader Microsoft 365 incident already reflected in Microsoft’s own service communications.
Which Microsoft next
The immediate next step is to watch Service Health and service communication data for changes. If the reports keep rising while the status page stays steady, the gap itself becomes the story, because it signals that user experience and official status are not moving in sync.
