Skip to main content

Corrections

Selected corrections

Published erratumNumerical correctionName correction
Published erratumNumerical correctionName correction
Chart key and correction counts
64

corrections, 2026-04 to 2026-10.

1 · 12

Corrections per day. Circle area is proportional to the count below 13; at that count or above, the circle size is fixed and the count is printed.

30

published errata: an earlier statement and its corrected interpretation.

33

numerical corrections: a revised or withdrawn numerical value.

1

name correction: an organization or facility name checked against its own filing or website.

0

ownership-event corrections: a description of an ownership transaction corrected against a filing.

Each circle groups corrections of one kind made on the same day. Within each kind, vertical separation prevents overlaps. Select a circle to open the first of its entries below.

The register

Further data updates appear in the Record.

Correction

Disclosure posture: parent-reporting filings attributed to the wrong companies

Previously

The Disclosure view of the Companies register listed 68 companies linked to tracked facilities, each with the reason its LEI record gives for reporting no consolidating parent, a link to that record and the company’s sites and capacity; its totals counted 491 declaring organisations. Each of the 68 company records linked to its row. For 24 of the 68 the LEI, and so the filing, belonged to another legal entity: University of Oxford showed the filing of Swiss Friends of Oxford University (Zug, Switzerland), Together AI that of TOGETHER (Perros-Guirec, France), Crusoe that of CRUSOE LIMITED (Gibraltar, lapsed since 9 April 2022), Orange that of a Marseille company named ORANGE whose registration is retired, and Princeton Digital Group that of another company in its group. Expedient’s LEI could not be tied to Expedient either way. The register labelled filings in the non-public class “Declines to name its parent”. The participation page sent, with each site it lists, whether the site’s operator and holders had filed such a reason, though it printed none of it. The Huawei Technologies and Microsoft dossiers described their non-consolidating declaration as control by an entity that does not consolidate the company’s accounts, and the visibility methodology said organisations are never matched by name alone and that corporate form is never stripped as noise.

Correction

The register’s rows and totals are withdrawn and its page says why; company records no longer link to it, and the participation page no longer reads it. The 68 LEIs were read against GLEIF’s records on 24 October 2026: 22 belong to a different legal entity and two to another company in the same group; one could not be tied to its company either way. Of the 43 that belong to the company named, 13 are on registrations GLEIF lists as lapsed or retired. The other 423 declaring organisations, which have no tracked site, were not checked. Each filing’s reason code is the one GLEIF holds for its LEI today. The posture classes and the methodology now use GLEIF’s definitions: a non-public filing states that the parent “relationship information must not be disclosed publicly”, and a non-consolidating one that the entity “is controlled by legal entities not subject to preparing consolidated financial statements”. The methodology’s identity note now says that a declaration reaches an organisation through the LEI on its record, and that the canonical identity map merges some records by normalised name and folds some subsidiaries into their groups.

Numerical correctionRecord revised

Concentration Monitor: supplier shares for four rows that their own source lines called editorial estimates

Previously

The Concentration Monitor printed supplier shares, a Herfindahl and an editorial composite for four rows whose own source lines said the cited sources do not verify the shares. Advanced 2.5D Packaging (CoWoS-class): TSMC 65%, Amkor 15%, ASE Group (SPIL) 12% and Samsung 8%, a Herfindahl of 4,658 and a composite of 5,543 (Elevated), labelled Stable; its source line kept the shares as editorial advanced-packaging estimates. EML Laser Chips (800G+ Optical Interconnect): Lumentum 55%, Coherent (incl. Source Photonics) 30% and others 15%, a Herfindahl of 4,150 and a composite of 9,172 (Critical), labelled Stable; its source line said the product announcement it cites does not verify the shares. EUV Photomasks & Pellicles: Toppan 30%, Dai Nippon Printing (DNP) 25%, Photronics 20%, HOYA 15% and others 10%, a Herfindahl of 2,250 and a composite of 2,565 (Moderate), labelled Stable; its source line called the shares editorial estimates without a verified EUV-specific market breakdown. Wafer Inspection & Metrology Equipment: KLA Corporation 60%, Applied Materials 15%, Hitachi High-Tech 10%, Onto Innovation 8% and others 7%, a Herfindahl of 4,038 and a composite of 4,179 (Elevated), labelled Stable; its source line said the filing it cites does not verify the market breakdown.

Correction

The four rows keep their cards, evidence and monitoring signals; each card lists its suppliers alphabetically, others last. Their supplier shares read Unknown, and their Herfindahl, composite, top supplier and trajectory read Unavailable; they have no bar in the ranked chart and no place in the rank comparison, which order the other 7 rows. Their assessments are dated 22 October 2026. The page’s export and the Query Builder’s concentration tool return the same rows.

Correction

UAE country pages: the condition on G42 and Core42’s chip approval

Previously

The United Arab Emirates’ country page and its profile in the Country Access register closed the note on approved recipients with “G42 and Core42’s authorization expires April 6, 2027 absent subsequent BIS notice.” The G42 dossier printed the same note in its export-control posture row.

Correction

The rule, 91 FR 43034, sets a condition the note left out: either company that has not become a US company by April 6, 2027 must apply to BIS under 15 CFR 748.3(c) to keep its approved status. The note now states it in the words of the G42 dossier’s corrected sentence.

Numerical correctionRecord revised

Concentration Monitor: supplier shares for three rows that no cited source gives

Previously

The Concentration Monitor printed supplier shares, a Herfindahl and an editorial composite for three rows whose shares no cited source gave. Chiplet Interconnects (UCIe): TSMC 55%, Intel 20%, Samsung 10% and others 15%, a Herfindahl of 3,750 and a composite of 5,063 (Elevated), labelled Concentrating. The shares estimated advanced-packaging capacity by a method the row did not disclose, and none of the sources cited here gives supplier shares for UCIe interconnects. US Data Center Grid Interconnection: PJM Interconnection 40%, ERCOT 25%, MISO 15% and other grid operators 20%, a Herfindahl of 2,850 and a composite of 3,078 (Moderate), labelled Concentrating. The percentages had no source or definition, and the page ranked their Herfindahl among company Herfindahls under the heading Supplier Concentration; grid operators are not suppliers a developer can choose between at one site. Semiconductor-Grade Neon Gas: Ukraine (Ingas, Cryoin) 55%, China 25%, Japanese purifiers 8%, Korean purifiers 4% and others 8%, a Herfindahl of 3,794 and a composite of 3,547 (Moderate), labelled Stable, with Ukraine as the top supplier. The card’s own source, a USITC briefing of April 2022, gave Ukraine roughly half of world supply and reported that Cryoin and Ingas had stopped production in March 2022; no source was cited for the other shares.

Correction

The three rows keep their cards, evidence and monitoring signals; each card lists its suppliers alphabetically, others last. Their supplier shares read Unknown, and their Herfindahl, composite and top supplier read Unavailable; they have no bar in the ranked chart and no place in the rank comparison, which order the other 11 rows. Their trajectory reads Unavailable, as their Herfindahl does: UCIe interconnects and grid interconnection no longer read Concentrating, and neon no longer reads Stable. The page’s export and the Query Builder’s concentration tool return the same rows.

Correction

Concentration Monitor: trajectory labels that the evidence on their own cards did not support

Previously

Five rows printed a trajectory that the evidence on their own cards did not support. Wafer Inspection & Metrology Equipment read Concentrating (Herfindahl 4,038, composite 4,179) over a filing that, the card said, does not validate a change in the 60% KLA share. EML Laser Chips (800G+ Optical Interconnect) read Concentrating (Herfindahl 4,150, composite 9,172) over a prototype demonstration that measures neither laser-chip production nor a shortfall. EUV Photomasks & Pellicles read Concentrating (Herfindahl 2,250, composite 2,565) over a pellicle maker’s production and a photomask development target, neither of which describes a change in the photomask shares scored. Advanced 2.5D Packaging (CoWoS-class) read Deconcentrating (Herfindahl 4,658, composite 5,543) over TSMC’s plan for two US packaging sites, which gives no production date and would add capacity to the largest supplier. ABF Dielectric Film read Deconcentrating (Herfindahl 9,050, composite 10,317), assessed 19 May 2026 on evidence that cites a glass-substrate announcement of 24 July 2026, which reports no commercial product shipment. The page’s lead read “6 chokepoints are concentrating, 6 stable and 2 diversifying”.

