HELIOSOpen AI Infrastructure Observatory
Static snapshot. This site serves two different things: 1,853 data centres reported by OpenStreetMap contributors nationwide, and 13 sites Helios infers from Arizona parcel records, exported on July 29, 2026. The first is a map of what has been recorded; the second is an argued hypothesis with an evidence chain. This is a point-in-time export, not a live view. See meta.json or the methodology.

OH

State · 95 data centres recorded in OpenStreetMap

Mapped facilities
95
on the map today
Floor area
1.38
km² across 81 buildings
Share of US load
1,509
MW, inferred upper bound
Water
3.28
million gal/day, inferred
13 of these 95 are not mapped as buildings, so no power figure is estimated for them. 8 are campus boundaries covering 3.23 km² of land, and 5 are sites mapped as under construction. The megawatt figure above divides a national total by building floor area, and the area of a land parcel is not floor area. A site still being built consumed none of the electricity that total measures. Both are counted here and left out of the estimate rather than folded into it, so this region's load is understated by however much those represent.

When these appeared on the map

observed, not surveyed
04895201620182019202020212023202420252026
Data centres recorded in OpenStreetMap at the end of each month. The hatched stretch is before 2017-01, when telecom=data_center was not yet in common use — the near-zero readings there describe the tag, not the country. This is a count of what has been mapped, and OpenStreetMap carries no construction dates.

What the grid here looks like

reported by OSM contributors
Substations
1,882
69 kV and above
Bulk substations
118
230 kV and above
Highest voltage
765
kV, present in this state
Generating capacity
30,643
MW across 292 plants

A facility drawing hundreds of megawatts connects at bulk transmission voltage, so the second figure matters more than the first: forty 69 kV yards are not a substitute for one 500 kV substation. 137 of the plants here carry no capacity tag, so the megawatt total is a floor rather than the region's output.

Proximity is not connection. Nothing here shows that any facility has contracted power from any of these substations. That gets settled in interconnection filings Helios cannot read, and in several regions those queues now run for years. A county showing no substations may have none mapped rather than none standing.

Largest named mapped records

by mapped area
NameOperatorMapped asMapped area m²Share MWFirst mapped
Meta Bowling Green Data Centernot recordedUnder construction1,997,251—2025-11-29
Google New Albany Data CenterGoogleCampus boundary1,616,081—2025-08-26
Google Lockbourne, OHGoogleUnder construction1,065,016—2024-09-09
Meta LCO 3 ProjectMetaUnder construction1,042,161—2026-03-21
Meta New Albany Data CenterMetaCampus boundary924,772—2026-03-21
Amazon AWS: Hilliard Data CenterAmazon Web Services us-east-2 datacenterCampus boundary239,550—2016-12-16
CyrusOne Cincinnati-Hamilton CIN4CyrusOneCampus boundary143,408—2024-12-27
Amazon New Albany: Jug and Beach Roadnot recordedUnder construction141,644—2024-12-27
Amazon Web Services Datacenter ComplexAmazon Web ServicesCampus boundary102,780—2016-12-16
T5@ClevelandT5 Data CentersCampus boundary90,561—2025-02-09
NAO 1/NAO 2MetaBuilding61,61767.52020-09-04
NAO 5/NAO 6MetaBuilding56,55662.02024-02-19
STACK New Albanynot recordedCampus boundary52,331—2023-11-24
NAO 3MetaBuilding33,99537.32020-09-04
LCO 1MetaBuilding33,96137.22025-05-13
LCO 2MetaBuilding28,25331.02025-05-13
GoogleGoogleBuilding27,10629.72026-04-19
GoogleGoogleBuilding26,93029.52024-02-19
GoogleGoogleBuilding26,87229.42024-02-19
Google NBY-3GoogleBuilding26,78829.42024-02-19
Google NBY-6GoogleBuilding26,71729.32025-05-13
Google NBY-5GoogleBuilding26,66429.22025-05-13
Google NBY-4GoogleBuilding26,64529.22024-02-19
Google NBY-7GoogleBuilding25,11827.52025-09-07
Vantage Building 1VantageBuilding22,80325.02025-09-07
T5@ClevelandT5 Data CentersBuilding22,73624.92025-04-29
Vantage Building 2VantageBuilding22,08624.22025-09-07
Amazon Web ServicesAmazon Web ServicesBuilding21,70323.82024-05-06
QTS NAL1 DC2Quality Technology ServicesBuilding21,06223.12025-08-26
QTS NAL1 DC1Quality Technology ServicesBuilding20,91422.92025-08-26
Vantage Building 3VantageBuilding20,66622.62025-09-07
Amazon Web ServicesAmazon Web ServicesBuilding20,49322.52024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding20,25622.22024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding20,24622.22025-05-13
Amazon Web ServicesAmazon Web ServicesBuilding20,08522.02025-05-13
Amazon Web ServicesAmazon Web ServicesBuilding19,91221.82024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding19,90621.82024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding19,88921.82025-05-13
Amazon Web ServicesAmazon Web ServicesBuilding19,83721.72025-05-13
Amazon Web ServicesAmazon Web ServicesBuilding19,79921.72025-05-13

“First mapped” is when OpenStreetMap recorded the facility, not when it was built — OpenStreetMap carries no construction dates. Mapped area means a building floor plate, campus boundary, or construction polygon according to the “Mapped as” column; those quantities are never added together. The megawatt column appears only for buildings and is their floor-area share of a reported national total, not a measurement.