“We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions. Further updates can be found at MO1550821 in the Microsoft 365 admin center.”
The video below opens with this update. The rest of the report was recorded earlier, and its status card is labeled as of 8:02 p.m. PT, Nov. 12.
A Microsoft 365 outage that began Thursday morning Pacific Time disrupted Outlook and Exchange Online around the world. Microsoft first described the problem as mailbox access “in the Americas,” then said the issue “may affect Microsoft 365 service connectivity for users in any region.” Independent outage tracker Downdetector said reports reached 74 countries and territories in about an hour, and that nearly 3 in 10 reports between 17:00 and 18:55 UTC came from outside the United States. Those figures are Downdetector’s user reports, not an official Microsoft count.
Who saw it first
These are reported timings, converted to Pacific Time, not a claim of a single official “patient zero.” The technical incident, by Microsoft’s later start time and by ABC News Australia’s written 3 a.m. AEDT figure, was underway around 8:00–8:17 a.m. PT, about 90 minutes before Microsoft’s first public post, which was still scoped to the Americas.
Time (PT)
What was reported
Source
just after 8:00 a.m.
ABC News (Australia) wrote that issues began affecting Australians “just after 3AM AEDT.” (On camera, reporter Julia Andre said it started “before 6am,” a less precise figure than the written report.)
Downdetector also said Microsoft’s outage reports reached 74 countries and territories in about an hour, and that between 17:00 and 18:55 UTC nearly 3 in 10 reports came from outside the United States. It counts a country once reports reach ten times normal and at least 20 in five minutes. It did not publish a full public list of all 74 in that post.
International reach
1
Worldwide
Microsoft said users in any region could be affected
After first describing the problem in the Americas, Microsoft said at 10:07 a.m. PT that it “may affect Microsoft 365 service connectivity for users in any region,” and that it was redistributing connection traffic across its “broader worldwide infrastructure.” Official Azure status continued to list no Azure issues. This is a Microsoft 365 / Exchange Online incident (EX1550543 and MO1550821), not a confirmed Azure outage.
2
Australia
Business and government “brought to a standstill,” ABC News reported
ABC News said Australian businesses, government agencies and other organizations reported being brought to a standstill, and that Downdetector Australia recorded more than 4,400 reports of problems with Outlook by 8:20 a.m. local time. Forbes Australia, citing AAP, reported that Service NSW said some transactions at its service centres and call centres were unavailable, and that NSW Parliament, the ACT and NT governments, local councils and Queensland Health were also hit. Australia’s cyber security coordinator, Lieutenant General Michelle McGuinness, was looking into the issue, a Home Affairs spokesperson said.
3
Asia-Pacific, U.K., Canada
Named reporting in Singapore, Japan, India, New Zealand, the U.K. and Canada
Channel News Asia said Downdetector recorded 250 reports for Outlook in Singapore at 7:05 a.m. Friday, and 152 for Microsoft 365. The BBC said users around the world, including the United States, Japan and Singapore, reported disruptions. Downdetector documented tenfold jumps in the United Kingdom, India and New Zealand. CBC News and Global News covered the outage in Canada, which was included in Microsoft’s first “Americas” notice. Microsoft’s “any region” wording covers the possibility of impact elsewhere; it is not a country-by-country confirmation.
No indication of a cyber-attack, officials said
4
A Microsoft spokesperson told The Guardian the company “had no indication of a cyber-attack.” The BBC said it understood there was no indication the outage was caused by a cyber-attack. Australia’s Home Affairs Minister, Tony Burke, said on 10 News that he had been briefed by Microsoft officials in Australia and by the cyber security coordinator. Relaying that briefing, Burke said: they “do not believe they are dealing with a cyber event,” they “don’t believe they are dealing with a cyber attack,” and they believe they are dealing with something “similar to what we saw with respect to CrowdStrike where there is an update that has gone awry.” Those are official and attributed statements, not an independent finding by this site. Social-media claims of a hack remain unverified and are not treated as evidence.
What Microsoft says happened
5
Microsoft has not issued a finished root-cause report. Its account evolved through the day. It first described elevated load, then said the load was not from a traffic spike but from servers becoming “unexpectedly unavailable.” It later said servers were failing automated health checks, and that “a core process on affected servers is becoming overwhelmed, causing capacity loss.” Servers returned to service, it said, “can become unresponsive again once they receive traffic.” Later Service Health page language, as quoted by XDA Developers (updated 5:22 p.m. PT) and independently reported by Technobezz, said: “a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests,” and that Microsoft had “begun reverting a recent network configuration change that correlates with the start of impact.” That later wording came after a 12:19 p.m. PT official post saying Microsoft had “not identified any recent change correlated with the start of impact.” That is an evolution in Microsoft’s own account.
Expert analysis and independent monitors
Analysis, not Microsoft’s finding. The points below are telemetry or outside expert views. Microsoft has not confirmed a BGP failure or a finished cause.
6
ThousandEyes
Packet loss inside Microsoft’s network
Independent network monitor ThousandEyes said it observed global Microsoft 365 availability issues beginning around 17:30 UTC (about 9:30 a.m. PT) and, in a 7:00 p.m. PT update, that “significant packet loss persists within Microsoft’s network.” Connection attempts to Outlook were still timing out as of 03:00 UTC Nov. 13, ThousandEyes said. This is telemetry, not a Microsoft confirmation of cause. No public incident write-up was found from Cloudflare Radar, Kentik or Catchpoint at the time the video was locked.
7
RMIT / The Register
A likely misconfiguration, one expert said
Mark Gregory, an associate professor at RMIT University, told ABC News a misconfiguration was likely, “either in what we call BGP … or another network configuration problem.” That is his analysis; Microsoft has not confirmed a BGP failure. The Register noted that Microsoft’s early posts said it had not identified a triggering change, while the Service Health page later discussed reverting recent configuration updates.
XDA Developers and Technobezz — Service Health page wording on a secure-connection process and a reverted network configuration change
The Register — Service Health quotations and the evolution of Microsoft’s account
NBC News — U.S. video report used in the package
Reporting checked against Microsoft’s official @MSFT365Status posts and public status pages, ABC News (Australia), 10 News, Downdetector, ThousandEyes, The Guardian, the BBC, Channel News Asia, Forbes Australia / AAP, CBC, Global News, XDA Developers, Technobezz, The Register and NBC News. The 74-country figure and tenfold-jump times are Downdetector’s, not Microsoft’s. Expert remarks and ThousandEyes telemetry are labeled as analysis or independent monitoring, not as Microsoft’s root cause. Official language describes a Microsoft 365 / Exchange Online incident, not an Azure outage and not a confirmed cyber-attack. The video status card is stamped as of 8:02 p.m. PT; the latest-status note on this page is as of 8:45 p.m. PT. Music: Steve’s Bodywork and PianoEnd. VoteWatch • Rio Dell Times • Thursday, November 12, 2026.