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.

OR

State · 137 data centres recorded in OpenStreetMap

Mapped facilities
137
on the map today
Floor area
1.81
km² across 117 buildings
Share of US load
1,984
MW, inferred upper bound
Water
4.32
million gal/day, inferred
14 of these 137 are not mapped as buildings, so no power figure is estimated for them. 13 are campus boundaries covering 2.02 km² of land, and 1 is a site 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
069138201620182019202020212023202420252026
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
408
69 kV and above
Bulk substations
127
230 kV and above
Highest voltage
1100
kV, present in this state
Generating capacity
15,656
MW across 337 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. 63 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
AWS Umatilla Data CenterAmazon Web ServicesCampus boundary469,047—before 2012
Google The Dalles Data CenterGoogleCampus boundary306,284—before 2012
Google Data Center The Dalles OregonGoogleCampus boundary138,184—2016-12-16
Google Taylor Lake Data CenterGoogleCampus boundary102,280—2019-07-23
MetaMetaBuilding58,54464.22020-02-16
MetaMetaBuilding57,87763.42020-02-16
MetaMetaBuilding42,30846.42024-09-02
AppleApple Inc.Building35,06738.42017-08-21
AppleApple Inc.Building32,02035.12019-07-23
Flexential Portland - Hillsboro 3FlexentialBuilding31,33434.32021-03-23
MetaMetaBuilding30,50733.42019-07-23
Digital Realty PDX11 Data CenterDigital RealtyBuilding26,74229.32023-03-13
GoogleGoogleBuilding26,74029.32026-05-08
GoogleGoogleBuilding26,72829.32026-05-08
Amazon Web ServicesAmazon Web ServicesBuilding26,38828.92019-07-23
Digital Realty PDX11 Data CenterDigital RealtyBuilding26,29728.82021-03-21
AppleApple Inc.Building25,56928.02024-04-26
Amazon Web ServicesAmazon Web ServicesBuilding25,23227.62021-04-05
MetaMetaBuilding25,05127.52016-12-16
Amazon Web ServicesAmazon Web ServicesBuilding24,84727.22016-12-16
Amazon Web ServicesAmazon Web ServicesBuilding24,49626.92019-06-15
Amazon Web ServicesAmazon Web ServicesBuilding24,23026.62019-07-23
NTT RagingWire DC - HillsboroNTTBuilding24,18626.52021-03-23
Percheron DCRowan Green Data LLCCampus boundary23,392—2026-04-21
Percheron DCRowan Green Data LLCCampus boundary23,391—2026-04-21
Percheron DCRowan Green Data LLCCampus boundary23,391—2026-04-21
Percheron DCRowan Green Data LLCCampus boundary23,390—2026-04-21
MetaMetaBuilding22,40724.62024-09-02
MetaMetaBuilding21,53823.62016-12-16
Amazon Web ServicesAmazon Web ServicesBuilding21,12423.12023-05-31
Amazon Web ServicesAmazon Web ServicesBuilding20,65522.62025-04-05
Amazon Web ServicesAmazon Web ServicesBuilding20,58422.62022-02-03
Amazon Web ServicesAmazon Web ServicesBuilding20,43922.42026-04-20
Amazon Web ServicesAmazon Web ServicesBuilding20,42922.42023-05-31
Amazon Web ServicesAmazon Web ServicesBuilding20,41422.42023-05-31
Amazon Web ServicesAmazon Web ServicesBuilding20,32022.32025-04-05
Amazon Web ServicesAmazon Web ServicesBuilding20,20022.12023-05-31
Amazon Web ServicesAmazon Web ServicesBuilding20,15122.12024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding20,13922.12024-02-19
Amazon Web ServicesAmazon Web ServicesBuilding20,11622.12024-02-19

“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.