Microsoft Outage Disrupts Teams, Outlook, and Azure Services Across Multiple Regions

The exact cause of the primary disruption has not been disclosed. UTC on July 23rd, routine device maintenance commenced on datacenter equipment.

3 dk okuma 14 görüntülenme
xbox outage

Microsoft faced service disruptions on Thursday affecting multiple platforms including Teams, Outlook, and Microsoft 365, while a separate maintenance error in California knocked Azure services offline for nearly five hours. Hundreds of users reported login failures beginning after 7:30 a.m., though the broader outage had substantially resolved by early afternoon with fewer than 30 reports by 2 p.m. The exact cause of the primary disruption has not been disclosed.

İçindekiler

California Azure Incident Details

In a separate incident affecting cloud infrastructure, Microsoft's West US region experienced extended downtime stemming from a maintenance operation gone wrong. At 2:44 p.m. UTC on July 23rd, routine device maintenance commenced on datacenter equipment. The procedure is designed to isolate specific network paths while maintaining redundancy through dual routes, with automated safety checks intended to verify that at least one backup remains operational.

However, a bug in the request conversion system incorrectly flagged additional devices for maintenance and removed Internet Protocol routes from more equipment than planned. This unintended change severed connectivity between the datacenter and the wide-area network, preventing traffic from entering or exiting the region. Microsoft's incident review indicates the issue initially presented as large-scale route disruption in the wide-area network before engineers traced the root cause to datacenter fiber maintenance activity. Recovery efforts began at 5:45 p.m. UTC, with full restoration completed by 7:41 p.m. UTC—spanning nearly five hours of service degradation.

Service Impact and Recovery Timeline

The primary outage affecting Teams, Outlook, and related Microsoft 365 services was resolved more quickly, with the company restoring access to most users by midday Thursday. The incidents underscore the vulnerability of cloud infrastructure to both human error and system bugs, even when multiple safeguards are theoretically in place. Microsoft joins other major cloud providers in experiencing significant outages despite redundancy measures designed to prevent such incidents.

What Microsoft services were affected by Thursday's outage?+
Microsoft 365, Teams, and Outlook experienced widespread disruption Thursday morning, preventing users from logging in. A separate incident also impacted Azure services in the West US region.
How long did the Azure California outage last?+
The Azure West US region outage lasted approximately five hours, from 2:44 p.m. UTC until 7:41 p.m. UTC on July 23rd, after engineers rolled back changes and restored network routes.
What caused the Azure outage?+
A bug in Microsoft's request conversion system incorrectly marked additional network devices for maintenance and caused Internet Protocol routes to be removed from more equipment than intended, severing connectivity between the datacenter and wide-area network.
What was the cause of the primary Microsoft outage Thursday morning?+
Microsoft has not disclosed the root cause of the Thursday morning outage affecting Teams, Outlook, and Microsoft 365. The company stated only that the disruption was under investigation.
How many users reported problems during the outages?+
Hundreds of users reported the primary outage after 7:30 a.m. Thursday morning. By 2 p.m., fewer than 30 users continued to report issues, indicating the service had largely recovered.

Bülten Aboneliği

Haftada bir, teknoloji ve dijital dünyadan seçtiklerimiz e-postanda. Spam yok, sadece içerik.

Benzer Haberler

Yorumlar

0
Henüz yorum yok. İlk yorumu sen yap!
app store'da indir