Correction

The five rows read Stable, the label the register gives where its evidence shows no change in supplier shares; their Herfindahls and composites are unchanged. Their assessments are dated 26 September 2026, the date of this re-assessment. The lead’s counts follow the labels: of the 11 rows with supported inputs, one is now counted as concentrating.

Numerical correctionRecord revised

Compute estimates: communication losses discounted twice

Previously

Compute estimates multiplied dense peak throughput by a utilization default of 0.40 and an interconnect default of 0.85, so at the defaults a site was estimated to sustain 0.34 of its peak. The 0.40 is SemiAnalysis’s reported model FLOP utilization for trillion-parameter training runs on H100s. Model FLOP utilization is achieved training throughput over peak, so it already includes the time lost to communication between accelerators, and the 0.85 took that loss off a second time. On the records of 26 September, the Thresholds page counted 19 of 184 estimable sites that could accumulate 10²⁵ FLOP within a month, 48 within a quarter and 90 within a year, across 21 countries, with 94 taking longer than a year and the fastest 1.25 days.

Correction

The interconnect default is now 1.00 (methodology version 1.4.0), so an estimate at the defaults sustains 0.40 of peak. Throughput and daily FLOP estimates at the defaults rise by a factor of 1/0.85, about 17.6%; days to a threshold and the accelerator count a fixed duration needs fall by 15%, before any rounding up. The upper end of the estimation bounds rises by a factor of 1/0.95, because the interconnect maximum moves from 0.95 to 1.00; the lower end is unchanged. On the same records, 23 sites could accumulate 10²⁵ FLOP within a month, 48 within a quarter and 92 within a year, across the same 21 countries, with 92 taking longer than a year and the fastest 1.06 days. Four enter the month: NVIDIA CoreWeave Eos-DFW Phase 1 (32.0 days, now 27.2), Oracle OCI Supercluster A100s (33.3, now 28.3), and Imbue 10k Cluster and Tesla 10k H100 Cluster (34.4, now 29.2). Two enter the year: IBM Vela (378.8, now 322.0) and Iris Energy Prince George cluster (421.6, now 358.4).

Correction

Facility class: 864 records read “Hyperscale DC”, a class no source states

Previously

864 facility records read “Hyperscale DC” on their own pages and wherever the site listed them: country ledgers, the facility register, site search, the Query Builder and the MCP server. No source any of them cites states a class. 718 are OpenStreetMap sites imported by their data-centre tags, 96 are sites in the IM3 Open Source Data Center Atlas and 21 are sites from an OpenStreetMap extract, each recorded only as a data centre; 29 are interconnection-queue requests in New York and Texas. Two of those requests are energy storage by their own sources: Giga Texas Data Center (ERCOT request 25INR0688, battery storage) and Port Jeff -Mt. Sinai Energy Storage (NYISO request 0821, withdrawn). The register’s “Hyperscale DC” filter and the Query Builder’s facility search returned these records under that class, and with them the 455 OpenStreetMap records corrected on 31 May, whose pages already read “Class not stated”: 1,319 records in all. The 864 were counted in the database on 25 September 2026: records stored as Hyperscale DC, from these four sources, with no class correction on record.

Correction

862 of the records read “Class not stated”, and the two energy-storage requests read “Other”. The class filters answer on the class the pages print: of the 1,319 records, “Class not stated” returns 1,317, “Other” the two requests, and “Hyperscale DC” none. Each correction names the source its record cites and what that source states.

Numerical correctionRecord revised

Sovereign AI Program Index: version 2026.3 was rewritten in place three times after its release

Previously

From 17 July 2026 until this correction the Sovereign AI Program Index download was labelled v2026.3, released 17 July 2026. Four different CSV files were served under that one label in turn: SHA-256 19a19e3f91fad40a2978b5b733f338eaa13f774f40906be003bf8133868dec56 (17 July, 34 programmes), 38c2dbda0a3acc41e571eab2fdd1a56c6b45faaa59dea982d3ae9ed230a81f13 (14 August, 36), 6be7b5ddc8b04ae01aaf36aabf9961045e051391a657f3488dcc9c5ca698a68f (14 August, 36) and cd296f9b045355c44b4696817e45fe61dd7af396c9f1c3dc456a2e4f8225304b (8 September, 36). From 21 September the methodology file served with the last of them said the v2026.3 CSV, its checksum and its release date were unchanged.

Correction

The index is now released as v2026.4, dated 25 September 2026, with its own checksum. A citation of v2026.3 identifies one of the four files only with its checksum; all four are listed in the v2026.4 methodology’s version history. The Compute Cost Index also moves to v2026.4; its CSV is byte-identical to its v2026.3 file.

Numerical correctionRecord revised

Sovereign AI: the TSMC and export-control-reach ratings are withdrawn, and four NVIDIA ratings removed

Previously

The Sovereign AI dashboard rated 35 of its 36 programmes high for TSMC dependency, and 35 on BIS jurisdictional reach (27 low, 3 medium, 3 high, 2 none). Neither rating had a published rubric, and no record cited a source for its rating. The export-control ratings contradicted the records: the UAE was rated low beside G42’s announcement of US approval for advanced-chip exports, while the Philippines and Thailand were rated high with no export-control source. China, the Czech Republic and Poland were rated high for NVIDIA dependency and Ireland medium, although none of the four records names NVIDIA hardware or lists a source about NVIDIA.

Correction

From 25 September 2026 both ratings are empty on every programme: on the dashboard, the programme pages, the embeds and in dataset v2026.4, and the register no longer has an export-control-reach column. The dashboard states TSMC’s role once, counted from the hardware records: 19 of 36 programmes name Hopper, Blackwell or MI300 accelerators, which NVIDIA’s and AMD’s own pages say TSMC fabricates on its 4N, 4NP and 5nm/6nm processes. The four NVIDIA ratings are empty, so China, the Czech Republic and Poland also leave the Taiwan Strait scenario’s list of programmes rated high for NVIDIA dependency; the other 30 programmes keep their NVIDIA ratings.

Numerical correctionRecord revised

Sovereign AI: Spain’s government funding was shown as absent beside its own government-funded component

Previously

Spain’s only priced component read “EUR 1.5B National AI Strategy 2024 | Government | $1.62B”, yet its programme page said “No government-only dollar amount on record”, and its government-funding field was empty on the dashboard and in the dataset; its country page gave the same $1.62B as a programme amount.

Correction

Spain’s government funding is $1.62B, an estimate: EUR 1.5B converted at 1.0818 US dollars per euro, the Federal Reserve rate for 14 May 2024 that the record already used. The Spanish government’s Council of Ministers notice of 14 May 2024, now among the record’s sources, says the strategy “is earmarked with €1.5 billion from the Recovery, Transformation and Resilience Plan and its addendum”.

Correction

Visibility sheet: Google’s sites counted as having no controlling jurisdiction

Previously

The visibility sheet read that 46.9% of operating capacity has no controlling jurisdiction identified: 7,761.0 MW of 16,555.8 MW hosted. Google’s data centres were counted in that share, because their AI-hardware owner was recorded on a second Google record separate from Alphabet Inc.’s, and that record had no parent in the ownership graph. The same split sent 78 recorded training runs and deployments, and 20 facility relationships, to the second record, with 54 more runs, two Together AI hardware-owner links, one IREN supply-chain link and one IREN name alias on second records of Meta, Together AI, IREN and Alphabet. The U.S. Department of Energy’s record read “Us Department Of Energy”, gave no headquarters country, typed the department as a power provider and cited an Epoch AI file that does not name it.

Correction

Google’s sites resolve to Alphabet Inc., the company whose SEC filings and legal-entity identifier the second record already carried, and whose 10-K claims the data centres at the consolidated level. The unattributed share reads 28.9%: 4,783.0 MW of the same 16,555.8 MW. Runs, relationships, hardware-owner and supply-chain links on the other second records point at Meta, Together AI, IREN Limited and Alphabet, and the name “IREN Limited” now resolves to one organisation instead of two. The Department of Energy’s record reads “U.S. Department of Energy”, headquartered in the United States, typed as a government body and cited to the department’s own page; its 169.1 MW remains without a controlling jurisdiction, because an organisation with no recorded parent is not yet classed by its own country. The coordination sheet and the facility records follow once their precomputed chains are rebuilt; the CSV export, the country drill-down and query results over deployments read the same records.

Numerical correctionRecord revised

