Swipe to scroll the page. Tap a marker for details below.
HighProposed
Project Blue
Pima County / Tucson, Arizona
Project Blue remains a high-priority Tucson/Pima County record because Tucson rejected the annexation and development agreement, but the county-side project continued through land, water-well, and electric-service pathways. NDA, land-sale, water, power, and public-cost records should stay visible for review.
Amazon Web Services / Beale InfrastructureConfirmed NDASource category: public agency / civic recordNo fuel-cell sourceMissing Public, Water
Data coverageVerified fields are source-backed or moderator-reviewed.
Public moneyNeeds FOIAPublic land-sale and economic-development negotiations were central to the local dispute; project-specific incentive, utility-cost, and public-benefit records still need review.
WaterNeeds FOIASource reviewed September 14, 2026: AZPM reported that Arizona water officials approved two commercial wells tied to Project Blue under three existing groundwater rights totaling 96.5 acre-feet per year. The Arizona Department of Water Resources told AZPM that annual water-use reporting is required; the article says each well was described as having 600 gallons-per-minute pumping capacity. This establishes a permitted supply path, not measured use, wastewater discharge, or proof of the developer's estimated 15,000–20,000 gallons per day once fully operational. Final well, groundwater, wastewater, and cooling records still need review.
PowerSource leadSource reviewed September 13, 2026: the Arizona Corporation Commission says it approved TEP's special electric-service agreement for Project Blue and describes an initial anticipated load of 286 MW, with additional generation beyond that amount to be paid by the data center. TEP's agreement summary says the deal also includes minimum monthly bills, financial security, and a termination fee if the project does not meet its obligations. TEP's June 2026 SEC filing says FERC approval triggered a $20 million customer advance for transmission and switchyard construction, with another $24 million expected after remaining conditions. These are approved planned utility terms and reported customer advances, not proof of energized capacity, actual operating bills, or data-center IT load.
Source reviewed September 14, 2026: AZPM reported that Arizona water officials approved two commercial wells tied to Project Blue under three existing groundwater rights totaling 96.5 acre-feet per year. The Arizona Department of Water Resources told AZPM that annual water-use reporting is required; the article says each well was described as having 600 gallons-per-minute pumping capacity. This establishes a permitted supply path, not measured use, wastewater discharge, or proof of the developer's estimated 15,000–20,000 gallons per day once fully operational. Final well, groundwater, wastewater, and cooling records still need review.
Power
Source reviewed September 13, 2026: the Arizona Corporation Commission says it approved TEP's special electric-service agreement for Project Blue and describes an initial anticipated load of 286 MW, with additional generation beyond that amount to be paid by the data center. TEP's agreement summary says the deal also includes minimum monthly bills, financial security, and a termination fee if the project does not meet its obligations. TEP's June 2026 SEC filing says FERC approval triggered a $20 million customer advance for transmission and switchyard construction, with another $24 million expected after remaining conditions. These are approved planned utility terms and reported customer advances, not proof of energized capacity, actual operating bills, or data-center IT load.
Public money
Public land-sale and economic-development negotiations were central to the local dispute; project-specific incentive, utility-cost, and public-benefit records still need review.
Confirmed NDA or major secrecy dispute Requested NDA or reported secrecy Reference / monitorAll proposed sites
29 resultsSearch by ZIP, city, county, state, operator, or project name
Methodology
Public-source tracker: 7,362 pre-merge rows in the bundled datasets, with 104 locations currently loaded after merging nearby curated records. The source files include 902 auto-promoted IM3/OSM baseline records and 1,313 FracTracker-derived records, plus 1,349 ATLAS North America location leads and 796 PeeringDB facility leads. This version also places 2,898 ATLAS backlog rows at city-level approximate coordinates when the city could be matched against an existing coordinate-backed North America record; unmatched backlog rows remain off-map until they can be placed responsibly. Public claims are separated as confirmed records, leads, submitted requests, or unresolved gaps. Reviewed dataset changes require a new build and release; no live location collector runs in this page. Source dates are available only where the linked record provides them.