Alphabet
Control of this organisation’s compute: the terms, the constraints, and what the public record does not show, with every claim carrying the disclosure it came from.
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.
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.
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
Receipt
“We own and operate data centers around the world to keep our products running 24 hours a day, seven days a week.”
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.
@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/
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.
The organization record places this company’s headquarters in the United States, on the strength of the company’s own published statements cited there.
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.
The organization holds legal entity identifier 5493006MHB84DD0ZWV18.
Registration of the entity itself in the global LEI system.
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 ↗
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 ↗
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.
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.
| 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 |
The 101 facilities the sums above are drawn from
| Facility | Status | Capacity |
|---|---|---|
| Google New Albany Ohio | announced | 450 MW (est.) |
| Google Papillion Nebraska | announced | 250 MW (est.) |
| Google A3 VMs | announced | 36 MW (est.) |
| Google Council Bluff Iowa | announced | not recorded |
| Google Lancaster Ohio | announced | not recorded |
| Google Lincoln Nebraska | announced | not recorded |
| Google Omaha Nebraska | announced | not recorded |
| Google south Columbus Ohio | announced | not recorded |
| Google Kansas City East | announced | not recorded |
| Google Hamina Data Center | expanding | not recorded |
| Google New Albany | operational | 339 MW (est.) |
| Google Columbus | operational | 303 MW (est.) |
| Google Council Bluffs (East) | operational | 237 MW (est.) |
| Google Omaha | operational | 237 MW (est.) |
| Google Papillion | operational | 237 MW (est.) |
| Google Storey County | operational | 161 MW (est.) |
| Google The Dalles | operational | 154 MW (est.) |
| Google Lincoln | operational | 141 MW (est.) |
| Google Lancaster | operational | 137 MW (est.) |
| Google Midlothian | operational | 103 MW (est.) |
| Google Mesa | operational | 90 MW (est.) |
| Google Waltham Cross | operational | 88 MW (est.) |
| Google Arcola | operational | 77 MW (est.) |
| Google Red Oak | operational | 77 MW (est.) |
| Google Pryor (North) | operational | 53 MW (est.) |
| Google TPUv5e | operational | 24 MW |
| Google Oklahoma TPU v4 Pods | operational | 24 MW |
| Gemini 1.0 Ultra training cluster A | operational | 20 MW (est.) |
| Magic G4 Google Cloud Rental | operational | 11 MW |
| Google Hypercomputer TPU v5p pod | operational | 10 MW |
| Paper on PaLM | operational | 4 MW |
| Google MLPerf 0.7 Submission | operational | 4 MW |
| Google TPU v4 Pod | operational | 3 MW |
| Google TensorFlow Research Cloud | operational | 3 MW (est.) |
| Google TPUv3 POD Generic | operational | 1 MW |
| Paper on AlphaZero | operational | 880 kW (est.) |
| GCP Africa South 1 | operational | not recorded |
| GCP Asia East 1 | operational | not recorded |
| GCP Asia East 2 | operational | not recorded |
| GCP Asia Northeast 1 | operational | not recorded |
| GCP Asia Northeast 2 | operational | not recorded |
| GCP Asia Northeast 3 | operational | not recorded |
| GCP Asia South 1 | operational | not recorded |
| GCP Asia South 2 | operational | not recorded |
| GCP Asia Southeast 1 | operational | not recorded |
| GCP Asia Southeast 2 | operational | not recorded |
| GCP Asia Southeast 3 | operational | not recorded |
| GCP Australia Southeast 1 | operational | not recorded |
| GCP Australia Southeast 2 | operational | not recorded |
| GCP Europe Central 2 | operational | not recorded |
| GCP Europe North 1 | operational | not recorded |
| GCP Europe North 2 | operational | not recorded |
| GCP Europe Southwest 1 | operational | not recorded |
| GCP Europe West 1 | operational | not recorded |
| GCP Europe West 10 | operational | not recorded |
| GCP Europe West 12 | operational | not recorded |
| GCP Europe West 2 | operational | not recorded |
| GCP Europe West 3 | operational | not recorded |
| GCP Europe West 4 | operational | not recorded |
| GCP Europe West 6 | operational | not recorded |
| GCP Europe West 8 | operational | not recorded |
| GCP Europe West 9 | operational | not recorded |
| GCP Middle East Central 1 | operational | not recorded |
| GCP Middle East Central 2 | operational | not recorded |
| GCP Middle East West 1 | operational | not recorded |
| GCP North America Northeast 1 | operational | not recorded |
| GCP North America Northeast 2 | operational | not recorded |
| GCP North America South 1 | operational | not recorded |
| GCP South America East 1 | operational | not recorded |
| GCP South America West 1 | operational | not recorded |
| GCP US Central 1 | operational | not recorded |
| GCP US East 1 | operational | not recorded |
| GCP US East 4 | operational | not recorded |
| GCP US East 5 | operational | not recorded |
| GCP US South 1 | operational | not recorded |
| GCP US West 1 | operational | not recorded |
| GCP US West 2 | operational | not recorded |
| GCP US West 3 | operational | not recorded |
| GCP US West 4 | operational | not recorded |
| Google: Arcola 2 | operational | not recorded |
| Google Data Center The Dalles Oregon | operational | not recorded |
| Google Data Center | operational | not recorded |
| Google Datacenter - Douglas County | operational | not recorded |
| Google Fiber | operational | not recorded |
| operational | not recorded | |
| Google - Thornton | operational | not recorded |
| SPC3A | operational | not recorded |
| Google Datacenter Middenmeer | operational | not recorded |
| Google Lockbourne, OH | operational | not recorded |
| Google: Lok Yang 1 | operational | not recorded |
| SPC4A | operational | not recorded |
| Google Data Center Fredericia | operational | not recorded |
| Google Berkeley County Data Center | operational | not recorded |
| Stonewall Creek Business Park | operational | not recorded |
| Google Montgomery Data Center | operational | not recorded |
| Google Jackson County Data Center | operational | not recorded |
| Google Datacentre Waltham Cross | operational | not recorded |
| Google Datacenter Eemshaven | operational | not recorded |
| Goodnight | under construction | not recorded |
| Google Cedar Rapids | under construction | not recorded |
| 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.
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).
The control ledger names no counterparty pairs to check against the supply corpus, so no corroboration class is derivable.
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; a record like this one exists where the control layer has been swept.