Country pages: no share printed over zero facility records

Previously

Fifteen country pages whose country holds no facility records (Afghanistan, Bolivia, Cyprus, Iraq, Jamaica, Jordan, Kyrgyzstan, Madagascar, Malta, Myanmar, Nicaragua, North Korea, South Sudan, Syria and Uzbekistan) printed “0.0% with capacity data or a site description” in their facility-detail figure. Its screen-reader label gave the same share of none (“0 of 0 facility records held for Afghanistan have capacity data or a site description (0%)”), and the power figure’s label beside it read “Operating plant is 0% here”.

Correction

No share exists for a country holding no facility records. The figure now reads “No facility records are held”, as the power figure beside it already read “No power figure on record”, and neither screen-reader label gives the country a share.

Numerical correctionRecord revised

Stargate UAE: a 5 GW campus envelope counted as capacity under construction

Previously

The United Arab Emirates page listed 5.0 GW of power under construction beside 3 MW operating and 160 MW announced, the countries register counted the same 5,000 MW in its under-construction stage, and Stargate UAE’s record called the figure not operating capacity because the site is under construction. The 5,000 MW is the campus’s announced envelope: the campus note on the record says the envelope should not be read as capacity already under construction, and puts the anchor project at about 1 GW with a first cluster of about 200 MW.

Correction

A campus envelope filed on a site under construction or expanding is listed with the announced figures. The United Arab Emirates reads 3 MW operating and 5.2 GW announced, with nothing under construction, and Stargate UAE’s record calls its 5,000 MW a campus envelope on a site not yet operating. The only other record affected is xAI’s Memphis programme total, whose figure a correction already withholds. No operating figure changes.

Numerical correctionRecord revised

Training evidence: Oracle’s operating power left out its 590 MW Abilene deployment

Previously

The training-evidence register gave Oracle Corporation about 170 MW of operating power. Oracle’s Abilene campus is filed as a current deployment of 590 MW, a review of which admits it as operating plant inside the 1,200 MW build-out, three phase records and the build-out itself, and the register keeps one record per site. The deployment’s figure was carried onto the kept record only when the deployment was the record the kept one replaced; at Abilene the phase records replaced it first, so the 590 MW was dropped.

Correction

Oracle Corporation reads about 760 MW operating, the Abilene deployment included.

Numerical correctionRecord revised

Company records and dossiers counted a site twice, or dropped it

Previously

Alphabet’s dossier counted 101 linked facilities as sites, including 88 operating and 9 announced, while Alphabet’s company record counted 96: the dossier included five second records of sites Alphabet already holds (Google’s Lincoln, Omaha and Papillion campuses in Nebraska, The Dalles in Oregon and Waltham Cross in England). The company records made the opposite error for a site a company holds only through a second record. G42’s record listed 15 facilities and not Stargate UAE, because G42’s record of that site is a second record of the campus whose canonical record is Oracle’s; the Stargate OpenAI record listed none.

Correction

A company counts each site once, keeping its own record of a site even when that record is not the site’s canonical one. Alphabet’s dossier reads 96 linked facilities: 86 operating, 1 expanding, 3 under construction and 6 announced. G42’s company record and dossier read 16, Stargate UAE included, and the Stargate OpenAI record lists the site through its phase 1 record. No power figure changes: every second record involved either has no figure or has it withheld by a correction.

Numerical correctionRecord revised

Compute Visibility: the ownership series compared snapshots on two power bases

Previously

The passage on ownership documentation over time read that across 3 snapshots from 23 to 25 September 2026 the operating-capacity share classified as Tier 1 had not moved, from 73.8% to 73.4%, with the data-gap share rising from 5.9% to 6.5%, and that the snapshots contained 4,266 and 4,266 facilities respectively, so the share moved with the set of records held. The 23 September snapshot counts Epoch’s records at IT power and the later ones at facility power: operating capacity went from 13,536 MW to 16,642 MW overnight with no tier’s facility count changing. The register table also printed the United Kingdom’s capacity controlled from elsewhere as 0.6 MW, where the country’s attribution figure read 0.5 MW.

Correction

The passage compares only snapshots counted on one power basis and names the snapshot it leaves out. On 25 September 2026 it compares 24 and 25 September: the Tier 1 share is 73.4% at both and the data-gap share 6.5%, over 4,266 facilities at both. The register table reads 0.5 MW for the United Kingdom; only the download rounds to two decimals.

Correction

Huawei, G42 and DeepSeek dossiers: three sources misread

Previously

Huawei’s and G42’s dossiers read “Searched US SEC filings (EDGAR full-text search), Aug 19, 2026: nothing shows ownership, operation or a capacity contract.” Huawei’s search account said “Huawei Cloud” returned 44 filings from 19 registrants, and that the two data-centre operators among them, GDS Holdings and VNET Group, identified no lease, hosting agreement or other facility-control arrangement with Huawei. G42’s said that neither NVIDIA’s filing nor Cerebras’s established facility ownership, operation or contracted capacity. DeepSeek’s gave a press report as “a self-built site of about 1 GW in Ulanqab, Inner Mongolia, and leased capacity from unnamed providers”.

Correction

The 44 filings come from 16 registrants. VNET names Huawei in March 2018 among large clients that “continued to expand their capacity at our IDC centers”, and as a current customer in filings from August 2020 to April 2022; GDS lists Huawei Cloud in October 2020 among the cloud providers its data centres host. None gives a site, a size or a term. For G42, a Cerebras statement of work effective 13 September 2023 supplies “power, space, communication, operation, and management” for G42’s Condor Galaxy 1 cluster, and TeraWulf’s presentation of 9 May 2025 says it “has a lease parent guaranty from G42”. Both dossiers now print what their searches found. The DeepSeek report, as The Japan Times syndicated it on 1 August 2026, says DeepSeek is looking to add a gigawatt of compute in Ulanqab, building a facility of its own while leasing more from other companies; it does not size the facility.

Correction

Company dossiers: opening lines claimed more than their searches had read

Previously

The opening line of six company dossiers stated a universal or a count wider than the search behind it. Anthropic’s read “Anthropic holds all its documented compute by contract, from 5 companies”; Microsoft’s “Microsoft Corporation runs its own sites and contracts capacity from 5 companies”; Alphabet’s “Alphabet runs its own sites; no contracted capacity is documented”; G42’s “No primary document shows how G42 holds its compute”, with the same sentence on DeepSeek’s dossier and, beneath its Entity List line, on Huawei’s. The searches had read other companies’ disclosures, and for G42 and Huawei only US SEC filings; none had read the subject’s own filings, announcements or papers. Anthropic’s own announcements show what that left out: it announced four of the recorded arrangements itself, and two more that the record did not hold. Its dossier also read, under “What cannot be seen”, “All 7 disclosures of these arrangements come from Anthropic’s counterparties”, every control plate printed an empty band as “No contractual capacity documented”, “No operating arrangement documented” or “No site-specific title documented”, and missing fields read as facts about the sources: “Anthropic’s share not stated” beside Colossus 1, which Anthropic’s own post of 6 May 2026 answers, “No contract start dates were disclosed”, “3 of 5 contracts state no capacity” and “No SEC filings under its own name”, which a 2004 Schedule 13D naming Huawei Technologies as a reporting person contradicts.

Correction

Each opening line now states only what the record holds and whose documents hold it, and counts companies as a floor: “Anthropic contracts compute from at least 5 companies, per their disclosures”; “Microsoft Corporation runs its own sites and contracts capacity from at least 5 companies, per its own and their disclosures”; “Alphabet runs its own sites, per its own disclosures”. A record with no control rows says only that: “How G42 itself holds its compute is not yet on record”, in the same form for DeepSeek and Huawei, with what each search read and found on a dated line beneath. The first line under “What cannot be seen” states what the sources leave out, for example “All 7 disclosures on record come from Anthropic’s counterparties; none is Anthropic’s own” and “G42’s own announcements were not searched”. Empty bands and missing fields say what the record lacks: “No capacity contract on record”, “Anthropic’s share not on record”, “No contract start date is on record”, “3 of 5 contracts on record have no capacity figure”, “No SEC registrant identifier of its own is on record”.

Correction

Anthropic dossier: Amazon’s delivery timing and investment, and TeraWulf’s $19 billion

Previously

