Hyperscale Map

Methodology

Data as of 16 November 2026

Hyperscale Map holds 225 cloud regions from 6 providers and 231 campuses made from 638 mapped buildings. This page says where each figure comes from and what it does not tell you.

Data as of

DatasetSnapshot
Cloud regions (provider lists)16 November 2026
Meta campus list16 November 2026
OpenStreetMap buildings16 November 2026 (database timestamp 2026-11-16T06:07:14Z)
Google regional carbon data2024 values, fetched 16 November 2026

Each dataset is a single snapshot. This map does not refresh on a schedule. When a snapshot is replaced the dates above change and the data files are republished.

Sources

SourceWhat is taken
AWSRegion code, name, availability zones, country
Microsoft AzureRegion name, programmatic name, availability zones, physical location
Google CloudRegion code, zones (counted), location
Google regional carbon dataCarbon-free energy share and grid carbon intensity for 2024 (Apache-2.0)
Oracle Cloud InfrastructureRegion identifier, name, location, availability domains
Alibaba CloudRegion ID, name, number of zones
IBM CloudRegion code, name, zones
Meta data centresCampus city, state or country, break-ground year
OpenStreetMap (Overpass API)Data-centre buildings of these operators: outline, ref, power-input and start-date tags where mapped (ODbL)
OpenStreetMap NominatimCoordinates and country for published localities; locality names for campuses (ODbL)

Only facts are taken: codes, names, localities, counts, years and mapped geometry. No prose, images, commercial figures or customer information are copied.

Cloud regions

A cloud region is a provider's deployment area, usually several buildings. Each entry is one row in the provider's published list. The pin comes from geocoding the locality the provider publishes (for example "Ohio" or "Frankfurt"), so it marks that area. Where a provider names only a state or a country the pin sits at its centre and the page says so. The position is never the address of a building.

Campuses

Campuses are built from data-centre buildings tagged in OpenStreetMap whose operator or name matches one of the seven operators. Buildings of the same operator within 1 km of each other (chained building to building) form one campus. The footprint is the area of the mapped building outline. The power figure is the input:electricity tag that some mappers add. It is a contributor tag, covers only the buildings that carry it, and is not an operator disclosure. Campuses on Meta's own list are matched to a mapped Meta campus within 15 km; if none exists they appear with no mapped buildings.

OpenStreetMap coverage is uneven. A campus with few buildings may simply be mapped lightly. The counts are floors, not totals, and no campus size is implied beyond what is mapped.

Missing values

Where a source does not publish a figure the page shows a hatched "Not published" or "Not in the source" value. Capacity in megawatts is shown this way everywhere because none of the sources publish it. Nothing is estimated, interpolated or filled from a model.

What is not included

Licence

The open data files are published under the Open Database Licence 1.0 because they include information from OpenStreetMap contributors. See open data for the files and the attribution line.

Corrections

If something is wrong or a campus is missing, write to contact@atlasdevelopment.io. Mapping a missing building in OpenStreetMap is the best fix for campuses.