Scrutica
Supply Chain
Not yet available
Facility-level telemetry including power capacity, hardware deployments, supplier relationships, and downstream dependencies. Linked to OVHcloud with cross-referenced BIS Entity List matches.
Detailed intelligence on OVHcloud SBG-2 (decommissioned). Operational capacity and ownership structure are mapped to determine the facility's strategic position within the global AI supply chain (including its exposure to relevant export control restrictions).
As of 2026-05-16
Direct operator or owner of this facility per the Scrutica facility record.
Ownership chain not yet documented in the available data (PitchBook affiliate graph, FactSet supply graph, SEC filings, LEI registry; as of 2026-05-16). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
France
Description
SBG-2, Strasbourg building destroyed in the 10 March 2021 fire. Not rebuilt. The fire was a primary trigger for OVHcloud's subsequent "hyper-resilience plan" referenced in URD §1.4.1 (page 15): "the Group expects to reduce one-off investments (hyper-resilience plan, IPv4 purchases and improvement of inventories linked to supply chain tensions) between now and 2026". Current Strasbourg operational footprint per OVHcloud's VMS status page is SBG-3 and SBG-5 only.
Notes
Decommissioned status anchored to OVHcloud post-incident communications + URD hyper-resilience-plan reference + absence of SBG-2 from current VMS status page (https://vms.status-ovhcloud.com/). SBG-1 and SBG-4 are NOT included in this ingest — their post-fire status is not tier-1-verified from currently-available primary sources (DQP §5).
Service des biens à double usage (SBDU) administers EU Regulation 2021/821 and the French dual-use code.
Regimes: Wassenaar Arrangement; EU Dual-Use Regulation 2021/821; EU Delegated Regulation 2025/2189
Established via: OVHcloud
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-05-16. Cascade closures evaluated: 0.
No ownership-change events documented in the available data for any entity in this chain over the last 5 years. Events draw from PitchBook deal records (M&A, buyout, divestiture, asset sale, JV formation); PitchBook coverage is strongest for private US/EU transactions and partial for state-owned-enterprise restructurings or non-Western private deals. Subsequent ingestion runs may add events here.
No documented sovereign or state-linked LP investment touches any entity in this chain. PitchBook LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for OVHcloud SBG-2 (decommissioned)starts at the operator org id (or owner org id when no operator is recorded) and climbs upward through the unified affiliate graph, normalized to trace child-to-parent relationships. At each hop, the highest-authority parent edge wins (priority ordering: SEC EDGAR / 10-K / LEI registry > FactSet Workstation / Revere > Compustat > BIS / Federal Register > PitchBook). Confidence and recency break ties.
The walk terminates on (a) a node with a public-filing-grade ancestor edge — a SEC filer, an LEI-registered listed entity, or a 10-K-disclosed parent — (b) a government entity, (c) a 10-hop limit, or (d) a detected cycle. When termination is not at a public filer or government, the panel labels the chain's end-state as opaque beyond that point. Opacity is reported, never implied.
Per-source confidence (PitchBook): HIGH for Parent / Subsidiary edges; MEDIUM for JV and AFFILIATE edges. Known limitations: (1) shell companies with undisclosed principals terminate the public-record walk; (2) recent transactions reach the panel after PitchBook's weekly refresh; (3) cross-jurisdiction private holding structures may carry intermediate hops that are not in any ingested source. Each row carries an edge-level as of date so freshness is auditable per hop.
Two further caveats are inherent to how the walker and the underlying data compose. The walker selects a single highest-authority parent per hop, so JV or multi-parent ownership structures collapse to one displayed path; alternate parents exist in the ingested sources but are not surfaced on this card. And some PitchBook edges encode parent-of relations against entity-resolved stub IDs whose display name reflects a sub-entity (a business unit, an acquired-then-renamed line) rather than the canonical parent — when a chain reads structurally surprising, the per-row source citation is the authoritative reference, not the chain's narrative shape.
Computed at: 2026-05-16. Walk depth observed: 1 hop. Sources combined: Scrutica facility record + PitchBook affiliate graph + SEC CIK cross-reference + LEI registry + (where applicable) FactSet Revere supply-chain graph + Federal Register designation closures.
OVHcloud ERI-1
Erith, United Kingdom