The Anthropic dossier listed Amazon’s April 2026 agreement under “Announced” as “up to 5.0 GW; current and future Trainium generations; no delivery dates”, and its note read “Amazon also announced an immediate $5 billion equity investment and up to $20 billion tied to milestones”. The note on TeraWulf’s August 2026 presentation said its approximately $19 billion contracted-revenue figure “supplements the earlier lease announcement”.

Correction

Amazon’s release of 20 April 2026 dates part of the capacity, “significant Trainium3 capacity expected to come online this year”, so the agreement now sits under “Being built or delivered” as “up to 5.0 GW; significant Trainium3 capacity expected online in 2026”. The release calls the $5 billion an investment in Anthropic, with up to $20 billion more “tied to certain commercial milestones”; it does not say equity, and the note no longer does. TeraWulf’s announcement of 6 July 2026, filed as Exhibit 99.1 to its Form 8-K, already stated approximately $19 billion of contracted revenue over the initial term; the August presentation repeats it.

Correction

Anthropic dossier: its own announcements were missing from the record

Previously

The Anthropic dossier held seven disclosures, all by its counterparties, and said under “What cannot be seen”: “All 7 disclosures on record come from Anthropic’s counterparties; none is Anthropic’s own”. Anthropic had announced seven of its compute arrangements itself, and this site’s chokepoints page already cited one of those announcements, of 6 May 2026, for Colossus 1. Three of the seven were missing from the record altogether, not the two an earlier notice gave: $30 billion of Azure compute capacity from Microsoft, up to one gigawatt on NVIDIA systems from counterparties Anthropic does not name, and a $50 billion investment in data centres built with Fluidstack. The receipt for TeraWulf’s August 2026 document called it a “furnished earnings presentation” that “repeats the approximately $19 billion of contracted revenue”, and the Project Rainier line dated Amazon’s release June 2025.

Correction

The record now holds 20 disclosures of 9 arrangements: 8 are Anthropic’s own announcements, 11 are its counterparties’ and one, NVIDIA’s 8-K, is a third party’s. The opening line reads “Anthropic contracts compute from at least 6 companies and counterparties not named, per its own and their disclosures and a third party’s filing”, and beside Colossus 1 “Anthropic’s share not on record” gives way to “all of Colossus 1’s compute capacity”, per Anthropic’s post of 6 May 2026. No source states the form of the Fluidstack arrangement, so it sits in its own band and is never counted as a contract. AMD’s partnership to deploy up to 2 GW of MI450 GPUs names no site, owner or facility operator, and is stated under “What cannot be seen”. TeraWulf’s document is its Q2 2026 business update, furnished as Exhibit 99.2, which puts the lease’s long-term contracted cash flows at about $19 billion over its 20-year term; “contracted revenue” is the wording of its 6 July announcement. The Rainier line is dated October 2025, the update the record quotes.

Correction

G42 dossier: the condition on its chip approval, and the rule’s dates

Previously

The G42 dossier said Supplement no. 8 to part 740 approves G42 and Core42 to receive specified advanced chips without a license and that, absent further notice from BIS, the approval expires on April 6, 2027, citing “91 FR 43034, Jul 10, 2026”. It described the United Arab Emirates as “treated as a US ally under US chip-export rules”.

Correction

The rule, published on 14 July 2026 and effective on 10 July, sets a condition the dossier left out: either company that has not become a US company by April 6, 2027 must apply to BIS under 15 CFR 748.3(c) to keep its approved status. The citation now carries the publication date, 14 July 2026, and the sentence names 10 July as the effective date. The UAE line now states the country’s treatment in the rule’s own terms, Country Group A:5 since 10 July 2026 with specified advanced-computing items reaching approved recipients without a license; the same rule keeps the license requirement for those items to any UAE recipient that is not approved.

Numerical correctionRecord revised

Capacity totals: one world figure read over three record sets

Previously

The notice of 23 September on planned capacity counted as present capacity said that operating capacity is 16.6 GW on 322 records, that a further 56.2 GW is recorded as announced, under construction, build-out beyond operating plant or earlier phases, and that the worldwide operating share every country page prints is 31.6%. The first two figures count every record, those from licensed sources included, and over them 16.6 GW is 22.9% of 72.8 GW; the 31.6% is taken over the publishable records alone, 52.6 GW. The company disclosure register gave the same 56.2 GW without saying that 20.2 GW of it sits on licensed records the country pages leave out, and the countries register printed 32% operating over the records placed in a country, 52.5 GW, leaving out 125 MW on 112 records whose country does not resolve. No page named the records it counted.

Correction

Read on 25 September 2026, the 72.8 GW of power on record is three sets. 52.6 GW is on publishable records, 16.6 GW of it operating, which is 31.6%; of that 52.6 GW, 52.5 GW is placed in a country and 125 MW (86 MW operating) sits on 112 records whose country does not resolve. The other 20.2 GW is on 184 records from licensed sources, none of it operating, and is published only as a total. The countries register and every country page print 31.6% over the publishable records and say so, the register now counting the records whose country does not resolve, and the company disclosure register names the licensed 20.2 GW inside its 56.2 GW.

Correction

Facility class: country pages printed a class the record withholds

Previously

Since 31 May, 455 facility records from the OpenStreetMap corpus have read “Class not stated” on their own pages: the ingest stamped all 1,173 of its records Hyperscale DC, and no source states a class for these 455. Country pages printed the stamped class instead, on at least 315 rows across 77 country pages, and the Query Builder, the site search and the MCP server returned it too.

Correction

Every channel now prints the class the record’s own page prints: “Class not stated” for the 455 records. The other 718 records the same ingest stamped are corrected in the notice on 864 records whose sources state no class.

Correction

Supply chain: 630 partnerships were listed as suppliers and customers

Previously

630 of the 5,485 public supply-chain records describe partnerships, which name neither company as the other’s supplier. Company records listed each one under a company’s suppliers or its customers, according to the column it happened to be stored in; the supply-chain graph and the map drew them as supplier-to-customer links; and the Query Builder and the MCP server’s supply-chain tool returned them as upstream or downstream relationships. NVIDIA’s record, headed “Upstream Suppliers · 116 records”, opened with AAEON Tech, ABB, Adlink, Advantech, AEye and Altair: 91 of the 118 records it read were partnerships, Barclays among them, whose cited filing is a share-repurchase agreement.

Correction

A relationship recorded as a partnership is listed under its own heading on both companies’ records, and nowhere as supply: not in a list of suppliers or customers, not as a link in the supply-chain graph or an arc on the map, and not in a Query Builder or MCP answer about suppliers or customers. This change leaves the 4,855 supply records as they were.

Correction

Colossus 1: Anthropic’s compute agreements with SpaceX

Previously

From 8 May, the Colossus 1 record, its Markdown copy and the Query Builder described one development, credited to xAI’s post: Anthropic leasing all of Colossus 1’s compute as the facility’s operating tenant, xAI keeping ownership of the facility, and the price and term undisclosed. The neocloud chart called the arrangement a whole-cluster lease. The chokepoints page gave Anthropic’s figure as “220,000 NVIDIA GPUs”.

Correction

The record now holds two dated statements, each credited to the party that made it. On 6 May Anthropic said it would use all of the compute capacity at Colossus 1: more than 300 MW and over 220,000 NVIDIA GPUs, which the chokepoints page now also reads. SpaceX’s final prospectus of 12 June calls the arrangements Cloud Services Agreements and gives their terms: $1.25 billion a month through May 2029 for capacity across Colossus and Colossus II that includes approximately 325,000 NVIDIA GPUs, terminable by either party on 90 days’ notice after an initial three months, and not divided between the sites. Neither xAI’s post nor these two documents describes the ownership and tenancy split the record stated.

Numerical correctionRecord revised

Export-control cross-reference: 101 of 102 ownership-chain matches could not be traced to the designated entity

Previously

The home page counted 142 designation-to-company matches, 102 of them through ownership chains. The Entity List cross-reference read 138 of 3,420 active designations as matched (4.0%), with 142 matches, 139 of them involving organisations with supply-chain records, 95 designations Confirmed and 43 Screening leads, and 102 chain matches between 101 designations and 10 organisations, 58 at high confidence and 44 at medium. Among them, 52 separately designated Huawei companies were matched to HiSilicon, 35 China Electronics Technology Group institutes and subsidiaries to their own parent group, four Pakistani companies with “Systems” in their names to Systems (Pakistan), AccoTest Technology and a hair-accessories maker to Anhui Conch Cement, and Xinjiang Police College to COL. Company records listed export-control designations reaching 78 organisations through affiliates, among them 92 on each of Rusal, EuroSibEnergo and Vostsibugol and 53 on HiSilicon. The methodology gave 699 of 3,435 designations (20.35%) an anchor in the ownership graph, and 101 (2.94%) a path to a compute-relevant organisation. The Impact Pre-Scorer measured its projections against 51 entities reached through corporate relationships in the Huawei 2019 family and 2 in SMIC 2020, and its removal case for CETC-7 and CETC-30 reached 13 closure entities.

