ECO TERRAVAULT INTELLIGENCE
Explore the data-center landscape across the United States and its territories. Trace public evidence. Understand what is known—and what still needs investigation.
A public research workspace.
Built for informed infrastructure decisions.
56 jurisdictions · Professional insight
01 / GEOGRAPHIC EXPLORER
Compare the documented footprint across states and territories. Each layer has its own source, date, and counting unit.
Compute Atlas v1.34.0 · Sep 21, 2026. Source-reported site/campus records. Campus and individual-site records may overlap; totals are records, not unique physical facilities. No live operational verification.
Generalized Census boundaries. Alaska, Hawaii, and territories appear as insets. No records means a gap in this layer, not an absence of facilities or issues. U.S. Minor Outlying Islands are outside these datasets.
LIFECYCLE CONTEXT
Reported by Compute Atlas as of its snapshot. “Operational” is a source classification, not an uptime check. Dormant and decommissioned stages are not tracked in this catalog.
FROM INFORMATION TO ACTION
Use public evidence to frame the next investigation. Site conditions, available capacity, water requirements, and recovery readiness need project-specific validation.
02 / FACILITY RESEARCH
A searchable catalog of source-reported data-center sites and campuses. Crypto-only facilities and dedicated power-generation records are excluded.
Snapshot: Sep 21, 2026 · v1.34.0. Status and confidence labels are inherited from Compute Atlas; Eco TerraVault has not independently verified every facility. Campus and individual-site records may overlap; totals are records, not unique physical facilities.
0 matching records · All jurisdictions
Try another area, stage, or search term. This is not evidence that no data centers exist there.
03 / REPORTED EVENTS & LIFECYCLE
Selected public postmortems, operator statements, and government records. Every report keeps its date, scope, and original source.
This is an initial research collection, not a systematic incident database. No report does not mean no issue. Regional service events are not attributed to individual buildings. A past incident does not establish a facility’s current condition.
15 reviewed reports · All jurisdictions
Cloudflare reported that a power interruption at a Portland-area facility disrupted its control-plane and analytics services. Its account says customer traffic-processing services continued operating and affected services were restored by November 4.
Historical customer postmortem, not a statement of current facility condition or all tenants' experience. The report includes preliminary explanations; this record does not assign fault or repeat speculative root causes.
Published: Nov 4, 2023 · Reviewed: Sep 27, 2026 · Facility / deployment: Cloudflare deployment at a Portland-area facility
Cloudflare reported a power interruption affecting its Portland PDX01 deployment. It said APIs and dashboards returned to normal within minutes through failover, while analytics recovered later that day; customer traffic processing was not affected.
Historical service-provider account of its own deployment. It does not establish present facility reliability, current unresolved issues, or impact on every tenant.
Published: Apr 8, 2024 · Reviewed: Sep 27, 2026 · Facility / deployment: Cloudflare PDX01 deployment, Portland area
AWS published a post-event explanation of network congestion that impaired services in its Northern Virginia region on December 7, 2021, including dependencies used by service-management functions.
A historical regional service event. The source does not identify an individual building, and this record must not be attached to every AWS facility in Virginia or shown as an active outage.
Published: Dec 10, 2021 · Reviewed: Sep 27, 2026 · Facility / deployment: AWS US-EAST-1 region (individual facility not identified)
Google reported that loss of power to affected racks and a failed transition to backup power disrupted several services in us-east4-a. Its incident report describes service recovery after power restoration, with follow-up work for a small subset of customers.
Historical zonal service report; the precise building is not named. The report's limited affected scope must not become a claim that the whole Northern Virginia region or all Google facilities lost power.
Published: Nov 8, 2023 · Reviewed: Sep 27, 2026 · Facility / deployment: Google Cloud us-east4-a zone, Northern Virginia (building not identified)
Google's incident report describes increased latency and errors across multiple services in us-central1 after a router restarted with an outdated configuration during maintenance. Google reported restoration of the correct routes and recovery that day.
Historical regional service event, not a physical-building failure or current outage. The publication date refers to the full incident report; initial status notices were posted earlier.
Published: Sep 6, 2022 · Reviewed: Sep 27, 2026 · Facility / deployment: Google Cloud us-central1 region, Iowa (building not identified)
Microsoft reported that a Texas storm caused utility-voltage disturbances that affected cooling and prompted a protective hardware shutdown. Its VSTS postmortem describes regional service interruption and wider dependency effects, with the VSTS incident ending September 6.
Historical postmortem about VSTS and its Azure dependencies. It is not a current condition assessment or evidence that every facility in Texas was affected; the source does not identify a specific building.
Published: Sep 10, 2018 · Reviewed: Sep 27, 2026 · Facility / deployment: Azure South Central US region (individual facility not identified)
The Department of Veterans Affairs' FY 2027 capital plan lists closure of its Sacramento Regional Data Center in 2023 as a completed space-reduction action.
The source documents closure, not demolition or the full physical decommissioning process. No exact closure day or present building use is established. Sacramento is in California; VA here names the federal department.
Published: FY 2027 congressional budget submission, available in 2026 · Reviewed: Sep 27, 2026 · Facility / deployment: Sacramento Regional Data Center
DOE's 2011 sustainability plan states that the Kansas City Plant had decommissioned three named data centers: SEL, EDSV and the Enterprise Computer Room. A separate DOE audit identifies the plant's location as Kansas City, Missouri.
One research record describes a group of three historical data centers; it is not three independently geolocated facility records. This does not establish the condition or current use of the former rooms or later Kansas City facilities.
Published: 2011 · Reviewed: Sep 27, 2026 · Facility / deployment: Kansas City Plant: SEL, EDSV and Enterprise Computer Room
Meta announced that its DeKalb data center was online and serving traffic. The announcement establishes an operating milestone, while also discussing future full operation of the development.
Status is attributed to the dated operator announcement, not independently monitored today. Serving traffic does not prove every planned campus building or phase was completed on that date.
Published: Nov 29, 2023 · Reviewed: Sep 27, 2026 · Facility / deployment: DeKalb Data Center
Iron Mountain's location page lists WPA-1 in Boyers, Pennsylvania as an underground colocation facility in a former limestone mine.
Operating is an operator-listed status observed on the review date, not an independent real-time check. Marketing claims about protection, efficiency or certification are not independently verified by this record.
Published: Date not stated · Reviewed: Sep 27, 2026 · Facility / deployment: WPA-1 Pennsylvania Data Center, Boyers
GTA lists GU1 and GU2 as data centers and cable landing stations offering carrier-neutral colocation in Guam. They are grouped here because the cited page describes them together.
An operator-listed observation, not a real-time operations check or a territorial total. This selected research record groups GU1 and GU2 as described together by the cited page; it is not GTA's complete facility inventory.
Published: Date not stated · Reviewed: Sep 27, 2026 · Facility / deployment: GTA GU1 and GU2 Data Centers
The Virgin Islands Energy Office's 2024 plan lists a St. Croix Data Center among government information-technology infrastructure and identifies the Bureau of Information Technology's role in government data and voice services.
The source establishes a named infrastructure listing, not a dated commissioning event, live operating status, capacity, incident history or exact building location.
Published: 2024 plan (file hosted in January 2025) · Reviewed: Sep 27, 2026 · Facility / deployment: St. Croix Data Center
The Virgin Islands Energy Office's 2024 plan lists a St. Thomas Data Center among government information-technology infrastructure and identifies the Bureau of Information Technology's role in government data and voice services.
The source establishes a named infrastructure listing, not a dated commissioning event, live operating status, capacity, incident history or exact building location.
Published: 2024 plan (file hosted in January 2025) · Reviewed: Sep 27, 2026 · Facility / deployment: St. Thomas Data Center
A Puerto Rico Public Buildings Authority procurement notice describes replacement of communications equipment for existing information systems at the Minillas government data center in San Juan.
Evidence of a documented facility and procurement scope, not proof that the works were awarded or completed, an operating-status audit, or an unresolved failure. This record omits street-level access and equipment details.
Published: Date not stated · Reviewed: Sep 27, 2026 · Facility / deployment: Centro de Datos e Información Digital, Centro Gubernamental Roberto Sánchez Vilella, San Juan
An ASTCA infrastructure presentation hosted by the U.S. Department of the Interior proposes moving cable-landing infrastructure to the ASTCA headquarters building, describing it as designed for data-center operations.
Planning evidence only. This is a supporting-infrastructure proposal, not proof of a new completed data center, subsequent commissioning, present operating status or an additional facility count.
Published: Presentation dated March 28, 2022; upload date not established · Reviewed: Sep 27, 2026 · Facility / deployment: ASTCA proposed cable-landing and technical-operations relocation
Public reports can inform questions about utility dependencies, cooling, recovery exercises, asset life, and handover evidence. They cannot replace a facility assessment.
04 / JURISDICTION COMPARISON
Place two research areas side by side using the same snapshot and definition. These are documented footprints, not market rankings or site-selection scores.
66
Data-center catalog records
Different sources and units. Do not sum these numbers or infer failure rates. Missing records reflect incomplete research coverage.
95
Data-center catalog records
Different sources and units. Do not sum these numbers or infer failure rates. Missing records reflect incomplete research coverage.
Counts do not establish power availability, water stress, environmental impact, security posture, investment returns, or a site’s suitability. No proprietary “ethical score” is assigned without a defined, independently supportable assessment.
05 / EVIDENCE & METHODS
Ethical intelligence starts with clear provenance. Source dates, counting units, and uncertainty remain visible throughout the tool.
1,605 data-center site/campus records, filtered from Compute Atlas v1.34.0. Snapshot: Sep 21, 2026. Other facility types are excluded. Campus and individual-site records may overlap; totals are not unique physical facilities.
Source-reported stages are not live operational verification. Dormant and decommissioned are not native catalog stages.
Compute Atlas source ↗Commission a technical study ↗CC BY 4.0 license ↗1,237 unique mapped buildings in the PNNL-led IM3 February 9, 2026 snapshot, including one in Puerto Rico. Campus and point layers are excluded to avoid mixing counting units.
OpenStreetMap coverage is incomplete. No operating, lifecycle, capacity, or construction-type classification is inferred.
Original IM3 research ↗Download jurisdiction counts ↓© OpenStreetMap contributors · ODbL ↗Selected historical incidents and lifecycle records, manually reviewed against cited public sources. Events and operating status are separate facts.
No exhaustive coverage or comparative reliability claim. Dormant status remains unknown without explicit evidence.
Request a scoped analysis ↗Submit a source or correction ↗50 states, D.C., and five inhabited U.S. territories. Generalized U.S. Census boundaries; territory insets use separate scales. U.S. Minor Outlying Islands are outside these source datasets.
Snapshots are reviewed and versioned before publication. This tool is not an automated live feed, a certification, or an inventory of Eco TerraVault facilities.
Read the full methodology ↗Download data methods ↓Eco TerraVault connects infrastructure operations, mechanical systems, cybersecurity, and lifecycle planning. Use this research to start a better-informed conversation.
