Prime Data Centers
Prime Data Centers develops and owns hyperscale and purpose-built data centers, with four gigawatts of operational and planned capacity across Chicago, Dallas, Los Angeles, Phoenix, Silicon Valley, Austin, Frankfurt, Berlin, Madrid and the Nordics.
Visit Prime Data Centers Compare with others Request a quote
Facts
Source per value- Model How the provider sells space. Retail: cabinets, cages and suites to many tenants, usually with interconnection. Wholesale and hyperscale: whole halls, buildings or build-to-suit campuses leased by the megawatt. Retail and wholesale: both, as the provider describes itself.
- Wholesale and hyperscale 1
- Data centers Provider-reported data center or location count. Read Count basis for buildings versus campuses, operating/development status, snapshot date and overlap. Campus-only counts use the separate Campuses field.
- Not published
- Metros Number of metros or markets the provider says it serves, as it counts them.
- Not published
- Countries Provider country coverage as published or counted from its location list; may include development and announced projects. Read Count basis and Key markets for stage and scope.
- Not published
- Key markets Flagship metros or countries named on the provider's own pages. Not a full location list: open the provider's site map for that.
- Chicago; Dallas; Los Angeles; Phoenix; Silicon Valley; Austin; Frankfurt; Berlin; Madrid; Nordics 1
- Built MW Operating capacity in megawatts as the provider publishes it, usually critical IT load. Where only a combined figure exists it goes in 'Incl. development' instead.
- Not published
- Incl. development MW Published platform scale including development, planned capacity or full build-out potential. This is not pipeline alone. Read Capacity basis for the exact definition, date and exclusions; figures are not directly comparable.
- 4,000 1
- Rack density kW/rack Published supported rack-density threshold or upper figure. Read Density basis for lower bounds, configuration and site restrictions; this is not a measured universal maximum.
- Not published
- Liquid cooling The provider offers or supports liquid cooling (direct-to-chip, rear-door heat exchangers or immersion) for colocation customers, on a page cited in the record's sources. Blank means no such offer was found on the pages read.
- Not published
- Liquid methods The liquid cooling methods the provider names: direct-to-chip, rear-door heat exchanger, immersion.
- Not published
- Interconnection The provider's interconnection offer as it names it: software-defined fabric, cloud on-ramps, internet exchanges and carrier-neutral meet-me rooms.
- Not published
- Networks on-net Carriers and networks the provider says are available across its platform (a stated '1,000+' is recorded as 1,000). Counts differ in what they include, so compare orders of magnitude.
- Not published
- Certifications Certifications and attestations the provider lists (ISO 27001, SOC 1/2, PCI DSS, HIPAA, Uptime Institute Tier and others). Coverage often varies by site; the source says which sites hold which.
- Not published
- Published price $/kW/mo Public list price per kW per month, where the provider publishes one. Converted from a per-cabinet monthly price only when the source states the cabinet's kW. Almost every provider quotes per deal, so this is usually blank.
- Not published
- Ownership Who owns the provider: a stock listing, or the named private owners from the provider's own pages, filings or the deal announcement.
- Not published
- Campuses Published campus count, separate from individual data center buildings. A campus can contain several facilities.
- Not published
- Count basis What the footprint count measures, its snapshot date where available, and any parent/platform overlap.
- Not published
- Capacity basis Exact basis and date of the MW figure: operational, leasable, construction, contracted, planned or potential. Not a measure of vacant availability.
- 4 GW operational and planned capacity in the March 2026 company release. No operating/construction split; not construction-only pipeline. 1
- Platform overlap Parent, subsidiary or joint-venture relationships relevant to avoiding double counting. Directory row counts are not independent operator totals.
- Not published
- Density basis Scope, configuration and threshold qualification of the published kW per rack figure.
- Not published
- Deployment example A sourced facility example with its own scope, kept separate from platform capacity totals.
- Not published
Sources
- Prime: March 2026 operational and planned platform capacity accessed 2026-11-11
Get a quote from Prime Data Centers and similar providers
Tell us what you need once. We send it to matching providers and they reply to you directly.