Correction

A chain match starts from an anchor, the ownership record taken to be the designated entity. For 97 of the 101, the anchor was admitted only because its name sits inside the designation’s own name, or the reverse (“Huawei” inside each Huawei company’s name; the alias “ACC” inside AccoTest’s); for two, it was one record that Inspur Group and Inspur Software both claimed, and a name cannot say which designated entity that record is. Many chains then climbed from a subsidiary to its parent, and two ended at a company the records had filed under SMIC and Inspur by an alias. The other two came from a separate subsidiary search: one begun from a name match withdrawn on 23 September, one following an ownership link whose cited registry record, iFLYTEK’s own, lists no subsidiary. One chain match stands: Huawei Technologies Co., Ltd. to HiSilicon, on a record carrying Huawei Technologies’ exact legal name. The home page reads 41 matches, 1 through an ownership chain. The cross-reference reads 40 of 3,420 active designations matched (1.2%), 41 matches, 38 involving organisations with supply-chain records, 39 Confirmed and 1 Screening lead, and 1 chain match between 1 designation and 1 organisation, at high confidence. Company records list designations through affiliates on 15 organisations; Rusal, EuroSibEnergo and Vostsibugol list none, and HiSilicon lists 1. 30 of the 3,435 designations (0.87%) have an anchor, and 1 (0.03%) reaches a compute-relevant organisation. The Impact Pre-Scorer counts 9 entities reached in the Huawei 2019 family and 1 in SMIC 2020, and the CETC-7 and CETC-30 removal case reaches none; the facilities each reaches are unchanged. The 4,314 ownership walks that descended from the refused anchors are withdrawn and kept, each with the rule that refused it, in a private ledger. Five of the 24 subsidiaries whose name matches were withheld on 23 September are among the Huawei companies: that notice said their parent relation is shown where ownership records establish it, and the chain match each carried was one of these, which led to HiSilicon rather than to a parent.

Numerical correctionRecord revised

Sovereign AI: the United States procurement figure counted records rated unrelated to AI, and advertised budgets as spending

Previously

The procurement column of the Sovereign AI dashboard gave the United States $40.4B, recorded across 2,298 of 2,471 records, beside a green dot labelled “High confidence (≥0.9)” and authority tier 1. The figure admitted any record the relevance classifier scored 0.7 or above, whatever it had rated the record’s relevance: 2,412 of the 2,471 were records it rated unrelated to AI ($39.9B), and 2,087 of those ($39.4B) were rejections by a keyword pre-filter, which records a score of 0.95 without a model reading the record. Grants.gov funding opportunities, advertised budgets set before any award, were counted as committed spending (948 records, $39.5B). One State Department opportunity, stored once for each of its four postings, was counted four times at $2,147,483,647, the largest value its source field accepts. The dot showed the classifier’s mean score for its own calls, and the tier graded the source documents; neither measured whether the figure was right.

Correction

On 25 September 2026 the United States figure counts $4.4M across 13 awards: records at the committed stage or later that the classifier rated high or medium AI relevance, with its score at 0.7 or above or a person’s review (high $2.0M in 4, medium $2.4M in 9). Beside it the page gives the counted solicitations’ advertised budgets, $314.0M across 6 (one without an amount), as not spending; the low-relevance awards it does not count, $3.1M across 19; and the records left out, by reason. The field-maximum value is stored as no amount with a note saying why, a re-posted solicitation counts once, and the dot and tier say what they measure.

Numerical correctionRecord revised

Export-control alignment: four SEC filers read as unresolved because of their own subsidiaries

Previously

The coordination view classed the 208 facilities it attributes to Microsoft, Equinix, Nvidia and ASML as OPAQUE, each chain described as having “no confirmed public-filing or government endpoint”, although all four companies file with the SEC: the records for Microsoft Fairwater Atlanta, Equinix LD10, NVIDIA Helios and ASML Veldhoven each labelled the chain “Unresolved ownership chain” beside a tier 1 visibility reading whose stated basis is the company’s SEC identifier. The OPAQUE total read 3,669 facilities and 4,894,253 operating H100-equivalent GPUs; NONE read 509 facilities and 7,722,834.

Correction

Each of the four companies’ own records carries its SEC filing number, so each chain ends at a listed company in an allied-coordinated jurisdiction (the United States; the Netherlands for ASML) and the 208 facilities read NONE (“No documented gap”). OPAQUE falls to 3,460 facilities and 3,059,955 operating H100-equivalent GPUs, NONE rises to 717 and 9,557,132. STRONG reads 64: the same recomputation moves GDS Beijing 1 from OPAQUE to STRONG, because when it was last classified, on 23 September, no source established its owner, operator or AI-hardware owner, and one now does (GDS Holdings); the earlier walk classifies it the same way, so that move is not part of this correction.

Correction

Query Builder: three EU procurement records built from misread notices are withdrawn

Previously

The Query Builder’s procurement search could return three records drawn from EU public procurement notices (Tenders Electronic Daily), and its allocation rollup three totals built from them: an open tender in Lithuania and contract awards in Switzerland and Poland, each rollup total reading $0. None described a real procurement. Each was filed under a number from inside a notice instead of the notice’s own publication number, so its source link led to no published notice; each named the contracting authority as the contract’s winner; each carried a three-letter country code where every other record carries two; and each was marked unrelated to AI although no notice had been read by the classifier: a filter rejected the notices’ product codes because they lacked a check digit, and the rejection was stored as the classification.

Correction

The three records and the three rollup totals built from them are withdrawn. None of the 763 conversations the site has stored names any of them.

Related pages

Query Builder

Numerical correctionRecord revised

Trade Impact: regional billings compared over post-event months the series does not hold

Previously

The regional-billings panel on Trade Impact compares WSTS billings in the twelve months after an action with a counterfactual, and the WSTS series on the page ends in January 2026. Selecting any of the five US actions dated after it, from the Super Micro indictment of 19 March 2026 to the UAE’s move to A:5 on 10 July 2026, printed a net gap of +$0M and, for each of the four regions, “+$0M vs counterfactual · +0.0%”: months the series does not hold were read as zero. For the ten actions from March 2025 to January 2026 whose following year the series holds only in part (1 to 11 months), the panel summed the months it had and described the sum as covering the twelve post-event months, and the per-action table printed seven of those sums beside full-year sums with no month count.

Correction

An action with no post-event month in the series prints no gap and says the series holds no month from the action onward. A partial window is summed over the months holding both a billing and a counterfactual, and the figure, the chart description and the table state how many of the twelve those are (the Entity List expansion of 25 March 2025 reads 11 of 12, the affiliates-rule suspension of 10 November 2025 3 of 12). The nine actions with a full year are unchanged.

Numerical correctionRecord revised

Iran scenario: the first render counted 14 of 183 location records in range

Previously

The Iran threat scenario’s summary, as the server sent it, read “14 location records fall within the published range envelopes”. The 14 were the supplemental cloud-region records alone: the page requested the facility records only after it reached the browser, so readers whose browser ran it saw the full count a moment later, while search engines, readers without scripts and any load whose facility request failed kept 14, and a failed request was not mentioned.

Correction

183 location records fell within the envelopes on 24 September 2026: 170 facility records and 13 supplemental cloud-region records, in 21 countries. The scenario now reads its facility records on the server, so the first render carries the full count with its status split, and a failed read keeps the page’s last good render instead of a partial count.

Numerical correctionRecord revised

Query Builder: the trade and licensing tools described data they do not hold

Previously

The Query Builder’s tool register described the BIS licensing tool as “2,587 rows covering CY2018-2022”, each carrying approval, denial and return-without-action counts, a licence value, and a friction rate and tier, with a start year defaulting to 2018 and a friction filter to use for “majority denied”. It described the trade tool as reading five sources, and that tool’s year and partner groupings, described as annual totals, added every source’s rows and every direction together, though the sources measure the same trade.

