Skip to the content
Data Centers Near Me
Operating (inferred) Utah County · UT

Meta Eagle Mountain Data Center

1499 N COMMUNITY CIR

Parcel boundary

Recorded as in service.

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

Get directions
Drawn at the assessor parcel. Other campuses on record nearby are drawn around it.
Status
Operating (inferred)
Owner
Likely Meta
Capacity
48 MW directory claim
Location known to
Parcel boundary
County
Utah County
State
Utah
Electric utility
Not identified
Grid operator
CAISO

Location and nearby

Meta Eagle Mountain Data Center is on record as operating in Utah County, Utah. A directory lists its capacity at 48 MW; no filing we hold states a figure. 31 other campuses are on record within 25 miles, 8 of them within 5 miles. The nearest is 0.28 mi away.

Nearest of each kind: Operating 0.28 mi Under construction 23.7 mi Proposed 0.7 mi

Nearest campuses on record

What is on record

Owner

Likely Meta

One circumstantial signal, not a document chain.

What the signal was
  1. OSM operator tag

    Meta

    Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 · Sep 2, 2024

Filed by: Meta

Address on file
1499 N COMMUNITY CIR
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 Eagle Mountain - Building 1 · Meta Eagle Mountain - Building 2 · Meta Eagle Mountain - Building 3 · Meta Eagle Mountain - Building 4 · Meta Eagle Mountain - Building 6 and 3 more

Buildings and phases

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

Name or address Status Permit Area Date
Meta Eagle Mountain Data Center Operating not stated not stated Sep 2, 2024
Meta Eagle Mountain Data Center Operating not stated not stated Sep 2, 2024
Unnamed data center (way/1473440674) Operating not stated not stated Feb 1, 2026
Unnamed data center (way/1473440676) Operating not stated not stated Feb 1, 2026

How the status changed

  1. Operating Sep 2, 2024 inferred

    osm footprint

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

  2. Operating Sep 2, 2024 inferred

    osm footprint

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

  3. Operating Feb 1, 2026 inferred

    osm footprint

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

  4. Operating Feb 1, 2026 inferred

    osm footprint

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

  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. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

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

  10. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

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

About this data

Evidence

Primary record

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

Location known to

Parcel boundary

Matched to an assessor parcel, so the boundary is the parcel.

Independent sources

3

assessor parcel, directory, 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

11 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/1024051963 Sep 2, 2024 stated in the file
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1024051997 Sep 2, 2024 stated in the file
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1473440674 Feb 1, 2026 stated in the file
Overpass data_center query, tile conus-w2 bbox 24.0,-115.0,50.0,-105.0 US Primary osm=way/1473440676 Feb 1, 2026 stated in the file
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3080 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3081 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3082 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3083 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3085 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3086 Sep 8, 2026 retrieved by us
Utah statewide parcels (UGRC) (point queries) US-UT assessor parcel 666570001, owner of record None, match pin_on_facility Corroborating query=40.26829,-112.01508 Sep 9, 2026 retrieved by us

Cleanview (cleanview.co)

Free email alerts

Know first when a data center is recorded in Utah County

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

Explore more