TL;DR
A Kubernetes crash caused a major Azure outage, impacting Teams and Minecraft in EMEA, with Microsoft working to restore services.
Key Points
Highlight key points with color coding based on sentiment (positive, neutral, negative).A significant outage affected Microsoft's Azure services due to a crash in Kubernetes instances, leading to a 30% capacity loss of Azure Front Door instances, particularly impacting regions in Europe, the Middle East, and Africa.
Microsoft ruled out a faulty update as the cause of the outage and focused on restarting the affected Kubernetes instances to restore service functionality.
The outage disrupted several services, including Microsoft Teams and Minecraft, causing users to experience issues such as being unable to log in or access certain services.
Microsoft's recovery efforts included restarting Kubernetes instances and initiating a failover for the Microsoft 365 Portal service to expedite the restoration process, with most services reportedly restored.
Despite the recovery efforts, some users continued to experience intermittent delays or timeouts, particularly when accessing the Azure Portal and Microsoft Entra.
Key Numbers
Present key numerics and statistics in a minimalist format.The capacity loss of Azure Front Door instances during the outage.
The time when problems were noted during the Microsoft Azure outage.
The percentage of impacted resources that were recovered at one point during the outage.
The percentage of the Azure Front Door service that was restored during the outage.
The number of Azure Front Door environments affected in Europe and Africa regions.
Stakeholder Relationships
An interactive diagram mapping entities directly or indirectly involved in this news. Drag nodes to rearrange them, and hover over lines to see relationship details.Organizations
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.Responsible for managing and resolving the Azure service outage.
Tools
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.Involved in the crash that led to the Azure service outage.
Affected during the Azure service outage.
Events
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.Caused by a crash in Kubernetes instances, affecting services like Microsoft Teams and Minecraft.
Industries
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.Directly impacted by the Azure service outage.
Timeline of Events
Timeline of key events and milestones.Microsoft detected problems with Azure services, noting a significant capacity loss of about 30% of Azure Front Door instances.
Minecraft gamers began reporting issues connecting to servers.
Fortnite users reported problems, coinciding with scheduled maintenance.
Hundreds of people reported an outage with Microsoft 365 services.
Microsoft announced it was investigating issues with Microsoft 365 services.
Microsoft confirmed issues with Azure Front Door affecting access to Microsoft 365 services.
Microsoft was investigating outages in Microsoft 365 and Azure services.
Users reported issues with Minecraft authentication.
Microsoft identified an issue within the Azure Front Door service causing access issues.
Minecraft and Fortnite users reacted to ongoing issues.
Microsoft provided an update on Azure issues, expecting full mitigation within 90 minutes.
Microsoft issued an update on Azure problems, indicating recovery efforts.
Microsoft 365 issues appeared to be resolving.
Azure Front Door service was 98% restored.
Azure users were warned of potential intermittent delays.
Microsoft confirmed the Azure Front Door mitigation was complete, with services fully recovered.
Microsoft network health status indicated all services were operational.
Microsoft engineers continued efforts to resolve Azure issues, with 96% of resources recovered.
Some Microsoft 365 users still experienced problems despite the apparent fix.
Users in various regions continued experiencing issues with Azure Front Door.
Long-form summary
Microsoft faced a significant outage impacting its Azure services due to a crash in Kubernetes instances. This incident resulted in a 30% capacity loss of Azure Front Door instances, affecting regions in Europe, the Middle East, and Africa. The outage disrupted services like Microsoft Teams and Minecraft, causing widespread issues for users trying to access these platforms. Microsoft ruled out a faulty update as the cause and concentrated on restarting the affected Kubernetes instances to restore functionality.
Recovery efforts were underway, with Microsoft engineers working diligently to bring the Azure Front Door instances back online. The company also initiated a failover for the Microsoft 365 Portal service to expedite the restoration process. Despite these efforts, some users continued to experience intermittent delays or timeouts. The outage also affected users' ability to cancel Game Pass subscriptions due to login issues.
Microsoft has not provided detailed information on why the Kubernetes instances crashed or why the recovery was not automatic. However, the company reported that the vast majority of impacted resources had been restored, and services were gradually returning to normal.
Enjoyed it?
Get weekly updates delivered straight to your inbox, it only takes 3 seconds!Subscribe to our weekly newsletter Kaptain to receive similar updates for free!
Give a Pawfive to this post!
Share with your friends and followers
Start blogging about your favorite technologies, reach more readers and earn rewards!
Join other developers and claim your FAUN.dev() account now!
FAUN.dev
FAUN.dev is a developer-first platform built with a simple goal: help engineers stay sharp without wasting their time.
Kaptain #Kubernetes
FAUN.dev
@kaptain