Correction

The 2,587 licensing rows span calendar years 2015 to 2022. Each is one ECCN, destination, year and action, approved or denied, with a count and a share of the world total; no row carries a licence value or a friction rate, the tool sets no start-year default, and a friction filter returns a note pointing to the per-country summaries instead of being applied. The trade tool reads six sources, the US Census Bureau among them, and groups by source and direction without adding them together. None of the 748 conversations the site has stored called the trade tool.

Numerical correctionRecord revised

Trade Impact: each corridor is read from one source, never two added together

Previously

Every corridor on Trade Impact added together the rows of every source that reports it, though each of those sources measures the same trade. Korea → China for the October 2022 controls read $101.6B → $82.9B a year (−18.4%): CEPII BACI’s $60.4B plus UN Comtrade’s $41.3B, a figure neither source reports. China’s IC imports from the United States read $30.0B → $17.8B (−40.7%), China GACC’s two-way trade added to UN Comtrade’s imports. The reporter totals each verdict is judged against, and the seller baskets on Plate IX, were summed the same way (Korea’s exports at about $229B a year; the Korean, Japanese and German baskets each drew “Other Asia, nes” twice, once per source’s code). The discovered corridors added sources as well, counted GACC’s two-way figures as exports (China → Taiwan, $174.8B), and listed one flow twice (CEPII BACI’s United States → China beside China’s own imports from the United States; Korea → Other Asia, nes under two codes). The December 2024 action was compared with 2025, a year neither UN Comtrade nor CEPII BACI reports, so its before-years added three sources and its after-year held one (Japan → China, −83.6%).

Correction

Each corridor now reads one source, the first of UN Comtrade, Taiwan Customs, the US Census Bureau, CEPII BACI and Japan e-Stat to report every year of both windows in the corridor’s direction, and draws the others beside it; China GACC, which files two-way trade, never heads a corridor. Korea → China reads $41.3B → $33.1B (−19.8%) on UN Comtrade, and China’s imports from the United States $14.4B → $7.75B (−46.1%). Eight of the nine featured corridors change figures (Taiwan → China was already read from Taiwan Customs alone), and none changes verdict. The totals behind the verdicts and the seller baskets are read from the same source as their corridor. Discovered corridors use export rows only and list no area under two of its codes. The comparison stops at actions dated 2023, the last year whose following year UN Comtrade and CEPII BACI report; the December 2024 action is listed and not compared.

Correction

Export-control cross-reference: name matches joining a designation to a different organisation

Previously

The cross-reference register joined ten Entity List designations to organisations they do not name: Schneider GmbH to Schneider Electric SE as a confirmed match, and nine others as screening leads, among them China Communications Construction Company to China Construction Bank, the University of Science and Technology of China and Nanjing University of Science and Technology to the University of Electronic Science and Technology of China, and Harbin Engineering University to the Harbin Institute of Technology. The change feed listed all ten as matches added.

Correction

None of the ten organisations is the designated entity. For three of the pairs, BIS designates the matched organisation separately under its own citation; the rest share only generic words with the designation. The ten matches are withdrawn with their reasons. Twenty-four further name matches joined a separately designated subsidiary or branch to its parent as the same organisation, among them Chengdu Huawei Technologies to Huawei Technologies and Yangtze Memory Technologies (Japan) to Yangtze Memory Technologies; they are withheld, and the parent relation is shown where ownership records establish it. The change feed shows all thirty-four as deprecated.

Numerical correctionRecord revised

Regulatory impact pre-scorer: simulations shown from partial reads

Previously

On at least two requests (15 August and 23 September 2026) a batch of organisation reads inside the Regulatory Impact Pre-Scorer timed out, and the page showed the simulation built from the reads that succeeded: the organisations in that batch lost their names and headquarters countries, so the report’s country breakdown left them out. Which entity was simulated, and the figures those two requests showed, were not recorded.

Correction

A simulation is shown only when every read it needs has succeeded; when one fails, the page says the simulation could not be run.

Numerical correctionRecord revised

Cascade: the downstream plate states connections, not how far a failure reaches

Previously

The plate on /cascade ranked every organization by its count of recorded downstream relationships within three links and described each count as how far “a failure here reaches”, naming Siemens EDA and TSMC the widest at 191 organizations each, most of that count running through partnership records.

Correction

The plate states what it counts: each organization is “connected to” so many others downstream within three recorded supplier–customer links, and the caption says the count records relationships and says nothing about volume, share or substitutes. Public relationships record that a relationship exists and almost never what flows (2 of the 999 drawn carry a product, none a criticality), and an SEC customer disclosure, their commonest source, evidences the supplier’s revenue concentration rather than the customer’s dependence. No ordering of that record measures how far a failure travels, so the plate no longer claims one.

Related pages

Cascade Simulation

Numerical correctionRecord revised

Supply-chain relationship counts: the count of the graph they describe

Previously

The About page gave 16,755 distinct supplier–customer relationships and the methodology page 16,755 supplier–customer–product keys, counting as separate relationships records that differed only in a product label the site withholds, while the cascade engine held 16,346 (earlier on 23 September the pages gave 14,831 against 14,422). The methodology page also said partnership records were in that count; the cascade leaves them out. The API index described the supply-chain graph endpoint as “Full supply-chain graph (20,798 edges)”, the number of stored records, licensed ones included.

Correction

The About and methodology pages give 11,858 supplier–customer relationships, the count the cascade engine simulates over on 24 September, and the methodology page says that partnerships are left out of it. The API index gives the 2,977 relationships from public sources that the endpoint returns.

Numerical correctionRecord revised

Cascade: relationships last disclosed five or more years before the latest filing wave no longer propagate

Previously

The cascade propagated disruptions along every relationship on record as a present dependency, including those whose only evidence is SEC disclosures for fiscal periods that ended five or more years before the latest filing wave: 1,367 of 13,233 supplier–customer pairs in the full corpus and 991 of 1,938 in the public graph drawn on /cascade. ASYST Technologies, last disclosed in fiscal 2002 and bankrupt since 2009, was among them.

Correction

A relationship whose every observation is a dated SEC disclosure, the latest for a fiscal period ending five or more years before the corpus’s latest filing wave, is historical and no longer propagates; an undated or curated observation keeps a relationship current. The wave is the latest period-end at least 20 filers disclose, 2024-12-31 on 23 September, so periods ending on or before 2019-12-31 are historical; it moves when a new wave arrives, never for one filing. Within a pair, consecutive disclosures fall at most five years apart 98.5% of the time; a lapsed disclosure is an absence of evidence, not a proven end. The simulation runs over 11,858 relationships where it ran over 13,310, the criticality weight covering 86.11% of them and price correlation 67.54%. The public graph drawn on /cascade holds 999 relationships among 591 organizations where it held 2,638 among 1,365, partnerships included in that fall; the download lists what is not drawn.

Numerical correctionRecord revised

Cascade: partnerships no longer propagate as supply

Previously

The cascade engine treated every stored supply-chain record as a supplier–customer dependency, including 3,337 that record a partnership: 1,008 licensed relationships of the partner kind and 2,329 whose product line reads “… partnership”. Disruptions travelled along them from one partner to the other, and /cascade read 14,422 relationships among 4,950 organizations (16,346 among 5,374 once the 1,924 licensed relationships added on 23 September reached it).

Correction

A partnership moves nothing from one firm to the other, so the engine no longer propagates along one and the coordination-gap edge counts leave them out. On the corpus of 23 September the simulation runs over 13,310 relationships among 4,974 organizations, the same 3,036 partnership edges removed before and after that addition; the criticality weight now covers 76.72% of propagation edges and price correlation 60.17%. Every scenario reaches as many organizations or fewer; the TSMC Taiwan disruption reaches 114 where it reached 118. Three records whose counterparty is merely called “Partners” remain supply.

Numerical correctionRecord revised

Company financials: another company's filing, and figures years out of date

Previously

Marvell's record gave revenue of $21.1B and capex of $0.3B: Cognizant Technology Solutions' figures, read from Cognizant's filer number. Equinix's gave revenue of $6.0B, its 2020 figure, and capex of $14.9M, which matches no line in its filings, under a 2024 annual-report citation. Iron Mountain's gave revenue of $4.5B, its 2021 figure, under the same kind of citation. No company's revenue or capex stated the fiscal year it covered.

