Useful data starts with clear boundaries.

Capacity is a staged claim.

Published national benchmarks describe the market at an aggregate level. Documented-site subtotals contain only comparable disclosures allocated to named sites. Their coverage and dates can differ. National benchmarks remain separate from map pins, site contributions and capacity charts; they are never added to the site subtotals. Compare operating-capacity measures →

The operating reconciliation also includes operator portfolios with a defined computing-power boundary. Named-site contributions are deducted from each portfolio before its remaining balance is counted. That balance stays at portfolio level without invented map locations. Different observation dates are retained, so the result is documented coverage rather than a census at one date.

Where a capacity figure’s IT boundary is inferred by reconciling several primary sources, the profile labels that inference and explains it. Approximate and minimum disclosures retain their qualifiers. A completed building with ongoing hall fit-out does not establish that its entire design capacity is operating.

Megawatts (MW) measure electrical power. Our capacity totals cover power for servers, GPUs, storage and networking equipment, excluding cooling and other building overheads. The industry calls this IT power, short for information technology. We keep it separate from total facility power. Neither is a count of installed GPUs, utilisation, contracted demand or capacity available to purchase. A design specification alone does not establish that the capacity is built.

Planned projects can be at different stages of application, approval, power connection and investment. Read the project profile for the documented milestones; the planned subtotal does not imply that every project has secured approvals or finance.

Count each physical scope once.

A campus can contain multiple buildings and phases. We retain separate facility and campus records where sources distinguish them, while grouping documented shared sites. Record counts and grouped site counts are displayed separately.

We do not add ultimate campus potential to its component phases. Every contributing MW claim has a capacity scope identifier; conflicting or duplicate scopes must be reconciled before a release is accepted. Facility power and figures with an unknown power basis do not enter IT totals. Planned IT capacity includes explicitly identified proposed and approved design envelopes, including labelled upper limits. This is an inventory of development potential, not a forecast or committed supply. An upper limit never establishes built capacity and design envelopes do not enter the dated delivery outlook. A campus and its included phases are never added together. Where a source establishes a common electrical boundary, a planned remainder may be calculated by subtracting the separately identified phase; the arithmetic and source are shown in the profile.

Explore the pipeline evidence for separate grid, facility-power and MVA observations, source comparisons and projects whose power basis remains unresolved.

Filters select matching facility records and preserve all their phases. Filtering for construction therefore shows the full capacity picture at the matching sites. All views and downloads use the same release and selection.

A target date is not commissioning.

The timeline separates three kinds of evidence: documented opening or commissioning events, dated historical capacity observations, and future delivery targets. The Facilities view counts distinct physical sites with documented milestones in each year, including expansions; it is not automatically a count of brand-new facilities. The Capacity added (MW) view uses only explicitly dated, incremental computing-power additions and comparable future targets. Missing MW appears as unknown, never zero. An opening date never inherits the site’s current capacity, and a difference between disclosure snapshots is not proof of an installation. The separate historical power bars carry forward the latest disclosed value for each observed electrical boundary. These form a partial evidence series whose coverage can change, not a complete national capacity history.

Historical observations distinguish built capacity from commissioned capacity. A report publication date is labelled as a disclosure snapshot when the underlying effective date is not explicit. Month- and year-only observations plot at period end, with original precision retained in the record.

The future buildup adds only comparable, dated, incremental capacity to the disclosed operating base. It is a conditional delivery scenario assuming completion and no retirements, not a forecast. Past targets awaiting confirmation and undated proposals sit outside that future series. The separate capacity waterfall reconciles every contribution by operator, state or facility record to the headline subtotal.

Passing a target date never automatically changes a site to operating. Financial-year targets are translated only where the reporting calendar supports the conversion. Retrieval dates and publication dates are kept separate from source-effective dates; missing commissioning dates stay unknown.

Government certification has a scope.

The Australian Hosting Certification Framework (HCF) is recorded against the exact named scope in its official register. These are categories within our physical directory, not extra sites to add to the site count. Inspect the official HCF register ↗

• Certified Strategic facility: a named facility matched to a Strategic entry in the official register.
• Certified Strategic enclave: the certified scope is an enclave within a facility. It does not certify the entire building or every MW at that address.
• Cloud service: a certified service is distinct from its physical hosting sites. We do not count a cloud service as a data centre.
• All verified Strategic scopes: the union of our matched facility and enclave records. These counts are not national HCF totals.
• Not verified: we have not established a current exact match. It does not mean uncertified.
• New Zealand: Australian HCF is marked not applicable. This makes no claim about NZ assurance or sovereignty.

Browse the HCF scope register → for the named facilities and enclaves, linked Atlas profiles and any unresolved identity matches.

