<!--
Source: https://scrutica.com/entities/companies/org-alphabet/dossier
Generated: 2026-08-13T17:19:46.934Z
Format: Markdown extraction of the rendered HTML at the source URL.
For the full agent guide see: https://scrutica.com/llms-full.txt
For the MCP server see: https://scrutica.com/api/mcp
-->

# Alphabet: who controls its compute — Scrutica
## 7 control relations on record for Alphabet — all 7 by operation

Every claim below carries the document it came from, who disclosed it, and the date that disclosure speaks to. Where the record holds nothing, the page states whether the public record was searched and what was searched — an unsearched layer and an empty one are different facts.

Cite

CSVJSONJSON+Prov

PrintScreenshot

30claims on this record11 attested0 reported19 inferred0 absences with method1 not swept

The record speaks Aug 8, 2026 – Aug 11, 2026 · Control to Aug 11, 2026 · Constraint to Nov 10, 2025 · Disclosure to Aug 8, 2026. Dates are when each underlying disclosure speaks, not when it was read.

### Control

Control here means one of three things the substrate keeps apart: holding **title** to a facility, **operating** one, or holding capacity by **contract**. The three are recorded separately because an organisation can hold any one without the others, and a model built on ownership alone cannot see an organisation whose compute is entirely leased.

_Plate 1._ Control relations on record — 7scrutica.com · Aug 11, 2026

title0Owns the facility, or holds its ground lease.

No titled ownership in the record as gathered.

operation7Runs the facility day to day.

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-midlothian-operates-2026-dc3d92 "Link to this claim")

Company statement by the subject · [Google Midlothian](/facilities/fac-epoch-google-midlothian) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-midlothian-operates-2026-dc3d92`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-midlothian-operates-2026-dc3d92,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-midlothian-operates-2026-dc3d92; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-midlothian-operates-2026-dc3d92): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-omaha-operates-2026-67a459 "Link to this claim")

Company statement by the subject · [Google Omaha](/facilities/fac-epoch-google-omaha) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-omaha-operates-2026-67a459`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-omaha-operates-2026-67a459,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-omaha-operates-2026-67a459; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-omaha-operates-2026-67a459): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-papillion-operates-2026-a6db2c "Link to this claim")

Company statement by the subject · [Google Papillion](/facilities/fac-epoch-google-papillion) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-papillion-operates-2026-a6db2c`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-papillion-operates-2026-a6db2c,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-papillion-operates-2026-a6db2c; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-papillion-operates-2026-a6db2c): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-red-oak-operates-2026-712367 "Link to this claim")

Company statement by the subject · [Google Red Oak](/facilities/fac-epoch-google-red-oak) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-red-oak-operates-2026-712367`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-red-oak-operates-2026-712367,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-red-oak-operates-2026-712367; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-red-oak-operates-2026-712367): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-storey-county-operates-2026-1a7e2b "Link to this claim")

Company statement by the subject · [Google Storey County](/facilities/fac-epoch-google-storey-county) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-storey-county-operates-2026-1a7e2b`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-storey-county-operates-2026-1a7e2b,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-storey-county-operates-2026-1a7e2b; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-storey-county-operates-2026-1a7e2b): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-google-the-dalles-operates-2026-ab8181 "Link to this claim")

Company statement by the subject · [Google The Dalles](/facilities/fac-epoch-google-the-dalles) · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-google-the-dalles-operates-2026-ab8181`

Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-google-the-dalles-operates-2026-ab8181,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-google-the-dalles-operates-2026-ab8181; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-google-the-dalles-operates-2026-ab8181): https://datacenters.google/locations/

