Technology

Outlook Down for Thousands While Microsoft’s Status Page Stayed Green

The third Outlook failure in two days — and the one Microsoft's status page never showed.

Microsoft’s public status page said all products were operational on Thursday evening. At the same time, Outlook users in Britain were reporting that they could not open their inboxes.

“Failed to fetch” greeted users loading Outlook on the web, and where the page did load, inboxes could appear blank and emails refused to send. Reports of Outlook down began just after noon Eastern time in the United States. By 12:55 p.m. ET, 22,323 people had reported problems with Microsoft 365, and Outlook itself was just short of 83,000 reports just before 1 p.m. ET. In Britain the rise came at 5:20 p.m., with more than 3,300 reports in 20 minutes. Teams drew about 2,000 reports and Copilot about 4,400 in the same stretch, according to the outage tracker Downdetector.

EX1550543 is the code Microsoft gave the outage. It appeared at 5:54 p.m. UTC on the company’s 365 Status account, attached to a post saying Microsoft was investigating reports of users unable to reach Exchange Online mailboxes “through multiple connection methods in the Americas”. The post gave no cause for the outage. The post said “in the Americas”. The outage was already in Britain. Metro quoted a further post from the same account saying the issue “may affect Microsoft 365 service connectivity for users in any region”. An earlier post, at 3:40 p.m. UTC, had reported trouble with Teams in North America under the code TM1550488, and USA TODAY reported that Microsoft said in the same thread the Teams issue was resolved around noon Eastern.

On Microsoft’s support forum, a support specialist answering a user who could not connect quoted the service status directly: the company was still addressing “persistent impact on the Outlook web service” and investigating delays in the mail queues. A second thread listed the affected ways in: Outlook on the web, the desktop client, REST and Exchange ActiveSync, with mail transport delays on top. Both threads said Microsoft would spend a period of “extended monitoring” before calling the incident resolved.

While the outage was under way, the admin-center incident EX1550543 was live and collecting reports, the public status page said everything was operational, and the support forum admitted impact that was still there. Downdetector showed a spike running since 12:27 p.m. Eastern. UptimeRobot recorded no incidents at all, and one tracker logged zero reports in 24 hours.

Thursday was the third Outlook failure in two days. On Wednesday, Microsoft’s own spam rules blocked legitimate mail from reaching Outlook.com, Hotmail and Live addresses, and the company rolled the change back. Microsoft said the mail flow had been restored and pointed customers to incident EX1545193; its shares slipped more than 2% that afternoon. The same day brought news of a different break: the October Windows Server updates had stopped some on-premises Exchange servers signing users into Outlook and delivering their mail, because of a new limit on the memory the Endpoint Mapper uses. The fix arrived with November’s Patch Tuesday updates, KB5131080 and KB5131090, and administrators who could not patch at once were told to edit a registry key and reboot.

StatusGator counts 16 Microsoft 365 apps outages since January 2025. Three of this year’s majors — January 22, September 9 and September 17 — are all marked “Officially acknowledged: No”, and the September 9 entry says the status page “did not reflect an acknowledged outage in that window”. The August 31 incident ran for three days under the code MO1465074, rooted in a shared authentication configuration, with Downdetector reports past 5,000 within hours and a fresh spike on the third morning. A January incident affecting Outlook, Defender and Purview pushed Downdetector reports past 15,000 at its peak.

By Thursday evening, a thread on Reddit titled “Can’t connect to Outlook” had 137 comments. The thread’s author, writing from Britain, said: “I can’t sign in at all on any Web browsers.” His wife had called from work thinking someone had got into her email. He had changed her password, he wrote, “but obviously now I can’t sign in to it because the page won’t load.” Another user, in capitals, wanted to know why the status said resolved: “WHY THE STATUS SAYS RESOLVED REDITT STOP LYINGH”. A third wrote that she and a coworker had been complaining they could not access Outlook, then found the thread while waiting for the page to load: “Thank you for making us realize we aren’t crazy!” A fourth reported the outage had reached his workplace: “Down at an enterprise level too… can’t access it at my job lol”.

The users in the thread asked whether it was down for everyone, whether their accounts had been hacked, whether they were imagining it. Microsoft’s posts gave the fault a code, EX1550543, and a region, the Americas, and a monitoring period. No Microsoft post answered those questions. The thread did, and so did Downdetector. One user in the thread pointed others to Downdetector instead.

In July 2025, Outlook and Hotmail were down worldwide for more than a day, with users told their licences were not valid. Microsoft declared that one resolved on X, under EX1112414, while its own service-health portal said everything was up and running and users were still locked out.

The Exchange Online post had drawn 372 replies by the evening. Mail sent during the outage may also arrive late: Microsoft’s support forum said it was investigating delays in the mail queues.