Global MS 365 Outage Disrupts Outlook, Teams, Copilot
IT DAILY ·
✦ AI Summary
A major connectivity outage hit MS 365 starting at 12:35 p.m. on the 12th, with the initial impact centered on the Americas, including the United States, Canada, and Latin America.
The outage spread to Outlook, Exchange Online, Teams, Copilot, and SharePoint, disrupting work at companies, public institutions, and medical organizations worldwide.
MS said the cause was a failure in automated health checks and took steps to restore some servers and reroute traffic, but did not disclose when full recovery would be completed.
BizCrushWant to follow Korean talks and live streams in real time?Try CapCrush on the web
Microsoft's cloud-based productivity software, MS 365, suffered a major access outage, according to reports from overseas media outlets such as The Guardian and MS's service status notices on the 12th. The outage began at 12:35 p.m. on the 12th, or 2:35 a.m. on the 13th in Korea time. The initial impact was centered on the Americas, including the United States, Canada, and Latin America.
About 15 minutes after its first notice, MS said a connectivity outage could affect all regions worldwide. After that, users experienced disconnects and response delays across major services.
The outage spread to Outlook, Exchange Online, Teams, Copilot, and SharePoint. As a result, companies, public institutions, and medical organizations around the world were hit by work disruptions.
MS was restoring some servers while also taking steps to distribute access traffic. However, it did not disclose when full recovery would be completed.
Reports of Outlook outages spread across multiple countries in a short time, showing a global outage pattern. According to Downdetector, the peak time for Outlook outage reports was 1:15 p.m. on the 12th, or 3:15 a.m. on the 13th in Korea time, and the peak number of reports was about 130,000. About 1 hour after the outage began, reports had come in from around 74 countries worldwide. In addition, about 30% of the initial reports between noon and 2 p.m. on the 12th, or between 2 a.m. and 4 a.m. on the 13th in Korea time, came from outside the United States.
The impact spread to medical and educational institutions, as well as MS 365 integration features for generative AI services. A hospital network in Toronto, Canada, declared Code Gray, a medical emergency, and the operations of an education authority in British Columbia were also paralyzed. The outage also spread to South America, Europe, and Asia. The MS 365 connector feature in OpenAI's ChatGPT and Anthropic's Claude was interrupted.
In its official service status notice, MS said the cause was a failure in automated health checks. The failed automated checks caused multiple servers to go down unexpectedly, concentrating the load on the remaining infrastructure. MS said it is reviewing whether a recently applied update was the cause and has temporarily suspended all deployments and configuration changes.
In a notice at 6:06 p.m. on the 12th, MS said some affected servers were operating normally and remaining stable, traffic was being rerouted through alternative paths on a segment-by-segment basis, and limited recovery had been confirmed in some regions. The MS service status page, which had at one point been inaccessible, was also restored to normal.
By 6:40 p.m. on the 12th, the number of Downdetector reports had fallen to 32,000, about one-fourth of the peak. The decline in reports indicated a gradual recovery.
Meanwhile, Cisco ThousandEyes analyzed that during the outage, internal connection resets occurred on the MS network, along with response timeouts, HTTP server errors, and significant traffic loss.
Mark Gregory, an associate professor at RMIT University in Australia, said that if some server pools drop out because of a configuration error at the network layer, requests will concentrate on the remaining servers, and that this request concentration triggers a chain reaction of overload. He said stronger pretesting environments and backup alternatives are needed.
MS 365 has seen repeated large-scale outages this year for different reasons. On January 22 this year, a North America infrastructure problem caused about 10 hours of connectivity disruption, and at the end of August, an authentication problem caused Outlook to go down for several hours, among other major outages in quick succession.
Source: IT DAILY · Kim Ho-jun
Original: https://www.itdaily.kr/news/articleView.html?idxno=242907
References
This article was produced with the help of an automated content generation algorithm.
Source: IT DAILY
View originalThis article was summarized and organized by BizCrush based on the original article from IT DAILY. For exact quotations and full details, please refer to the original article.
