Un defecto introducido en julio, un aumento del tráfico y una reducción temporal de la capacidad de sus servidores están detrás del fallo que afectó a millones de usuarios Un defecto introducido en julio, un aumento del tráfico y una reducción temporal de la capacidad de sus servidores están detrás del fallo que afectó a millones de usuarios
La caída mundial de Microsoft del pasado jueves 12 de noviembre se debió a un defecto de software que llevaba más de tres meses presente … en sus sistemas sin ser detectado. Así lo ha explicado Charles Lamanna, vicepresidente ejecutivo de Copilot, Agentes y Plataforma de la compañía, a través de una publicación en su cuenta de X, en la que ha detallado los motivos de una interrupción que afectó a numerosos servicios de Microsoft 365.
Según Lamanna, el incidente se produjo por la coincidencia de tres factores. El primero fue un fallo introducido en una actualización específica para los servidores de la infraestructura de red de Microsoft 365, cuyo despliegue comenzó en julio. «Durante más de tres meses, el cambio se implementó en todo el mundo sin impacto», reconoce el directivo. El defecto provocaba que los servidores se saturasen y dejaran de responder bajo determinadas condiciones de carga.
A este problema se sumaron un aumento del tráfico en la infraestructura principal, después de que Teams realizase un cambio de red unas quince horas antes de la caída, y la reducción temporal de casi el 14% de la capacidad de los servidores, que permanecían fuera de servicio por una incidencia independiente del día anterior.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).The final Post-Incident Review (PIR) will provide more details later this week.
— Charles Lamanna (@clamanna)
La combinación de estos elementos desencadenó un fallo en cadena. Cuando algunos servidores dejaron de responder, el sistema redirigió automáticamente el tráfico hacia los que seguían operativos, lo que incrementó todavía más su carga de trabajo. «En menos de dos horas, el defecto previamente desconocido se encontró en toda nuestra flota», explica Lamanna. En el momento más crítico, más del 80% de los servidores afectados por la incidencia no respondía.
La recuperación también se complicó porque los equipos que volvían a funcionar recibían inmediatamente las peticiones acumuladas y volvían a saturarse. Para solucionar el problema, los ingenieros desarrollaron una actualización que devolvía el código a una versión anterior y la aplicaron progresivamente a los servidores.
Lamanna ha pedido disculpas por las consecuencias de la interrupción y ha avanzado que Microsoft publicará una revisión completa del incidente durante esta semana, con más detalles sobre lo sucedido y las medidas que adoptará para evitar que vuelva a repetirse.
RSS de noticias de tecnologia