Correction

From each company's own annual report as filed with the SEC: Marvell $8.2B revenue and $354M capex for the fiscal year ended 31 January 2026; Equinix $9.2B and $4.3B for 2025; Iron Mountain $6.9B and $2.3B for 2025. Every company record now states the fiscal year its revenue and capex cover, and pairs them only when both come from that year.

Numerical correctionRecord revised

Compute Visibility Index: the ownership-documentation series read whole

Previously

From 14 August 2026 the worldwide series on the Compute Visibility Index was built from the first 1,000 of the snapshot rows (the table held 38,717 on 23 September). It read “Across 4 snapshots between 2026-04-25 and 2026-04-29, the capacity share classified as Tier 1 has risen, from 39.6% to 43.8%”, over 4,529 and 3,669 facilities, with the data-gap share at 12.4% and 13.1%. The last of those snapshots was cut part-way: it holds 4,529 facilities, of which the page read 3,669.

Correction

Read whole on 23 September 2026, the series holds 145 snapshots from 25 April to 23 September. Summing every recorded power figure, the Tier 1 share went from 39.6% to 52.6% and the data-gap share from 12.4% to 15.3%, over 4,529 and 4,266 facilities. Since 24 September the chart plots only the snapshots that weight tiers by operating capacity, which begin on 23 September (Tier 1 at 73.8% of operating capacity that day); the earlier snapshots are listed beneath it with the figure each recorded, and the page marks where Epoch’s records counted IT power (11 July to 23 September).

Numerical correctionRecord revised

Capacity totals: planned capacity counted as present capacity

Previously

Capacity totals added the power and accelerator figures of records in every status, and the operating figures that did read status counted two things a status does not settle: a campus build-out figure filed on an operating record, and an earlier phase of a cluster whose operating later phase already counts its chips. The United Arab Emirates page gave 5.2 GW of tracked capacity, 5,000 MW of it one campus under construction, and 91,888 accelerators, 85,000 of them announced; the countries register ranked it second. The United States page gave 16.3 GW operating, counting the New Carlisle and Abilene build-out figures (2,200 MW and 1,200 MW) as operating plant, and 6,987,464 accelerators of every status. The Compute Visibility headline read 67.7% of tracked capacity as having no controlling jurisdiction identified, over 72.3 GW across 4,057 sites; the disclosure register placed its declaring organisations at 11.7 GW of 72.8 GW; the training-evidence register led with Meta at 4,625 MW; the participation page gave the United States 16,330 MW on 152 sites; the neocloud chart gave CoreWeave 1,158,959 H100-equivalents and Applied Digital 846,387, none of Applied Digital’s on an operating site; the threshold plot ranked 201 facilities, 97 reaching 10²⁵ FLOP within a year; the coordination view summed H100-equivalents of every status; the impact pre-scorer summed power of every status (8,032 MW with Oracle as the seed); and Alphabet’s dossier counted 736 MW announced on 3 records, one of them a second record of Google’s Papillion campus whose figure the corrections withhold.

Correction

Every total counts operating capacity only and names beside it what it leaves out: announced or permitted records, records under construction or expanding, build-out figures on operating records, earlier phases of operating clusters, and retired records. Where a campus had been counted once at its build-out figure, the operating record’s own figure counts instead, under a review citing its source: New Carlisle 1,092 MW of the 2,200 MW campus, Abilene 590 MW of 1,200 MW. Operating capacity is 16.6 GW on 322 records, a further 56.2 GW is recorded as announced, under construction, build-out beyond operating plant or earlier phases, and the worldwide operating share every country page prints is 31.6%, not 34.7%. The United Arab Emirates reads 3 MW operating and 6,888 operating accelerators; the United States 14.7 GW and 2,252,843. Compute Visibility reads 46.9% of operating capacity as having no controlling jurisdiction identified, over 16.6 GW across 306 operating sites; the declaring organisations sit at 1.0 GW of it; Meta reads 2,365 MW operating, second to Alphabet’s 3,083 MW; the participation page gives the United States 14,707 MW on 157 sites; CoreWeave has 805,245 operating H100-equivalents and 353,714 on sites not operating, Applied Digital none operating; the threshold plot ranks 183 facilities, 89 within a year, once 26 earlier phases leave it; the coordination view sums operating H100-equivalents only; with Oracle as the seed the impact pre-scorer reads 760 MW operating, with 7,272 MW not operating beside it; and Alphabet’s dossier counts 486 MW announced on 2 records.

Related pages

Countries: Capacity and Export Controls · Country Radar · Compute Visibility Index · Disclosure Posture · Capacity: Training Evidence · Neocloud Landscape · Participation · Capacity Thresholds · Allied Coordination Gap Analyzer · Regulatory Impact Pre-Scorer · Alphabet: who controls its compute · AWS Project Rainier (New Carlisle, IN) · Anthropic-Amazon New Carlisle · Stargate Abilene (OpenAI/Oracle/SoftBank) · OpenAI Stargate Abilene · Afghanistan · Albania · Angola · Argentina · Armenia · Australia · Austria · Bahrain · Bangladesh · Belarus · Belgium · Bhutan · Bolivia · Brazil · Bulgaria · Canada · Cape Verde · Chile · China · Colombia · Costa Rica · Côte d’Ivoire · Croatia · Cuba · Cyprus · Czech Republic · Denmark · Djibouti · Dominican Republic · Ecuador · Egypt · El Salvador · Estonia · Faroe Islands · Finland · France · Georgia · Germany · Ghana · Greece · Guam · Guatemala · Hong Kong · Hungary · Iceland · India · Indonesia · Iran · Iraq · Ireland · Isle of Man · Israel · Italy · Jamaica · Japan · Jordan · Kazakhstan · Kenya · Kosovo · Kyrgyzstan · Laos · Latvia · Lebanon · Lithuania · Luxembourg · Madagascar · Malawi · Malaysia · Maldives · Malta · Mauritius · Mexico · Moldova · Morocco · Mozambique · Myanmar · Nauru · Nepal · Netherlands · New Zealand · Nicaragua · Nigeria · North Korea · North Macedonia · Norway · Oman · Pakistan · Palestine · Panama · Papua New Guinea · Paraguay · Peru · Philippines · Poland · Portugal · Puerto Rico · Qatar · Romania · Russia · Saudi Arabia · Serbia · Singapore · Slovakia · Slovenia · South Africa · South Korea · South Sudan · Spain · Sri Lanka · Sweden · Switzerland · Syria · Taiwan · Tanzania · Thailand · Turkey · Tuvalu · Uganda · Ukraine · United Arab Emirates · United Kingdom · United States · Uzbekistan · Venezuela · Vietnam

Numerical correctionRecord revised

Export-control alignment: ownership chains start where a source establishes the role

Previously

The coordination view walked each facility’s ownership chain from whichever organisation its record named as operator, owner or hardware owner, whether or not a source established that role. It read 104 facilities as STRONG (a chain reaching a non-aligned or restricted jurisdiction), 28 as MILD, 780 as NONE and 3,354 as OPAQUE.

Correction

A chain starts only at the organisation a source establishes as operator, owner or AI-hardware owner, the starting point the Compute Visibility attribution uses, and follows no ownership link reviewed as establishing no control. The 315 classified facilities whose chain had started from an organisation no source establishes are now unresolved, 41 of them previously STRONG (DayOne Nusajaya Tech Park the largest by H100-equivalent GPUs): 63 STRONG, 25 MILD, 509 NONE and 3,669 OPAQUE.

Numerical correctionRecord revised

Compute attribution: control classed only where a source establishes the role

Previously

The attribution chart on the Compute Visibility Index classed a facility’s control from whichever organisation its record named as operator, owner or AI-hardware owner, whether or not any source established that role, and walked every recorded ownership link above it. It read 43.6% of 72.3 GW as attributable to a controlling jurisdiction (34.8% to the host country, 8.8% elsewhere), 32.9 GW (45.5%) as an unresolved chain and 7.9 GW (10.9%) as no organisation on record.

Correction