Operatesheld in own namecapacity not disclosed[§](#ctrl-alphabet-self-org-level-operates-2026-a0515f "Link to this claim")

Company statement by the subject · as of Aug 11, 2026

Receipt

> “We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”

Instrument `company_statement` · disclosed by the subject · authority tier 2 · claim id `ctrl-alphabet-self-org-level-operates-2026-a0515f`

site: US operated sites without a wired facilities row (12 listed) — Google's official data-center locations page lists the site as active (not 'in development'). The page is a living, undated document: as\_of records the sweep's access date (2026-08-11), explicitly NOT a publication date the page does not carry. Sites, verbatim as the page lists them: Central Ohio; Council Bluffs, IA; Douglas County, GA; Ellis County, TX; Henderson, NV; Indiana; Jackson County, AL; Lenoir, NC; Mayes County, OK; Montgomery County, TN; Northern Virginia; The Lowcountry, SC. Wiring residue: Central Ohio spans two Epoch rows (Columbus, New Albany); Council Bluffs and Mayes County have campus-specific Epoch rows ('Council Bluffs East', 'Pryor North') the page's coarser labels were not asserted onto.

[Primary source ↗](https://datacenters.google/locations/)

Cite this claim

@misc{scrutica-ctrl-alphabet-self-org-level-operates-2026-a0515f,
  title = {Company statement disclosing Alphabet operates},
  year = {2026},
  howpublished = {\\url{https://datacenters.google/locations/}},
  note = {Compiled in the Scrutica control ledger, claim ctrl-alphabet-self-org-level-operates-2026-a0515f; disclosure dated 2026-08-11}
}

Company statement disclosing Alphabet operates (2026). Retrieved via the Scrutica control ledger (claim ctrl-alphabet-self-org-level-operates-2026-a0515f): https://datacenters.google/locations/

contract0Holds capacity by lease, offtake, colocation, or reservation.

No contractual control in the record as gathered.

_Plate 1._ One row per relation in the control-relations substrate; the three bands are the substrate’s own classes and all three draw whether or not they hold rows. Every capacity figure carries its measurement basis, every row carries who disclosed it and through what instrument, and the receipt under each row holds the verbatim span, the primary link, and a per-claim citation. Rows are facts about the gathered record, not a census of the subject’s arrangements.

_Plate 3._ Who put this record on the recordscrutica.com

Disclosed by7Through7

Disclosed bythe subject **7**

ThroughCompany statement **7**

_Plate 3._ Every claim on the control ledger entered the public record through somebody’s disclosure. The upper strip decomposes the 7 claims by who disclosed — the subject itself, a counterparty to the relation, a regulator, or a third party — and the lower strip by the instrument that carried it. Segment widths are claim counts over the same 7\-claim total, and every segment’s count is listed beneath its strip.

_Plate 4._ The subject in the tracked universescrutica.com

Alphabet7

title operation contract

_Plate 4._ One bar per organization carrying control relations in the substrate — 16 today — stacked by relation class and ordered by relation count. Only the subject’s bar is named: the figure places one organization’s control profile inside the distribution of what the substrate has gathered. The distribution reflects the state of that gathering as much as the state of the industry.

Across the 16 organisations carrying control relations in this substrate, 7 hold contractual capacity without a single titled facility on record. That pattern is what the three-way split exists to make visible: an attribution model keyed on ownership records the 7 as holding nothing.

### Constraint

What regime the organisation sits under, and whether any export-control designation in the Federal-Register-anchored list held here reaches it. A quiet result is reported as a check with its date rather than left as silence.

Jurisdiction

The organization record places this company’s headquarters in the United States, on the strength of the company’s own published statements cited there.

Designations

No export-control designation is linked to this organization. The cross-reference that would carry such a link resolves **50 organizations** to entries on the Federal-Register-anchored lists; this organization is not among them.

The denominator is printed because a zero on its own cannot be told from a check that never ran. The lists themselves last moved on Nov 10, 2025, so a quiet result here reflects the record rather than a stalled feed.

### Disclosure posture

What the organisation itself has put on the record with the registries that ask, and which registries reach it at all. Each regime asks a different question of a different population, so each finding carries what that regime counts; nothing here is divided by anything else.

Legal entity identifierOn record

The organization holds legal entity identifier 5493006MHB84DD0ZWV18.

Registration of the entity itself in the global LEI system.

[registry record ↗](https://search.gleif.org/#/record/5493006MHB84DD0ZWV18)

Parent-reporting declarationsDeclared

Declares no consolidating parent — The organization has declared to the global LEI registry that no entity consolidates it. The chain terminates here by the registrant’s own statement, rather than running out of records.

What the registrant itself declared to the LEI registry about its consolidating parent, per parent category.

Registry reason code: `NO_KNOWN_PERSON` · as of Aug 8, 2026 · [registry record ↗](https://search.gleif.org/#/record/5493006MHB84DD0ZWV18)

Consolidation records naming this identifier as parentOn record

83 active consolidation records name this identifier as parent (33 direct, 50 ultimate). 0 of the reporting entities resolve to organizations tracked here — a boundary of this platform’s entity resolution, not of the registry’s records.

Entities holding identifiers of their own that report being consolidated into this organization’s audited accounts. Identifier adoption is uneven by jurisdiction, so this is a lower bound on structure, not a census.

as of Aug 8, 2026 · [registry record ↗](https://search.gleif.org/#/record/5493006MHB84DD0ZWV18)

SEC registrant recordNot retrieved

The organization files with the SEC (CIK 1652044); its Exhibit 21 has not been retrieved into this corpus.

Exhibit 21 lists legal subsidiaries above a materiality threshold — a threshold-bounded list, not a complete structure.

[registry record ↗](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=1652044)

### Capacity

Facilities this organisation is linked to in the substrate. Frontier-site capacity figures come from Epoch AI’s data-center catalog and are cited to them per record; where Epoch records who owns the AI hardware at a site, that is rendered as what it is — hardware ownership per Epoch — and not as facility ownership or operation.

Tracked facilities linked to Alphabet, by status, with megawatt sums and the count of facilities each sum is known for.

Status

Facilities

Capacity where recorded

operational

88

2.5 GW across the 26 of 88 with a figure

expanding

1

no capacity figures recorded

under construction

3

no capacity figures recorded

announced

9

736 MW across the 3 of 9 with a figure

Epoch frontier catalog19Sites this subject’s group is linked to in Epoch AI’s frontier data-center catalog — their measurement lane, cited per record.

[Google New Albany](/facilities/fac-epoch-google-new-albany)339 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Columbus](/facilities/fac-epoch-google-columbus)303 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Council Bluffs (East)](/facilities/fac-epoch-google-council-bluffs-east)237 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Omaha](/facilities/fac-epoch-google-omaha)237 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Papillion](/facilities/fac-epoch-google-papillion)237 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Storey County](/facilities/fac-epoch-google-storey-county)161 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google The Dalles](/facilities/fac-epoch-google-the-dalles)154 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Lincoln](/facilities/fac-epoch-google-lincoln)141 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Lancaster](/facilities/fac-epoch-google-lancaster)137 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Midlothian](/facilities/fac-epoch-google-midlothian)103 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Mesa](/facilities/fac-epoch-google-mesa)90 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Waltham Cross](/facilities/fac-epoch-google-waltham-cross)88 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Arcola](/facilities/fac-epoch-google-arcola)77 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Red Oak](/facilities/fac-epoch-google-red-oak)77 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Pryor (North)](/facilities/fac-epoch-google-pryor-north)53 MW (est.) per Epochoperational[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Goodnight](/facilities/fac-epoch-goodnight)capacity not disclosedunder construction[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Cedar Rapids](/facilities/fac-epoch-google-cedar-rapids)capacity not disclosedunder construction[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Fort Wayne](/facilities/fac-epoch-google-fort-wayne)capacity not disclosedunder construction[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

[Google Kansas City East](/facilities/fac-epoch-google-kansas-city-east)capacity not disclosedannounced[↗](https://epoch.ai/data/data-centers "Epoch catalog record")

The 101 facilities the sums above are drawn from

Every facility linked to Alphabet, with its status and recorded capacity, so each status total above can be reproduced by hand.

Facility

Status

Capacity

[Google New Albany Ohio](/facilities/fac-epoch-gc-google-new-albany-ohio)

announced

450 MW (est.)

[Google Papillion Nebraska](/facilities/fac-epoch-gc-google-papillion-nebraska)

announced

250 MW (est.)

[Google A3 VMs](/facilities/fac-epoch-gc-google-a3-vms)

announced

36 MW (est.)

[Google Council Bluff Iowa](/facilities/fac-epoch-gc-google-council-bluff-iowa)

announced

not recorded

[Google Lancaster Ohio](/facilities/fac-epoch-gc-google-lancaster-ohio)

announced

not recorded

[Google Lincoln Nebraska](/facilities/fac-epoch-gc-google-lincoln-nebraska)

announced

not recorded

[Google Omaha Nebraska](/facilities/fac-epoch-gc-google-omaha-nebraska)

announced

not recorded

[Google south Columbus Ohio](/facilities/fac-epoch-gc-google-south-columbus-ohio)

announced

not recorded

[Google Kansas City East](/facilities/fac-epoch-google-kansas-city-east)

announced

not recorded

[Google Hamina Data Center](/facilities/fac-google-hamina)

expanding

not recorded

[Google New Albany](/facilities/fac-epoch-google-new-albany)

operational

339 MW (est.)

[Google Columbus](/facilities/fac-epoch-google-columbus)

operational

303 MW (est.)

[Google Council Bluffs (East)](/facilities/fac-epoch-google-council-bluffs-east)

operational

237 MW (est.)

[Google Omaha](/facilities/fac-epoch-google-omaha)

operational

237 MW (est.)

[Google Papillion](/facilities/fac-epoch-google-papillion)

operational

237 MW (est.)

[Google Storey County](/facilities/fac-epoch-google-storey-county)

operational

161 MW (est.)

[Google The Dalles](/facilities/fac-epoch-google-the-dalles)

operational

154 MW (est.)

[Google Lincoln](/facilities/fac-epoch-google-lincoln)

operational

141 MW (est.)

[Google Lancaster](/facilities/fac-epoch-google-lancaster)

operational

137 MW (est.)

[Google Midlothian](/facilities/fac-epoch-google-midlothian)

operational

103 MW (est.)

[Google Mesa](/facilities/fac-epoch-google-mesa)

operational

90 MW (est.)

[Google Waltham Cross](/facilities/fac-epoch-google-waltham-cross)

operational

88 MW (est.)

[Google Arcola](/facilities/fac-epoch-google-arcola)

operational

77 MW (est.)

[Google Red Oak](/facilities/fac-epoch-google-red-oak)

operational

77 MW (est.)

[Google Pryor (North)](/facilities/fac-epoch-google-pryor-north)

operational

53 MW (est.)

[Google TPUv5e](/facilities/fac-epoch-gc-google-tpuv5e)

operational

24 MW

[Google Oklahoma TPU v4 Pods](/facilities/fac-epoch-gc-google-oklahoma-tpu-v4-pods)

operational

24 MW

[Gemini 1.0 Ultra training cluster A](/facilities/fac-epoch-gc-gemini-1-0-ultra-training-cluster-a)

operational

20 MW (est.)

[Magic G4 Google Cloud Rental](/facilities/fac-epoch-gc-magic-g4-google-cloud-rental)

operational

11 MW

[Google Hypercomputer TPU v5p pod](/facilities/fac-epoch-gc-google-hypercomputer-tpu-v5p-pod)

operational

10 MW

[Paper on PaLM](/facilities/fac-epoch-gc-paper-on-palm)

operational

4 MW

[Google MLPerf 0.7 Submission](/facilities/fac-epoch-gc-google-mlperf-0-7-submission)

operational

4 MW

[Google TPU v4 Pod](/facilities/fac-epoch-gc-google-tpu-v4-pod)

operational

3 MW

[Google TensorFlow Research Cloud](/facilities/fac-epoch-gc-google-tensorflow-research-cloud)

operational

3 MW (est.)

[Google TPUv3 POD Generic](/facilities/fac-epoch-gc-google-tpuv3-pod-generic)

operational

1 MW

[Paper on AlphaZero](/facilities/fac-epoch-gc-paper-on-alphazero)

operational

880 kW (est.)

[GCP Africa South 1](/facilities/fac-cloud-gcp-africa-south1)

operational

not recorded

[GCP Asia East 1](/facilities/fac-cloud-gcp-asia-east1)

operational

not recorded

[GCP Asia East 2](/facilities/fac-cloud-gcp-asia-east2)

operational

not recorded

[GCP Asia Northeast 1](/facilities/fac-cloud-gcp-asia-northeast1)

operational

not recorded

[GCP Asia Northeast 2](/facilities/fac-cloud-gcp-asia-northeast2)

operational

not recorded

[GCP Asia Northeast 3](/facilities/fac-cloud-gcp-asia-northeast3)

operational

not recorded

[GCP Asia South 1](/facilities/fac-cloud-gcp-asia-south1)

operational

not recorded

[GCP Asia South 2](/facilities/fac-cloud-gcp-asia-south2)

operational

not recorded

[GCP Asia Southeast 1](/facilities/fac-cloud-gcp-asia-southeast1)

operational

not recorded

[GCP Asia Southeast 2](/facilities/fac-cloud-gcp-asia-southeast2)

operational

not recorded

[GCP Asia Southeast 3](/facilities/fac-cloud-gcp-asia-southeast3)

operational

not recorded

[GCP Australia Southeast 1](/facilities/fac-cloud-gcp-australia-southeast1)

operational

not recorded

[GCP Australia Southeast 2](/facilities/fac-cloud-gcp-australia-southeast2)

operational

not recorded

[GCP Europe Central 2](/facilities/fac-cloud-gcp-europe-central2)

operational

not recorded

[GCP Europe North 1](/facilities/fac-cloud-gcp-europe-north1)

operational

not recorded

[GCP Europe North 2](/facilities/fac-cloud-gcp-europe-north2)

operational

not recorded

[GCP Europe Southwest 1](/facilities/fac-cloud-gcp-europe-southwest1)

operational

not recorded

[GCP Europe West 1](/facilities/fac-cloud-gcp-europe-west1)

operational

not recorded

[GCP Europe West 10](/facilities/fac-cloud-gcp-europe-west10)

operational

not recorded

[GCP Europe West 12](/facilities/fac-cloud-gcp-europe-west12)

operational

not recorded

[GCP Europe West 2](/facilities/fac-cloud-gcp-europe-west2)

operational

not recorded

[GCP Europe West 3](/facilities/fac-cloud-gcp-europe-west3)

operational

not recorded

[GCP Europe West 4](/facilities/fac-cloud-gcp-europe-west4)

operational

not recorded

[GCP Europe West 6](/facilities/fac-cloud-gcp-europe-west6)

operational

not recorded

[GCP Europe West 8](/facilities/fac-cloud-gcp-europe-west8)

operational

not recorded

[GCP Europe West 9](/facilities/fac-cloud-gcp-europe-west9)

operational

not recorded

[GCP Middle East Central 1](/facilities/fac-cloud-gcp-me-central1)

operational

not recorded

[GCP Middle East Central 2](/facilities/fac-cloud-gcp-me-central2)

operational

not recorded

[GCP Middle East West 1](/facilities/fac-cloud-gcp-me-west1)

operational

not recorded

[GCP North America Northeast 1](/facilities/fac-cloud-gcp-northamerica-northeast1)

operational

not recorded

[GCP North America Northeast 2](/facilities/fac-cloud-gcp-northamerica-northeast2)

operational

not recorded

[GCP North America South 1](/facilities/fac-cloud-gcp-northamerica-south1)

operational

not recorded

[GCP South America East 1](/facilities/fac-cloud-gcp-southamerica-east1)

operational

not recorded

[GCP South America West 1](/facilities/fac-cloud-gcp-southamerica-west1)

operational

not recorded

[GCP US Central 1](/facilities/fac-cloud-gcp-us-central1)

operational

not recorded

[GCP US East 1](/facilities/fac-cloud-gcp-us-east1)

operational

not recorded

[GCP US East 4](/facilities/fac-cloud-gcp-us-east4)

operational

not recorded

[GCP US East 5](/facilities/fac-cloud-gcp-us-east5)

operational

not recorded

[GCP US South 1](/facilities/fac-cloud-gcp-us-south1)

operational

not recorded

[GCP US West 1](/facilities/fac-cloud-gcp-us-west1)

operational

not recorded

[GCP US West 2](/facilities/fac-cloud-gcp-us-west2)

operational

not recorded

[GCP US West 3](/facilities/fac-cloud-gcp-us-west3)

operational

not recorded

[GCP US West 4](/facilities/fac-cloud-gcp-us-west4)

operational

not recorded

[Google: Arcola 2](/facilities/fac-im3-google-arcola-2-va)

operational

not recorded

[Google Data Center The Dalles Oregon](/facilities/fac-im3-google-data-center-the-dalles-oregon-or)

operational

not recorded

[Google Data Center](/facilities/fac-im3-google-data-center-va)

operational

not recorded

[Google Datacenter - Douglas County](/facilities/fac-im3-google-datacenter-douglas-county-ga)

operational

not recorded

[Google Fiber](/facilities/fac-im3-google-fiber-ga)

operational

not recorded

[Google](/facilities/fac-im3-google-sc)

operational

not recorded

[Google - Thornton](/facilities/fac-im3-google-thornton-co)

operational

not recorded

[SPC3A](/facilities/fac-im3-spc3a-tn)

operational

not recorded

[Google Datacenter Middenmeer](/facilities/fac-osm2-w1138948050)

operational

not recorded

[Google Lockbourne, OH](/facilities/fac-osm2-w1281982556)

operational

not recorded

[Google: Lok Yang 1](/facilities/fac-osm2-w1460863652)

operational

not recorded

[SPC4A](/facilities/fac-osm2-w1470261550)

operational

not recorded

[Google Data Center Fredericia](/facilities/fac-osm2-w436766762)

operational

not recorded

[Google Berkeley County Data Center](/facilities/fac-osm2-w626226408)

operational

not recorded

[Stonewall Creek Business Park](/facilities/fac-osm2-w706726088)

operational

not recorded

[Google Montgomery Data Center](/facilities/fac-osm2-w708931343)

operational

not recorded

[Google Jackson County Data Center](/facilities/fac-osm2-w714889192)

operational

not recorded

[Google Datacentre Waltham Cross](/facilities/fac-osm2-w795170874)

operational

not recorded

[Google Datacenter Eemshaven](/facilities/fac-osm2-w956325143)

operational

not recorded

[Goodnight](/facilities/fac-epoch-goodnight)

under construction

not recorded

[Google Cedar Rapids](/facilities/fac-epoch-google-cedar-rapids)

under construction

not recorded

[Google Fort Wayne](/facilities/fac-epoch-google-fort-wayne)

under construction

not recorded

19 of the 101 linked facilities are in Epoch’s frontier catalog, carrying 2.4 GW between them. Sums cover only the facilities with a recorded figure; the count of those is printed beside each row of the table above, because a megawatt total whose denominator is invisible reads as a census when it is a partial sum.

### Supply

This layer publishes what is known about the completeness of the supply picture, not the picture itself. Some supply records here were established with reference to subscription corporate-data sources that cannot be republished, so what renders is the epistemic state — position in a distribution, a corroboration class, whether a contradiction was found — and never a relationship, a counterparty, or a count from those sources.

Some records behind this layer were established with reference to subscription corporate-data sources that cannot be republished. What renders here is the epistemic state — position in a distribution, a corroboration class, whether a contradiction was found — and never a relationship, a counterparty or a count from those sources.

Position in the tracked graph

This organization’s supply-relationship count sits above the **99th percentile** of the 5,088 organizations in the tracked supply graph. The underlying counts and distribution ride subscription-licensed rows and are not published; the percentile band is the disclosure (see the sourcing note below).

Corroboration of the control ledger

The control ledger names no counterparty pairs to check against the supply corpus, so no corroboration class is derivable.

Contradiction check

No contradiction between the subscription-licensed corpus and the public-record claims rendered on this page was found in the review of Aug 12, 2026. Where such a contradiction is found, the public claim renders here with a flag that conflicting subscription evidence exists — the flag is the maximum disclosure.

### Working detail — grades, sources, and what is withheld

#### 1 · How claims are graded

No confidence value is stored anywhere. Each grade is derived when the page renders from three recorded facts — the authority tier of the source, who disclosed it, and whether the value is flagged as an estimate — so a grade cannot disagree with the claim it sits beside.

Attested Stated in a primary or research-grade record by the subject, a counterparty to the relation, or a regulator.

Reported Carried by press or third-party reporting rather than a party’s own record.

Inferred Derived or estimated — including ceilings a party states as “up to” figures.

An estimate outranks its source: a ceiling stated in a counterparty’s own press release (“up to 5 GW”) grades inferred, because the number is a bound and not a measurement.

#### 2 · Where each layer reads

**Control.** `control_relations` only — never a facility’s owner or operator column. Those columns carry, for catalog rows, a copy of the hardware-owner field whose own published definition disclaims facility ownership and operation, so they were retired as attribution sources.

**Constraint.** Export-control designations anchored to Federal Register citations, the platform’s designation-to-organisation cross-reference, and rule-derived country access classifications.

**Disclosure posture.** The Global LEI Foundation golden copy — registration, parent-reporting declarations, and consolidation records — read by the organisation’s own identifier, plus its SEC registrant record where one exists.

**Capacity.** The facilities substrate, with Epoch AI cited per record for catalog rows.

#### 3 · How absence is recorded

Three states, kept apart everywhere on this page. **Rows**: the record holds claims. **Searched, nothing admissible**: a search was run, its method and date are printed, and what it found could not be reduced to a citable primary. **Not swept**: no search is on file.

Collapsing the last two would let a budget limit read as a finding about the world. A lead that cannot be traced to a document is recorded as a lead, never as a row.

#### 4 · What is not published, and why

Some records here were established with reference to subscription corporate-data sources that cannot be republished. Where that applies, the published record cites the public primary that establishes it; the subscription source informed only which records to seek and how complete we believe the result to be. No subscription-sourced record, identifier or value is served by this site.

That is why the supply layer publishes a percentile band rather than a count, and a corroboration class rather than a list. Those forms cannot be inverted back into the underlying rows, which is the property that makes them publishable at all.

Everywhere else on this page, a derived figure prints the operands it was computed from.

The four records in this instrument were chosen to span the cases the substrate has to handle: compute held only by contract, compute held by title, compute held by operation, and an organisation the public record barely reaches. Other organisations have [directory entries](/entities/companies); a record like this one exists where the control layer has been swept.