Orange's 2026 network outage revealed critical flaws in modern infrastructure, emphasizing the need for robust resilience strategies and real-world crisis simulations.
Mobile network interruption in Orange
On October 21, 2026, Orange experienced a mobile network interruption that disrupted communications for part of its subscribers. The operator told 01net that a faulty piece of equipment in its new network core was responsible, and it ruled out a cyberattack, distinguishing this from a separate cyberattack detected earlier in 2025.Network core vs. radio access network
The incident highlights the complexity of modern network architectures, where the radio access network and the network core serve different functions. The network core handles tasks like terminal registration and subscriber authentication, while the radio access network manages the radio link that connects devices to the network.Resilience engineering and redundancy
Resilience engineering emphasizes understanding dependencies and recovery mechanisms. Redundancy must be designed to survive common causes, and geographic separation may not be enough if logical dependencies remain. CIOs must clearly document what each redundancy covers and ensure distributed systems are not vulnerable to errors from central orchestrators.Capacity after failover
The capacity available after a failover must be carefully considered, as the nominal capacity may become insufficient during the transition due to session reconstruction and increased requests. Restarting components does not always end an incident, as customers may retry connections, leading to a surge in demand that can hinder recovery efforts.Recovery strategies and protections
Recovery strategies must limit the actual demand accepted during an outage. Protections include mechanisms like limited connection attempts, increasing delays with random dispersion, and admission control. Emergency accesses must be protected, limited, logged, and regularly checked, with alternatives to SMS analyzed for availability.Recovery objectives and incident management
Recovery objectives must distinguish between technical restoration and business resumption, using RTO (Recovery Time Objective) and RPO (Recovery Point Objective) to define acceptable time frames and data loss. Connectivity outages can lead to pending transactions and delayed processing, requiring specific reconciliation processes and assigned responsibilities.Supplier contracts and testing
Supplier contracts must specify the information available during an incident, and CIOs must align potential outage durations with business needs. Testing failovers with affected users is essential, as systems like cash registers and contact centers have different recovery priorities and requirements.Learning from fictional scenarios
The incident also highlights the need to turn fictional scenarios, such as those in the series Zero Day, into measurable exercises. These can help test crisis management strategies and ensure teams are prepared. The incident also emphasizes the importance of analyzing the chronology of events with recent changes, security logs, traffic, and integrity alerts to identify the root cause.
