Skip to the content
Data Centers Near Me
Permitted Maricopa County · AZ

QTS Glendale I

MARICOPA COUNTY, Maricopa County, Arizona

Parcel boundary

A permit or approval is on record. Construction may not have started.

Get directions
Drawn at the assessor parcel. Other campuses on record nearby are drawn around it.
Status
Permitted
Owner
QTS
Capacity
66 MW directory claim
Location known to
Parcel boundary
County
Maricopa County
State
Arizona
Electric utility
Not identified
Grid operator
not stated

Location and nearby

QTS Glendale I is on record as permitted in Maricopa County, Arizona. A directory lists its capacity at 66 MW; no filing we hold states a figure. 48 other campuses are on record within 25 miles, 7 of them within 5 miles. The nearest is 0.85 mi away.

Nearest of each kind: Operating 4.8 mi Under construction 4.1 mi Permitted 1.5 mi Proposed 0.85 mi

Nearest campuses on record

What is on record

Owner

QTS Strong

The chain
  1. assessor parcel owner of record

    QTS GLENDALE I DC12 LLC

    Maricopa County AZ Assessor parcels (point queries) · Sep 9, 2026

Filed by: QTS GLENDALE I

Capacity
66 MW as reported by cleanview, not from a filing
Diesel generators
Air permit on record AZMCA000000F050976
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
QTS GLENDALE I · QTS Phoenix 3 DC1 · QTS Phoenix 3 DC10 · QTS Phoenix 3 DC11 · QTS Phoenix 3 DC12 · QTS Phoenix 3 DC13 and 10 more

How the status changed

  1. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  2. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  3. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  4. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  5. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  6. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  7. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  8. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

    Cleanview status 'Planned'

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

  11. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  12. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  13. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

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

  14. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

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

  15. Proposed Sep 8, 2026 inferred

    Cleanview status 'Planned'

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

  16. Permitted Sep 6, 2026

    epa air permit active

    EPA ECHO Exporter, all facilities (weekly refresh)

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. The point comes from a directory, which does not say how it was derived.

Independent sources

3

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

17 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
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3889 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3890 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3891 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3892 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3893 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3894 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3895 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3896 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3897 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3898 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3899 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3900 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3901 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3902 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=3903 Sep 8, 2026 retrieved by us
EPA ECHO Exporter, all facilities (weekly refresh) US Primary REGISTRY_ID=110072129278 Sep 6, 2026 last changed on the server
Maricopa County AZ Assessor parcels (point queries) US-AZ assessor parcel 50229985, owner of record QTS GLENDALE I DC12 LLC, match owner_names_operator Corroborating query=33.51764,-112.43134 Sep 9, 2026 retrieved by us

Cleanview (cleanview.co)

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