Skip to the content
Data Centers Near Me
Operating (inferred) Maricopa County · AZ

Meta data center, Mesa, AZ

Maricopa County, Arizona

Building outline

Recorded as in service.

Status inferred from osm footprint (Sep 9, 2026). No filing states it in as many words.

Get directions
Drawn at the mapped building outline. Other campuses on record nearby are drawn around it.
Status
Operating (inferred)
Owner
Meta
Capacity
48 MW directory claim
Location known to
Building outline
County
Maricopa County
State
Arizona
Electric utility
Not identified
Grid operator
not stated

Location and nearby

Meta data center, Mesa, AZ is on record as operating in Maricopa County, Arizona. A directory lists its capacity at 48 MW; no filing we hold states a figure. 62 other campuses are on record within 25 miles, 20 of them within 5 miles. The nearest is 0.67 mi away.

Nearest of each kind: Operating 0.7 mi Permitted 0.7 mi Proposed 0.67 mi

Nearest campuses on record

What is on record

Owner

Meta Confirmed

The chain
  1. meta first-party locations page lists this site

    Meta

    Meta US data center locations page (first party, city-level) · Sep 9, 2026

Filed by: Meta

Capacity
48 MW as reported by cleanview, not from a filing
Diesel generators
No air permit found in the records we collect
Water
Not collected. State water withdrawal permits are not in this build.
Electric utility
More than one utility serves this county, and no filing we hold names which one
Also recorded as
Meta · Meta Mesa - Building 1 · Meta Mesa - Building 2 · Meta Mesa - Building 3 · Meta Mesa - Building 4 · Meta Mesa - Building 5 and 4 more

Buildings and phases

3 distinct buildings, parcels or permits make up this campus.

Name or address Status Permit Area Date
Unnamed data center (way/1456975947) Operating not stated not stated Dec 8, 2025
Unnamed data center (way/1456975948) Operating not stated not stated Dec 8, 2025
Unnamed data center (way/1456975949) Operating not stated not stated Dec 8, 2025

How the status changed

  1. Operating Dec 8, 2025 inferred

    osm footprint

    Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0

  2. Operating Dec 8, 2025 inferred

    osm footprint

    Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0

  3. Operating Dec 8, 2025 inferred

    osm footprint

    Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0

  4. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  5. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  6. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  7. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  8. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  9. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  10. Operating Sep 9, 2026 inferred

    Meta locations page card; city-level

    Meta US data center locations page (first party, city-level)

About this data

Evidence

Primary record

A government filing, a federal permit, an assessor parcel or the operator’s own page.

Location known to

Building outline

A mapped building outline.

Independent sources

3

directory, first party, osm footprint. Directories count once between them, because they copy each other.

How we build this

Spotted something wrong? Tell us and we will fix it.

Where this comes from

10 source records back this page. Each row is a document we retrieved and kept, so a claim can be checked against the original.

Document Role Row Date
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1456975947 Dec 8, 2025 stated in the file
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1456975948 Dec 8, 2025 stated in the file
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1456975949 Dec 8, 2025 stated in the file
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3102 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3103 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3104 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3105 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3106 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3107 Sep 8, 2026 retrieved by us
Meta US data center locations page (first party, city-level) US Primary card=Mesa Sep 9, 2026 retrieved by us

Cleanview (cleanview.co) Meta first-party locations page

Free email alerts

Know first when a data center is recorded in Maricopa County

Each time we refresh the public records and a new campus appears in Maricopa County, you get one short email naming it, with the document behind it.

Explore more