Scrutica
Power
Supply Chain
Not yet available
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by Yotta Data Services; any BIS Entity List exposure is walked through the canonical org graph rather than asserted at the facility row.
Capacity, ownership chain, and supply-chain position for Yotta D2, including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.
As of 2026-07-18
Operator (or owner of record) per the Scrutica facility row.
Ownership chain not yet documented in the available data (licensed corporate-ownership database, licensed supply-chain database, SEC filings, LEI registry; as of 2026-07-18). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
Description
Yotta D2 is the announced 60 MW second data center at Yotta's Greater Noida hyperscale campus (campus scalable to 250 MW), sibling to the operational 30 MW Yotta D1. Announced 2026-02-18 as the primary deployment site for Yotta's NVIDIA HGX B300 supercluster: 'Yotta Data Services today announced it will deploy 20,736 liquid-cooled NVIDIA Blackwell Ultra GPUs, forming one of Asia's largest AI superclusters. The deployment represents an investment exceeding $2 billion and is expected to go live by August 2026' — with the supercluster 'deployed at Yotta's 60 MW D2 data center at Greater Noida hyperscale campus (scalable to 250 MW), with additional capacity from Navi Mumbai campus, scalable to 2 GW.' The release also announces a four-year, over-$1B engagement with NVIDIA to establish one of APAC's largest NVIDIA DGX Cloud clusters within the supercluster.
Timeline
Announced
Feb 18, 2026
Notes
STAGED — NOT YET INGESTED (Task #40 staging pass, 2026-07-18; closes the Yotta D2 gap identified in the 2026-07-17 scope doc — confirmed via direct DB query 2026-07-18 that no fac-yotta-d2* row exists in prod). PER-FIELD SOURCE ATTRIBUTION: every populated value (60 MW, campus-scalable-to-250-MW, announced_date 2026-02-18 dateline 'New Delhi, February 18, 2026', supercluster context) is verbatim in Yotta's own press release at source_url (tier 1, operator disclosure, fetched 2026-07-18). total_gpu_count DELIBERATELY NULL: the 20,736-GPU supercluster explicitly spans D2 PLUS 'additional capacity from Navi Mumbai campus' — the release does not decompose the count per site, so attributing 20,736 (or any portion) to D2 would be false precision; the count lives in description as supercluster-level context only. expected_operational_date null: 'expected to go live by August 2026' attaches to the SUPERCLUSTER deployment, not to D2 building commissioning, and is month-precision. status 'announced': the release does not state D2's construction status. Campus corroboration (secondary, same operator): Yotta's colocation listing page https://colocation.yotta.com/data-center/ (fetched 2026-07-18) describes the Greater Noida campus as '6 interconnected data center buildings offering 30,000 racks capacity powered by more than 250 MW of power' — consistent with the release's 250 MW campus ceiling. Coordinates null pending facility-level disclosure (same-campus-as-D1 rule, mirroring the fac-yotta-nm2 precedent). STANDING INSTRUCTION honored: the '75MW/36,000 GB300' NM2 figure circulating in tier-2/3 paraphrase was NOT adopted anywhere; it is unrelated to this D2 record. [sovereign-staged-2026-07-18]
India (IN)
Wassenaar participant since 2017; operates the Special Chemicals, Organisms, Materials, Equipment and Technologies (SCOMET) list under the Foreign Trade (Development and Regulation) Act.
Regimes: Indian SCOMET list authority
Established via: Yotta Data Services
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-18. 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 a licensed corporate-ownership database’s deal records (M&A, buyout, divestiture, asset sale, JV formation); 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. The licensed fund/LP database’s LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for Yotta D2starts 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 > licensed corporate-ownership database > licensed supply-chain database > BIS / Federal Register > licensed affiliate graph). 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 (licensed corporate-ownership database): 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 the database'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 licensed-database 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-07-18. Walk depth observed: 1 hop. Sources combined: Scrutica facility record + licensed corporate-ownership database + SEC CIK cross-reference + LEI registry + (where applicable) licensed supply-chain database + Federal Register designation closures. The licensed databases are held under subscription and not redistributed; per-hop labels name no vendor.
Yotta NM1
Navi Mumbai, Maharashtra, IN