Certification does not establish GPU type, available supply, service-level data residency, ownership or the location where AI inference is processed.

Evidence, coverage and locations.

We prioritise operator disclosures, investor reports, government registers and planning records. Every claim links to a source with publisher, retrieval date and a page or section locator. Directory listings can establish a facility’s existence without establishing comparable capacity.

Browse the sources and research register → for the authorities we consult, operator portfolios and accepted evidence, including review dates and limitations.

Core-field coverage checks eight items equally: an identity source, city, corroborated site location, facility type, known stage, MW with a known basis, resolved certification scope, and a dated capacity claim or milestone. It is not a probability, quality rating or claim that research is complete.

“Source-listed profile” means a source supports the catalogue entry. “Directory-listed record” identifies a record whose identity still rests on a secondary directory listing, cited as a source with its retrieval date; the listing’s own text and map position are not republished. “Profile reviewed” indicates field-specific source checks. Evidence status and source dates apply to the individual fields; a profile label does not establish every capacity figure, address or future delivery date as verified.

The map shows every catalogued record with an available location by default. Solid markers use operator map points or directions, or an OpenStreetMap building or address feature matched to a published numbered street address. Each profile states the method and sources. Grey dashed city groups represent records without a more specific mapped position; they must not be used to navigate to a facility. Positions reported by commercial directories are not shown. Each evidence class can be shown or hidden separately. Marker numbers count grouped records, which can include multiple buildings or operator records at one physical site. Zooming separates nearby site markers.

Commercial directory listings are cited as sources only. The Atlas does not republish their text, specification fields or map positions, and a capacity figure, rack specification, certification or position reported by a listing is never promoted into accepted Atlas evidence. Directory figures do not add to the capacity charts. Published operator and planning evidence remains separate when sources disagree.

A site marker is not a surveyed boundary or a guarantee of an entrance location. A street-only geocoder result, map viewport centre or unconfirmed neighbouring address is insufficient. Public registry entries such as PeeringDB are research leads only; the Atlas does not republish their coordinates or treat them as evidence of capacity or commissioning. OpenStreetMap address features retain attribution to OpenStreetMap contributors and the ODbL licence in their source entries. Missing positions do not remove records from directory counts. Inspect current coverage and gaps →

Attribution and reuse.

Map tiles are served by OpenFreeMap from OpenMapTiles, built on data from OpenStreetMap contributors under the Open Database Licence. The map control carries that attribution. Address and locality points whose source entry names OpenStreetMap are also OpenStreetMap contributor data under the ODbL. Approximate city positions come from Natural Earth, which is in the public domain. The Manrope typeface is used under the SIL Open Font Licence.

Operator, government, planning and research sources remain the property of their publishers. Each claim cites its source, locator and dates; quotations are short and attributed. The Atlas’s own compiled data, research claims and text are published under the Creative Commons Attribution 4.0 licence (CC BY 4.0): reuse them freely with attribution to Accelerate AI Partners, ANZ Compute Atlas, and the release identifier. Two things are excluded from that licence: OpenStreetMap-derived points and town centroids, which carry the ODbL; and quoted or linked third-party material, including directory listings cited as sources, which stays under its publishers’ terms. The same statement travels in every release snapshot as its licence field.

Verify the field and keep its scope.

Field evidence records the question, source date and whether the cited documents support the claim, conflict with it or do not establish it. “Not found” does not prove a feature or contract is absent. A recently retrieved page can still describe an older project design.

Demand, workload, hardware and commercial evidence are separate structured claims. Each retains a geography, lifecycle, applicable date, units and limits. Portfolio totals and unnamed regional deployments are not allocated to guessed sites. Training capability is not evidence of a training run; accelerator systems, GPUs, qubits, electrical power and annual energy are distinct measures. Read the demand and compute evidence →

Versioned and open to correction.

Each accepted dataset receives a release identifier and a downloadable snapshot. Cite the facility profile, release identifier, claim and underlying source together. A source-linked subtotal is still only a subtotal of this research sample.

Suggested citation: Accelerate AI Partners, ANZ Compute Atlas, release 2026-11-03-launch-13, relevant facility profile and source, accessed on your retrieval date.

This is a dated dataset. Use the source and observation dates alongside the publication date, particularly for projects with changing designs or delivery targets. Operating status requires evidence of delivery or an explicit operating disclosure.

Public Data Center Map listings first identified many records in the Atlas. Each such record cites its listing as a source with the retrieval date; the listing’s text, specification fields and map positions are not republished, and the record’s identity, address and lifecycle are re-checked against operator, planning and news sources as research proceeds. Source publishers retain rights in their material.

Send a source or discuss a correction with Accelerate AI Partners →