Read the scope before the number.

What earns a record

A physical facility must be tied to a GPU-cloud operator or AI infrastructure developer by public documentation. A dedicated regional facility qualifies when its city is withheld, with a null city and no map pin. An operator can own the facility, lease a dedicated hall or deploy within a host campus. We include operating deployments and credible announced sites, with their status visible. Headquarters, network-only points of presence and provider-wide GPU fleets do not establish a compute deployment. Vultr’s API explicitly describes physical cloud regions; these rows cover its general cloud footprint and do not assert that GPUs are installed in every region. Applied Digital records identify the infrastructure operator where the compute tenant is unnamed.

Each record needs at least three sourced data fields beyond its name, URL and summary. We check first-party operator and facility-partner pages, technical material and filings; named local reporting can qualify a contested status. Research for this edition was checked on 2026-11-11. This is a public-evidence snapshot. Sites without sufficient public identifiers cannot be enumerated from fleet totals. Historical withdrawn or transferred projects remain visible with that status and are excluded from the construction-and-plans hub.

Evidence dates and status

“Sources checked” is when we accessed the evidence. “Evidence date” is the date of the status statement or the reporting period it describes. An undated page keeps that field empty. A construction announcement with a target opening date remains construction evidence until a source establishes commissioning.

Operational means a source explicitly describes an operating deployment, even if later phases are pending. Under construction means the evidence describes active building work. Announced means a planned commitment without verified operation. Status unconfirmed identifies an unresolved delivery question, with the reason in the record.

MW figures cannot be added together

The power column deliberately preserves the source’s scope: critical IT load, a contracted lease, total facility power, an initial phase or a full-campus ambition. Those are different measures. We do not convert gross power to IT load using an assumed PUE, attribute the host’s entire campus to a tenant, or turn planned MW into live MW.

For example, Denton’s contracted IT load differs from the host’s total campus power. Childress Horizon 1 covers a delivered phase, while Independence carries an ultimate campus ambition. The adjacent power basis and linked evidence are part of every comparison.

“Delivered MW” is populated only for an explicitly delivered or operating quantity. “Planned / contracted MW” can describe either a total commitment including delivered phases or additional expansion. The adjacent basis and scope notes define which; these columns are not additive.

GPU platforms and counts

Models and counts are included only when tied to the location. A lower bound stays a lower bound in “GPU count basis.” An expansion platform stays labelled as an expansion; a future deployment stays labelled with its target year. A model name establishes neither available inventory nor a bookable service. Missing data remains null, never zero.

Map positioning

Map pins use Open-Meteo’s geocoding API, based on GeoNames, with locality and state/province matches reviewed against the cited facility location. Each plotted record includes the exact query URL and access date. Coordinates are rounded to four decimals and identify locality centers, not facility entrances. We review country and state matches; a shared city name does not establish a location. “Near Lille” and “Narvik / Kvandal” use metro centers. Ward County, Monarch, Maryland 5C and other unresolved localities remain unplotted. We also withhold pins for industrial parks or broad metros without an exact locality match.

Nearby localities are grouped to keep the map selectable. Numbers refer to the visible index under each map; pin area has no relationship to MW or GPU count. The world map and regional plates use a simple equirectangular projection and Natural Earth public-domain land outlines at 1:110m. The illustration is decorative and is separate from the geographic map.

Coverage and unresolved locations

TensorWave remains outside this edition: its Nevada board discussion identifies a headquarters rather than a data center. Genesis Cloud could not be tied to a currently verifiable physical deployment using accessible first-party sources. Network-presence listings alone are insufficient.

CoreWeave’s published fleet total exceeds the separately identifiable sites in this dataset. We include the US and European locations we can attribute from releases, municipal material and host filings; unnamed fleet capacity is not expanded into invented rows. Nebius’s second UK region and other country-only regional labels are not counted separately without evidence distinguishing the physical site from an existing row.

Nscale Loughton remains in the current operator directory, with delivery status unconfirmed. Stargate UK is an announcement with no site allocation of the nationwide GPU commitment. Fluidstack Bosquel and Crusoe Wyoming are historical records, linked to withdrawal reporting and the operator’s transfer announcement respectively.

Corrections and commercial placement

Send a correction with a public source to hello@neocloudmap.com. We update the affected fact and its verification date. Sponsors buy the explicitly labelled placement below the home table. Sponsorship does not change sourced data, eligibility or the default alphabetical order. No record is sponsored at launch.

Reuse and source rights

Download JSON with field-level provenance or CSV for analysis. Our compilation is available under CC BY 4.0; cite Neocloud Map and the relevant record. Linked publications retain their own rights. Locality coordinates originate in GeoNames through Open-Meteo; retain that attribution when reusing them.