A control class is shown only where a source establishes the role: the chain starts at the organisation a source establishes as operator, owner or AI-hardware owner and walks no ownership link reviewed as establishing no control, each review citing its document. Of the same 72.3 GW, 32.3% is attributable (25.3% to the host country, 7.0% elsewhere) and 16.0 GW (22.1%) has an unresolved chain; 19.8 GW (27.4%) has an owner named only by a licensed source not yet reviewed, now a category of its own; for 13.2 GW (18.2%) no source establishes an owner, operator or AI-hardware owner. Among the tracked facilities, 1,489 whose recorded organisation no source establishes no longer carry a control class, and nine facilities of Nebius and TSMC Arizona (433.3 MW) move from foreign-controlled to unresolved, their parent chain having rested only on corporate trees their source describes as operational rather than legal hierarchies.

Numerical correctionRecord revised

Epoch facility records: IT power shown as facility power

Previously

From 10 July 2026 the 52 facility records drawn from Epoch AI’s data-centre table gave Epoch’s IT power as their power capacity, while records from every other source give facility power, cooling and other overhead included. Country and operator totals added the two: the United States page read 13.8 GW operating of 36.5 GW tracked, and its capacity chart put Colossus 2 at 1,276 MW beside a record reading 946 MW.

Correction

Each of those records now gives Epoch’s facility power, with Epoch’s IT power beside it as power for IT equipment, both from the same dated Epoch estimate: Colossus 2 reads 1.3 GW, 946 MW of it for IT equipment. The 50 of them counted in totals rise from 9,653.8 MW to 12,408.6 MW. The United States reads 16.3 GW operating of 39.0 GW tracked, and the worldwide operating share is 34.7% instead of 31.1%. Ownership-share snapshots taken from 11 July to 23 September keep the IT basis, and the charts that draw them say so.

Correction

Country pages: sovereign funding figures named by type

Previously

Country pages printed a programme’s government funding under the word “announced”: the United States read $30.0M announced, against the programme’s ~$2.6B headline announcement.

Correction

Each figure carries the name the sovereign programme table uses: for the United States, $30.0M government funding and ~$2.6B in programme announcements. The Czech Republic, Germany, France, Japan and Australia are corrected the same way.

Correction

EDA market shares in scenario and coordination analysis

Previously

Two disruption-scenario rationales gave Synopsys and Cadence about 75% of the EDA market while the scenario descriptions gave 62%, and the coordination analysis gave an unsourced 80% or more for the three largest vendors.

Correction

Every figure reads the recorded 2024 revenue shares: about 62% for Synopsys and Cadence, and about 76% with Siemens EDA.

Correction

Foundry market shares for the second quarter of 2025

Previously

The coordination analysis cited TrendForce’s second-quarter 2025 foundry figures but gave TSMC 71% and Samsung Foundry both 6.8% and 8%.

Correction

The figures are TrendForce’s: TSMC 70.2%, Samsung Foundry 7.3%, SMIC 5.1% and UMC 4.4% of foundry revenue in the quarter.

Numerical correctionRecord revised

Karolina counted once in Czech and EuroHPC totals

Previously

The Czech Republic’s accelerator total counted the Karolina supercomputer’s 576 GPUs twice, once from IT4I’s hosting record and once from a catalogue’s deployment record: 1,152 GPUs. EuroHPC JU’s organisation totals carried the same 576 twice.

Correction

The two records describe one fleet, 72 nodes with eight NVIDIA A100 GPUs each, and it is counted once: 576 GPUs for the Czech Republic and 576 fewer in EuroHPC JU’s totals.

Correction

Advantest–Astronics transaction: consideration terms

Previously

Both company records gave the February 2019 transaction a single value of $135.0M, a figure the seller’s filings do not state.

Correction

The records give the terms Astronics reported: $100.0M announced cash; $103.8M of 2019 proceeds; a first earnout capped at $35.0M and an uncapped second earnout over 2019–2022; and earnout receipts of $10.7M, $11.3M and $3.4M for 2020 to 2022. No all-in price is stated.

Related pages

Advantest · Astronics

Numerical correctionRecord revised

Gadi: GPU partitions in the count and the compute estimate

Previously

640 GPUs: the V100 partition. Once the count was corrected to 776, the compute estimate applied the V100 rate to all 776 GPUs, and the record’s catalogue figures gave 203.73 PFLOP/s and 165 H100-equivalent by assuming the SXM form of the H200.

Correction

776 GPUs, including 120 H200 and 16 A100 GPUs alongside the 640 V100 GPUs. Compute is estimated partition by partition. NCI does not state the H200 form factor, and the SXM and NVL versions differ in dense FP16 throughput, so no facility estimate is derived; each partition’s status appears on the facility record.

Correction

Condor Galaxy 1: Cerebras systems no longer given an H100 rate

Previously

The compute estimate treated the facility’s 64 Cerebras CS-2 systems as 64 NVIDIA H100 GPUs, because no rate was recorded for Cerebras hardware.

Correction

No cited dense FP16 rate is recorded for the Cerebras CS-2, so no compute estimate is derived for the facility. Hardware without a cited rate is not assigned another accelerator’s rate.

Numerical correctionRecord revised

Shaheen III: chip count and compute estimate

Previously

2,816 GH200 superchips, from the planned configuration. Once the count was corrected to 2,800, the record’s compute figures applied the NVIDIA H100 SXM rate to each superchip: 2,770.6 PFLOP/s and 2,800 H100-equivalent.

Correction

2,800 GH200 superchips. KAUST reported completing acceptance and ownership transfer in October 2025. No primary source gives a dense FP16 figure per GH200 superchip, so no compute estimate is derived for the facility.

Related pages

KAUST Shaheen-III

Correction

Stargate UAE chip inventory withheld

Previously

G42’s company-wide authorization to purchase up to 35,000 GB300-equivalent chips was assigned to Stargate UAE Phase 1.

Correction

The authorization does not establish an installed inventory at this facility. Its chip count and derived performance figures are withheld.

Correction

Comparable periods in chip shipment and concentration figures

Previously

Incomplete quarters and annual observations were included alongside cumulative shipment series. Changes in source coverage appeared as changes in shipments and concentration.

Correction

Incomplete quarters are excluded. Annual observations appear separately, and the cumulative series use consistent reporting windows. The figures cover the designers reported by the source.

Correction

Stress-index exports use the selected weights

Previously

Changing the weights updated the chart, but exports retained the equal-weight series.

Correction

Exports now include the selected weights and component scores needed to reproduce the displayed composite. When all weights are zero, only the component series remain. The former confidence assessment was removed because it had no uncertainty model.

Correction

Unsupported supply-chain values withheld

Previously

Some relationship records included numerical values and sourcing flags that their public citations did not establish.

Correction

Those attributes are withheld from the affected records and their aggregates. A citation supporting a relationship does not by itself establish its value, volume or alternative suppliers.

Correction

Sovereign-AI funding-gap allocations withdrawn

Sovereign-AI funding-gap allocations withdrawn

Previously

The former funding-gap breakdown attributed shares of the difference between announced and disbursed funding to particular causes.

Correction

The allocations and programme gap classifications were withdrawn because the retained evidence could not reproduce them. The programme records and funding ledgers remain available.

Correction

Neocloud relationships and chart weights

Previously

The chart included unsupported relationships and weights that did not consistently describe the connections drawn.

Correction

Unsupported links were removed, and IBM was identified as a CoreWeave customer. The retained links have public citations. Card width represents the number of relationships drawn.

Related pages

Neocloud Landscape

Correction

MI350X dense-performance figures

Previously

The MI350X record used sparsity-assisted figures for dense performance.

Correction

AMD’s product brochure gives 2,309.6 TFLOPS for dense FP16/BF16, 4,614 TFLOPS for dense FP8 and 9,227.5 TFLOPS for dense FP4. The dense fields now use those values.

Related pages

Chip Classification

CorrectionInitial correction

Advanced packaging and export controls

Withdrawal: Who can stop a frontier AI run?

Previously

The compute-leverage analysis described advanced packaging as outside export controls.

Correction

BIS’s January 2025 due-diligence rule applies to advanced-chip packaging. The analysis note built around the broader claim was withdrawn on 10 August 2026.

Correction

Loughton ownership and deployment commitment

Previously

The Loughton record named CloudHQ as owner and used a 45,000-chip site-capacity ceiling as the deployment count.

Correction

The ownership and tenant attributions were corrected to Nscale and Microsoft respectively. Nscale’s September 2025 announcement committed to 23,040 GB300 GPUs for delivery in Q1 2027; the earlier ceiling referred to GB200 capacity.

Report an error

Send the page URL and the claim or value at issue to davidgringras@hsph.harvard.edu, with a supporting source where available.