Summary
- The available summary of BEA-RI’s investigation places electrical securing at 02:30, alongside deployment of water-based firefighting measures. That is a response milestone, not a finding about what ignited the fire. BEA-RI report summary
- A written procedure, an installed change and a witnessed test establish different things. Assessing emergency readiness requires distinguishing them, rather than treating an announced remedy as demonstrated capability.
What the 02:30 milestone establishes
At 02:30 on 10 March 2021, according to the available summary of BEA-RI’s investigation, the OVH Strasbourg site was electrically secured and water-based firefighting measures were deployed. The same account describes SBG2 as fully engulfed at that time, with fire spreading towards adjacent buildings. BEA-RI’s report, MTE-BEARI-2022-005, was issued in May 2022; the fire and the investigation report belong to different dates. BEA-RI investigation
That chronology matters without answering every causal question. It does not establish that no firefighting occurred earlier. Nor does it quantify how much time a different electrical-isolation arrangement would have saved, or prove that earlier isolation would have prevented SBG2’s destruction. Those stronger conclusions would require evidence beyond a single reported milestone.
In its reporting of 15 June 2022, W.Media said the fire destroyed SBG2 and damaged servers in adjacent buildings. It also reported that the precise cause of the fire had not been conclusively determined. The distinction is important: uncertainty about ignition does not make the response arrangements irrelevant, but findings about the response cannot settle the ignition question. W.Media’s account
This retrospective relies on summaries of the technical investigation and W.Media’s reporting. The full investigation text and page-level quotations have not been independently verified for this article. The evidence supports a bounded examination of emergency control, not a complete reconstruction of the incident.
A decision is not yet an executable response
The report summary identifies the absence of an emergency electrical-isolation procedure and highlights the need to isolate a datacenter from the general electricity network without waiting for external intervention. That is narrower than a claim that all emergency planning was absent. It also does not identify, in the material examined here, the full chain of people who could request, authorise, execute and confirm isolation. BEA-RI’s reported findings
W.Media separately reported that the Bas-Rhin fire service had identified a lack of automatic extinguishing and a delay in electrical cutoff as problems that complicated firefighting in the power room. This is W.Media’s account of the fire-service findings; it should not be mistaken for an independently inspected fire-service report or a legal determination. W.Media on the response difficulties
The operational lesson is a distinction between controls. Detection identifies a need to act. Electrical securing concerns the conditions under which the intended response can proceed. An alarm, an escalation call, an authorised decision and confirmation of a safe electrical state are not interchangeable evidence.
Nor is external involvement automatically evidence of fault. A competent assessment would need to establish whether that involvement was technically necessary, required for safety or governed by another constraint. The relevant accountability question is how the dependency was designed, understood and exercised—not whether an outside organisation can be blamed by inference.
For operators and customers examining a facility’s arrangements, four questions follow:
- Authority: Which roles may request and authorise the relevant emergency action, including outside normal working hours?
- Capability: What can authorised personnel actually accomplish under the conditions covered by the emergency plan?
- Dependency: Which actions depend on another organisation, and how are the handoff and confirmation recorded?
- Demonstration: What exercise or test shows the arrangement working, and what exceptions remained unresolved?
These are assurance questions, not instructions for manipulating electrical equipment. Procedures and tests belong to competent, authorised personnel coordinating with emergency services.
What would count as evidence of improvement?
A recommendation establishes that a change was proposed. A management announcement establishes that a change was described or promised. Neither, by itself, demonstrates that the relevant equipment, authority, access and coordination work together.
A more persuasive record would identify the dated arrangement and its scope, allocate responsibilities, and include a test or exercise describing participants, conditions, results and exceptions. Where a test uncovered a deficiency, evidence of correction and retesting would answer a different—and more useful—question than a statement that the project was complete.
The sources examined here do not establish whether OVH has since installed, tested or maintained such measures. Current remediation status therefore remains unverified in this account. That is not evidence that no corrective work occurred, and historical findings should not be projected onto every present-day OVH facility.
Physical safety also cannot stand in for every form of customer recovery. Containing a fire, restoring a service, recovering data and compensating a customer answer different questions. An improvement in one does not establish the others; this article makes no finding about individual customers’ backup obligations, recovery results or compensation rights.
For corporate reference, see the OVH SAS directory entry. The incident reporting uses OVH or OVHcloud. Those names do not, by themselves, establish the exact legal entity’s incident-specific operational or contractual responsibilities.
The bounded conclusion is that emergency electrical isolation deserves its own evidence of readiness. The historical account raises that question clearly; it does not supply a verdict on the adequacy of today’s arrangements.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
