{ "schema_version": 1, "source_compilation_context": { "al": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/al.json", "updated": "2026-10-24" }, "az": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/az.json", "updated": "2026-10-24" }, "ca": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/ca.json", "updated": "2026-10-25" }, "co": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/co.json", "updated": "2026-10-26" }, "fl": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/fl.json", "updated": "2026-10-24" }, "ga": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/ga.json", "updated": "2026-10-24" }, "ia": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/ia.json", "updated": "2026-10-24" }, "il": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/il.json", "updated": "2026-10-26" }, "nj": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/nj.json", "updated": "2026-10-24" }, "oh": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/oh.json", "updated": "2026-10-24" }, "or": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/or.json", "updated": "2026-10-26" }, "pa": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/pa.json", "updated": "2026-10-24" }, "sc": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/sc.json", "updated": "2026-10-26" }, "tx": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/tx.json", "updated": "2026-10-24" }, "ut": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/ut.json", "updated": "2026-10-24" }, "va": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/va.json", "updated": "2026-10-25" }, "wi": { "attribution": { "inventory": { "name": "Compute Atlas", "creator": "Edward Kubiak", "url": "https://www.compute-atlas.com/api", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/", "snapshot_url": "https://www.compute-atlas.com/api/facilities", "retrieved": "2026-10-14", "sha256": "79ad432dab7c128e428234c9d0dd40933114b415a4a5d697db00095637d50f37", "changes": "Added provenance, publication-date distinctions, display-safe wording, quarantine flags and state partitioning. Original source records retained locally." }, "counties": "U.S. Census Bureau county boundaries (public domain)", "research": "Field-specific source context. See the linked source and limits on each record." }, "source_data_url": "https://datacentersatlas.com/data/wi.json", "updated": "2026-10-25" } }, "scope": "Linked company names and sourced roles retain their separate meaning in each record. Research records retain their sources, dates and location limits. Counts are not a census of operating buildings. Company name links alone do not establish ownership or operation.", "collection": { "kind": "companies", "key": "qts", "label": "QTS" }, "records": [ { "id": "qts-ashburn-1-va", "state": "va", "kind": "facility", "name": "QTS Ashburn 1", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Loudoun" ], "city": "Sterling", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Undated page still uses coming-online target and under-construction label after target quarter. No automatic commissioning inference; 55 MW headline should not be added again to the DC1 specification. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/ashburn-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" } ], "loc": { "lat": 39.11386, "lng": -77.57236, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 28, "dc1_critical_power_mw_lower_bound": 55, "dc2_critical_power_mw_lower_bound": 22.5, "dc2_target": "2026-Q2", "dc1_address": "22271 Broderick Drive, Sterling, VA 20166", "dc2_address": "22280 Randolph Drive, Sterling, VA 20166", "dc2_operator_described_status": "under construction" }, "notes": [ "Undated page still uses coming-online target and under-construction label after target quarter. No automatic commissioning inference; 55 MW headline should not be added again to the DC1 specification.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "S2-Virginia-DEQ-20261015", "scope": "Current operator services for Ashburn 1 campus, DC1 service component; building/campus completeness and opening date remain separate.", "fields": { "facility_designation": "Ashburn 1 campus, DC1 service component", "current_status": "operating", "status_basis": "Current operator listing advertises services for the named facility or campus component. No dated opening, full commissioning, energized IT load or completion of all buildings is established.", "agency_registration_number": "74141", "agency_air_operational_status": "Operating", "agency_registered_address": "22271 Broderick Drive, Sterling, VA, 20166", "operator_named_building_addresses": { "DC1": "22271 Broderick Drive, Sterling, VA 20166", "DC2": "22280 Randolph Drive, Sterling, VA 20166" }, "capacity_and_schedule_scope": "Current page advertises 55 MW+ critical power capacity in DC1 and 22.5 MW+ in DC2 with a Q2 2026 target, while still labeling DC2 under construction. The elapsed target is not proof of completion; plus figures are lower bounds, not exact measured loads." }, "notes": [ "Provider brand is distinct from legal owner, tenant and parent-company identity. Named buildings and overlapping research records are not additive physical-site counts.", "Source-check dates are not opening, commissioning or technical measurement dates. All inherited coordinates, precision, opening fields and legacy MW remain unchanged. No address was taken from a corporate footer, directory snippet or unavailable PDF.", "DEQ air-site Operating is a registry classification, not an individual issued permit, building completion certificate, actual generator use or full-campus energization." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed operator source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" } ], "checked": "2026-10-15", "whole_record_certified": false }, { "overlay": "Company role source check44, October23,2026", "scope": "QTS identifies the named Ashburn 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 at22271BroderickDrive from DC2 at22280RandolphDrive in Sterling. A future Q2 2026 delivery phrase and an under construction label for DC2 are not proof of its completion. The marketing market name does not replace Sterling.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS identifies the named Ashburn 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 at22271BroderickDrive from DC2 at22280RandolphDrive in Sterling. A future Q2 2026 delivery phrase and an under construction label for DC2 are not proof of its completion. The marketing market name does not replace Sterling." }, "provider_role": "operator" }, "notes": [ "QTS identifies the named Ashburn 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 at22271BroderickDrive from DC2 at22280RandolphDrive in Sterling. A future Q2 2026 delivery phrase and an under construction label for DC2 are not proof of its completion. The marketing market name does not replace Sterling." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Sterling · Loudoun · Source context reviewed", "status_scope": "Current operator services for Ashburn 1 campus, DC1 service component; building/campus completeness and opening date remain separate.", "building_contexts": [ { "id": "building:qts-ash1-dc1", "name": "Ashburn 1 DC1", "phase": null, "identity_scope": "Named operator building associated for research with this campus record; physical identity and parcel extent remain unresolved.", "address": "22271 Broderick Drive, Sterling, VA 20166", "status": "operator_listed_existing_service", "status_scope": "DC1 services/critical power advertised; no full commissioning or opening date established.", "field_sources": { "name": [ "https://q.com/data-centers/ashburn-1/" ], "phase": [ "https://q.com/data-centers/ashburn-1/" ], "identity_scope": [ "https://q.com/data-centers/ashburn-1/" ], "address": [ "https://q.com/data-centers/ashburn-1/" ], "status": [ "https://q.com/data-centers/ashburn-1/" ], "status_scope": [ "https://q.com/data-centers/ashburn-1/" ] }, "conflicts": {} }, { "id": "building:qts-ash1-dc2", "name": "Ashburn 1 DC2", "phase": null, "identity_scope": "Named operator building associated for research with this campus record; physical identity and parcel extent remain unresolved.", "address": "22280 Randolph Drive, Sterling, VA 20166", "status": "operator_reported_under_construction", "status_scope": "Operator page explicitly retains under construction; elapsed Q2 2026 target is not completion proof.", "field_sources": { "name": [ "https://q.com/data-centers/ashburn-1/" ], "phase": [ "https://q.com/data-centers/ashburn-1/" ], "identity_scope": [ "https://q.com/data-centers/ashburn-1/" ], "address": [ "https://q.com/data-centers/ashburn-1/" ], "status": [ "https://q.com/data-centers/ashburn-1/" ], "status_scope": [ "https://q.com/data-centers/ashburn-1/" ] }, "conflicts": {} } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "51107" } }, { "id": "qts-ashburn-2-ashburn-lockridge-va", "state": "va", "kind": "facility", "name": "QTS Ashburn 2 (Ashburn-Lockridge)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Loudoun" ], "city": "Sterling", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Planned capacity wording is preserved, not labeled current operating consumption. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/ashburn-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" } ], "loc": { "lat": 39.11803, "lng": -77.70202, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 24, "planned_capacity_mw_lower_bound": 75, "power_basis": "current planned capacity; webpage does not separately define critical IT versus utility in this section" }, "notes": [ "Planned capacity wording is preserved, not labeled current operating consumption.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Operator-Jurisdiction-20261015", "scope": "Current operator Ashburn 2 campus listing, planned capacity and named building addresses. Current operating stage, individual commissioning and air-registration address identity remain unresolved.", "fields": { "facility_designation": "Ashburn 2 / Ashburn-Lockridge campus service listing", "current_status": "unresolved", "status_basis": "Current operator page describes 75 MW+ planned capacity without establishing commissioned or operating service. The DEQ address crosswalk is unresolved; no operating label is assigned.", "operator_named_building_addresses": { "DC1": "44675 Quality Tech Lane, Sterling, VA 20166", "DC2": "44655 Quality Tech Lane, Sterling, VA 20166" }, "capacity_and_schedule_scope": "Current page advertises 75 MW+ current planned campus capacity. It does not identify this as IT load, a utility approval, actual energized capacity, or separate capacity for each building. Current individual building commissioning is not established.", "unresolved_air_registration_address_context": "DEQ74232 names ASH2 Lockridge at 22426 Lockridge Rd; current operator page lists DC1/DC2 on Quality Tech Lane. Same-parcel identity, address renumbering and building-specific applicability are not established. Registration stays pending as an identity hold." }, "notes": [ "Provider brand is distinct from legal owner, tenant and parent-company identity. Named buildings and overlapping research records are not additive physical-site counts.", "Source-check dates are not opening, commissioning or technical measurement dates. All inherited coordinates, precision, opening fields and legacy MW remain unchanged. No address was taken from a corporate footer, directory snippet or unavailable PDF.", "A current marketing listing or a tour invitation does not by itself establish an operating phase when the available power figure is explicitly planned." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed operator source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" } ], "checked": "2026-10-15", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "The current QTS page identifies Ashburn 2 and Ashburn Lockridge DC1 and DC2, offers tours and labels campus capacity as planned. The page does not explicitly establish the physical stage of both facilities. No address or permit crosswalk is adopted and planned campus power is not observed IT capacity.", "fields": { "current_stage_evidence": { "outcome": "campus_listing_and_planned_capacity_stage_held", "scope": "The current QTS page identifies Ashburn 2 and Ashburn Lockridge DC1 and DC2, offers tours and labels campus capacity as planned. The page does not explicitly establish the physical stage of both facilities. No address or permit crosswalk is adopted and planned campus power is not observed IT capacity." } }, "notes": [ "The current QTS page identifies Ashburn 2 and Ashburn Lockridge DC1 and DC2, offers tours and labels campus capacity as planned. The page does not explicitly establish the physical stage of both facilities. No address or permit crosswalk is adopted and planned campus power is not observed IT capacity.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check44, October23,2026", "scope": "QTS identifies the named Ashburn 2 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 and DC2 addresses in Sterling and advertises current planned capacity. Neither planned capacity, a tour invitation nor the provider relationship establishes commissioned operation. The existing unclear status remains exact.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS identifies the named Ashburn 2 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 and DC2 addresses in Sterling and advertises current planned capacity. Neither planned capacity, a tour invitation nor the provider relationship establishes commissioned operation. The existing unclear status remains exact." }, "provider_role": "operator" }, "notes": [ "QTS identifies the named Ashburn 2 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source separates DC1 and DC2 addresses in Sterling and advertises current planned capacity. Neither planned capacity, a tour invitation nor the provider relationship establishes commissioned operation. The existing unclear status remains exact." ], "sources": [ { "url": "https://q.com/data-centers/ashburn-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Sterling · Loudoun · Source context reviewed", "building_contexts": [ { "id": "building:qts-ash2-dc1", "name": "Ashburn 2 DC1", "phase": null, "identity_scope": "Named operator building associated for research with this campus record; physical identity and parcel extent remain unresolved.", "address": "44675 Quality Tech Lane, Sterling, VA 20166", "status": "unknown", "status_scope": "Campus service listing and planned capacity do not establish this building is fully commissioned.", "field_sources": { "name": [ "https://q.com/data-centers/ashburn-2/" ], "phase": [ "https://q.com/data-centers/ashburn-2/" ], "identity_scope": [ "https://q.com/data-centers/ashburn-2/" ], "address": [ "https://q.com/data-centers/ashburn-2/" ], "status": [ "https://q.com/data-centers/ashburn-2/" ], "status_scope": [ "https://q.com/data-centers/ashburn-2/" ] }, "conflicts": {} }, { "id": "building:qts-ash2-dc2", "name": "Ashburn 2 DC2", "phase": null, "identity_scope": "Named operator building associated for research with this campus record; physical identity and parcel extent remain unresolved.", "address": "44655 Quality Tech Lane, Sterling, VA 20166", "status": "unknown", "status_scope": "Campus service listing and planned capacity do not establish this building is fully commissioned.", "field_sources": { "name": [ "https://q.com/data-centers/ashburn-2/" ], "phase": [ "https://q.com/data-centers/ashburn-2/" ], "identity_scope": [ "https://q.com/data-centers/ashburn-2/" ], "address": [ "https://q.com/data-centers/ashburn-2/" ], "status": [ "https://q.com/data-centers/ashburn-2/" ], "status_scope": [ "https://q.com/data-centers/ashburn-2/" ] }, "conflicts": {} } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "51107" } }, { "id": "qts-atlanta-1-atlanta-metro-dc1-ga", "state": "ga", "kind": "facility", "name": "QTS Atlanta 1 (Atlanta-Metro DC1)", "group": "operating", "status": "Operator-reported operation", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Fulton" ], "city": "Atlanta", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Campus total, not DC1 alone. Substations are planned; no energized utilization or all-building completion inferred. Company conservation acres and annual report totals excluded. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/atlanta/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/fayetteville/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" }, { "url": "https://q.com/data-centers/atlanta-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=1033+Jefferson+St+NW%2C+Atlanta%2C+GA+30318&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 33.77566228073, "lng": -84.422626439969, "precision": "address", "basis": "Published QTS facility address 1033 Jefferson St NW, Atlanta, GA 30318 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 99, "advertised_critical_campus_capacity_mw_lower_bound": 278, "planned_dedicated_substations": 3 }, "notes": [ "Campus total, not DC1 alone. Substations are planned; no energized utilization or all-building completion inferred. Company conservation acres and annual report totals excluded.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/atlanta/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "QTS explicitly says it operates its Atlanta campus in the current Fayetteville page and links that campus to Atlanta 1. The Atlanta 1 page lists DC1 at 1033 Jefferson Street with other campus buildings. The label is a source reported campus operation context. It does not certify every building, advertised capacity, commissioning date or an independent physical site count.", "fields": { "current_stage_evidence": { "outcome": "operator_reported_operation", "scope": "QTS explicitly says it operates its Atlanta campus in the current Fayetteville page and links that campus to Atlanta 1. The Atlanta 1 page lists DC1 at 1033 Jefferson Street with other campus buildings. The label is a source reported campus operation context. It does not certify every building, advertised capacity, commissioning date or an independent physical site count." } }, "notes": [ "QTS explicitly says it operates its Atlanta campus in the current Fayetteville page and links that campus to Atlanta 1. The Atlanta 1 page lists DC1 at 1033 Jefferson Street with other campus buildings. The label is a source reported campus operation context. It does not certify every building, advertised capacity, commissioning date or an independent physical site count." ], "sources": [ { "url": "https://q.com/data-centers/fayetteville/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" }, { "url": "https://q.com/data-centers/atlanta-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 33.77566228073, "lng": -84.422626439969, "precision": "address", "basis": "Published QTS facility address 1033 Jefferson St NW, Atlanta, GA 30318 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "1033 Jefferson St NW, Atlanta, GA 30318", "county_fips": [ "13121" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact.", "The existing record explicitly names Atlanta Metro DC1. The official campus page explicitly binds DC1 to 1033 Jefferson Street NW; other building addresses are excluded. Aerial context shows a street beside industrial building forms. No roof or additional campus building is assigned." ], "sources": [ { "url": "https://q.com/data-centers/atlanta-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=1033+Jefferson+St+NW%2C+Atlanta%2C+GA+30318&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source describes the Atlanta 1 campus, with multiple buildings, addresses and future components. This role does not resolve a particular DC1 code, change its point or establish completion of all campus works.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source describes the Atlanta 1 campus, with multiple buildings, addresses and future components. This role does not resolve a particular DC1 code, change its point or establish completion of all campus works." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source describes the Atlanta 1 campus, with multiple buildings, addresses and future components. This role does not resolve a particular DC1 code, change its point or establish completion of all campus works.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/atlanta-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Atlanta · Fulton · Source context reviewed", "status_scope": "QTS explicitly says it operates its Atlanta campus in the current Fayetteville page and links that campus to Atlanta 1. The Atlanta 1 page lists DC1 at 1033 Jefferson Street with other campus buildings. The label is a source reported campus operation context. It does not certify every building, advertised capacity, commissioning date or an independent physical site count." }, { "id": "qts-blue-hole-blakely-ga", "state": "ga", "kind": "facility", "name": "QTS Project Blue Hole", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Early" ], "city": "Blakely", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Named original reporter/issuer context with current versus historical stage explicit.. JacklynnLambert WTVY August11,2026 originalBlakelymeetingreport sayscityapprovedMOUwithEarlyCounty,schools,developmentauthority/QTS. SOURCECORRECTED earlier TAXBREAK label.7.5Mfirstphasefollowed7Mannualpaymentsreportedcommitments, notabatementvalue/paidreceipts. Sharedfunddistributionandwater/sewer/transportdetailsSTILLTOBEAGREEDpercityattorney. Nofullyexecutedallpartycounterpartread, no unconditionalpaymentguarantee/allpermits/ITMWoroperatingdate. Do notmultiplyundefinedannualdurationoraddunrelatedcommunityprojectcosts. Not everyfield/currentphysicaloperation/paidfunds/issuedpermit/exactITcertified.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.wtvy.com/2026/08/11/blakely-approves-agreement-with-qts-data-centers-related-proposed-facility/", "host": "wtvy.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/blakely/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 31.32321, "lng": -84.90307, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "national-opening-land-and-approval-stage-review-round77-2026-10-15.json", "scope": "Named original reporter/issuer context with current versus historical stage explicit.", "fields": {}, "notes": [ "JacklynnLambert WTVY August11,2026 originalBlakelymeetingreport sayscityapprovedMOUwithEarlyCounty,schools,developmentauthority/QTS. SOURCECORRECTED earlier TAXBREAK label.7.5Mfirstphasefollowed7Mannualpaymentsreportedcommitments, notabatementvalue/paidreceipts.", "Sharedfunddistributionandwater/sewer/transportdetailsSTILLTOBEAGREEDpercityattorney. Nofullyexecutedallpartycounterpartread, no unconditionalpaymentguarantee/allpermits/ITMWoroperatingdate. Do notmultiplyundefinedannualdurationoraddunrelatedcommunityprojectcosts.", "Not everyfield/currentphysicaloperation/paidfunds/issuedpermit/exactITcertified." ], "sources": [ { "url": "https://www.wtvy.com/2026/08/11/blakely-approves-agreement-with-qts-data-centers-related-proposed-facility/", "host": "wtvy.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "encore-2026-10-17-batch2", "scope": "Limited source identity and stage review; not whole-record certification, parcel verification or a physical-site census.", "fields": { "current_stage_evidence": { "outcome": "unresolved", "scope": "The August 2026 account reports a QTS agreement with future utility and payment arrangements. The publisher expressly corrected the claim that it was a tax break. Proposed amounts are not payments received, and an original signed MOU was not established in this pass. Current construction and operation remain unresolved." } }, "notes": [ "The August 2026 account reports a QTS agreement with future utility and payment arrangements. The publisher expressly corrected the claim that it was a tax break. Proposed amounts are not payments received, and an original signed MOU was not established in this pass. Current construction and operation remain unresolved." ], "sources": [ { "url": "https://www.wtvy.com/2026/08/11/blakely-approves-agreement-with-qts-data-centers-related-proposed-facility/", "host": "www.wtvy.com", "published": "", "date": "", "checked": "2026-10-17", "label": "Reviewed source context" } ], "checked": "2026-10-17", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "QTS describes a proposed Blakely campus in early planning, with final designs and a start date not yet determined. The page does not identify the Project Blue Hole code in the inherited record. Retain the proposal lead while an exact project identity and approval crosswalk remain open. Future commitments and assurances do not establish paid funds or measured effects.", "fields": { "current_stage_evidence": { "outcome": "unresolved", "scope": "QTS describes a proposed Blakely campus in early planning, with final designs and a start date not yet determined. The page does not identify the Project Blue Hole code in the inherited record. Retain the proposal lead while an exact project identity and approval crosswalk remain open. Future commitments and assurances do not establish paid funds or measured effects." } }, "notes": [ "QTS describes a proposed Blakely campus in early planning, with final designs and a start date not yet determined. The page does not identify the Project Blue Hole code in the inherited record. Retain the proposal lead while an exact project identity and approval crosswalk remain open. Future commitments and assurances do not establish paid funds or measured effects." ], "sources": [ { "url": "https://q.com/data-centers/blakely/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": false, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Blakely · Early · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "13099" } }, { "id": "qts-cedar-rapids-ia", "state": "ia", "kind": "facility", "name": "QTS Cedar Rapids Data Center Campus", "group": "building", "status": "Operator-reported construction", "raw_status": "under construction", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Linn" ], "city": "Cedar Rapids", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Cedar Rapids official development agreement announcement. City announcement supports agreement approval account but signed terms not read here.18Mover20years conditional commitment not already paid.30permanentjobs distinct from hundreds of construction/trade jobs. Water-free cooling does not mean zero total site water consumption. No exact critical IT MW, commissioning or actual spend adopted. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://cedar-rapids.org/news_detail_T6_R2180.php", "host": "cedar-rapids.org", "date": "2025-02-12", "published": "2025-02-12", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/cedar-rapids/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 42.10908, "lng": -91.57601, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "public-institution-review-round11-2026-10-14.json", "scope": "Cedar Rapids official development agreement announcement", "fields": { "agency": "City of Cedar Rapids, Iowa", "announcement_date": "2025-02-12", "operator": "QTS Cedar Rapids LLC", "city_reported_agreement_approval_date": "2025-01-28", "site": "Big Cedar Industrial Center", "site_acres": 612, "minimum_planned_investment_usd": 750000000, "community_betterment_commitment_usd_max": 18000000, "commitment_years": 20, "payment_trigger": "following first construction phase", "minimum_first_two_phase_fulltime_jobs": 30, "jobs_per_first_phase": 15 }, "notes": [ "City announcement supports agreement approval account but signed terms not read here.18Mover20years conditional commitment not already paid.30permanentjobs distinct from hundreds of construction/trade jobs. Water-free cooling does not mean zero total site water consumption. No exact critical IT MW, commissioning or actual spend adopted.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://cedar-rapids.org/news_detail_T6_R2180.php", "host": "cedar-rapids.org", "date": "2025-02-12", "published": "2025-02-12", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "QTS explicitly describes the Cedar Rapids campus as being built in Big Cedar Industrial Center. This is an operator reported campus construction context. It does not establish an exact start day, completed buildings, operating service, capacity delivered, water use or the outcome of regulatory review.", "fields": { "current_stage_evidence": { "outcome": "operator_reported_construction", "scope": "QTS explicitly describes the Cedar Rapids campus as being built in Big Cedar Industrial Center. This is an operator reported campus construction context. It does not establish an exact start day, completed buildings, operating service, capacity delivered, water use or the outcome of regulatory review." } }, "notes": [ "QTS explicitly describes the Cedar Rapids campus as being built in Big Cedar Industrial Center. This is an operator reported campus construction context. It does not establish an exact start day, completed buildings, operating service, capacity delivered, water use or the outcome of regulatory review." ], "sources": [ { "url": "https://q.com/data-centers/cedar-rapids/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Cedar Rapids · Linn · Source context reviewed", "status_scope": "QTS explicitly describes the Cedar Rapids campus as being built in Big Cedar Industrial Center. This is an operator reported campus construction context. It does not establish an exact start day, completed buildings, operating service, capacity delivered, water use or the outcome of regulatory review.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "19113" } }, { "id": "qts-chicago-1-il", "state": "il", "kind": "facility", "name": "QTS Chicago 1", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Cook" ], "city": "Chicago", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. named operator source. Dedicated page reviewed does not provide site MW. Do not import a generic archive value or corporate annual-report spending as a verified current site value. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Illinois statewide owner/operator certificate register and commitments,notbuilding-levelallocations. 34approvedapplications/certificates not34verified physical operating buildings;91tenantcertificates not91more sites. Investment commitments not audited spend;666.6Mcalculated6.25percent estimate not actual foregone tax measured.731listednewjobs not observed employment. Company/campus totals cannot repeat for each building. Legal entity aliases and exactbuilding crosswalk remain explicit holds.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/chicago/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://dceo.illinois.gov/content/dam/soi/en/web/dceo/aboutdceo/reportsrequiredbystatute/2025-data-centers-annual-report.pdf", "host": "dceo.illinois.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=2800+S+Ashland+Ave%2C+Chicago%2C+Illinois+60608&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 41.84219257589, "lng": -87.665912876151, "precision": "address", "basis": "Published QTS facility address 2800 S Ashland Ave, Chicago, Illinois 60608 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "campus_acres": 30, "campus_buildings": 2, "published_address": "2800 S Ashland Ave, Chicago, IL60608" }, "notes": [ "Dedicated page reviewed does not provide site MW. Do not import a generic archive value or corporate annual-report spending as a verified current site value.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/chicago/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "government-primary-review-round7-2026-10-14.json", "scope": "Illinois statewide owner/operator certificate register and commitments,notbuilding-levelallocations", "fields": { "program_report_year": 2025, "program_register_as_of": "2025-12-31", "applications_received": 35, "approved_owner_operator_applications": 34, "operator_certificates_issued": 34, "tenant_certificates_issued": 91, "construction_credit_certificates_issued": 0, "total_investment_commitments_usd": 10665815092, "estimated_tax_benefits_usd": 666613443, "estimated_tax_benefit_calculation_percent": 6.25, "listed_new_job_commitments": 731, "investment_commitment_period_months": 60 }, "notes": [ "34approvedapplications/certificates not34verified physical operating buildings;91tenantcertificates not91more sites. Investment commitments not audited spend;666.6Mcalculated6.25percent estimate not actual foregone tax measured.731listednewjobs not observed employment. Company/campus totals cannot repeat for each building. Legal entity aliases and exactbuilding crosswalk remain explicit holds.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://dceo.illinois.gov/content/dam/soi/en/web/dceo/aboutdceo/reportsrequiredbystatute/2025-data-centers-annual-report.pdf", "host": "dceo.illinois.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS lists current IT services at Chicago 1 while explicitly offering preleasing for a second building. Only a service phase of the existing campus is supported. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operating_phase", "scope": "QTS lists current IT services at Chicago 1 while explicitly offering preleasing for a second building. Only a service phase of the existing campus is supported. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS lists current IT services at Chicago 1 while explicitly offering preleasing for a second building. Only a service phase of the existing campus is supported." ], "sources": [ { "url": "https://q.com/data-centers/chicago/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 41.84219257589, "lng": -87.665912876151, "precision": "address", "basis": "Published QTS facility address 2800 S Ashland Ave, Chicago, Illinois 60608 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "2800 S Ashland Ave, Chicago, Illinois 60608", "county_fips": [ "17031" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact." ], "sources": [ { "url": "https://q.com/data-centers/chicago/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=2800+S+Ashland+Ave%2C+Chicago%2C+Illinois+60608&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The Chicago 1 page includes a second building offered for future lease. Existing service and future expansion remain separate; no whole campus operating conclusion is adopted.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The Chicago 1 page includes a second building offered for future lease. Existing service and future expansion remain separate; no whole campus operating conclusion is adopted." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The Chicago 1 page includes a second building offered for future lease. Existing service and future expansion remain separate; no whole campus operating conclusion is adopted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/chicago/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Chicago · Cook · Source context reviewed", "status_scope": "QTS lists current IT services at Chicago 1 while explicitly offering preleasing for a second building. Only a service phase of the existing campus is supported. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." }, { "id": "qts-clinton-clinton-county-ia", "state": "ia", "kind": "facility", "name": "QTS Clinton Data Center Campus", "group": "proposed", "status": "Proposed", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Clinton" ], "city": "Clinton", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Page describes exploration, not project approval, construction or operation. General company environmental claims do not establish a site permit or measured water use. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Named-site current agency/operator stage, reviewed October 15, 2026. Portfolio-wide operating or sustainability statements do not establish this proposal is operating. No construction, permit completion, technical total or precise point adopted. Publication date of this current page is not established; the review date is not an event date. Displayed status uses the explicitly reviewed current status field; it is a source statement, not a physical inspection.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/clinton/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 41.898, "lng": -90.53233, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "operator_stage": "exploring development, very early plans" }, "notes": [ "Page describes exploration, not project approval, construction or operation. General company environmental claims do not establish a site permit or measured water use.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/clinton/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Atlas targeted primary-source follow-up", "scope": "Named-site current agency/operator stage, reviewed October 15, 2026", "fields": { "current_status": "proposed", "status_basis": "QTS describes a proposed Clinton campus and very early planning; the initial site plan is not final." }, "notes": [ "Portfolio-wide operating or sustainability statements do not establish this proposal is operating. No construction, permit completion, technical total or precise point adopted. Publication date of this current page is not established; the review date is not an event date." ], "sources": [ { "url": "https://q.com/data-centers/clinton/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "checked": "2026-10-15", "capture_sha256": "cec23c91c64b499f3f7e678e5b057015b52b851b0a6e062cc73a8e95c10fa34c", "events": [], "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Clinton · Clinton · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "19045" } }, { "id": "qts-colorado-springs-co", "state": "co", "kind": "facility", "name": "QTS Colorado Springs Data Center", "group": "operating", "status": "Operator-listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "El Paso" ], "city": "Colorado Springs", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Current operator specification, not measured utilization or total company capacity. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/colorado-springs/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://gisservices.elpasoco.com/arcgis2/rest/services/HubPublic/Parcels/FeatureServer/0/query?where=PARCEL%3D%277313001005%27&outFields=%2A&returnGeometry=true&outSR=4326&f=json", "host": "gisservices.elpasoco.com", "published": "", "date": "", "checked": "2026-10-22", "label": "County general reference parcel 7313001005" }, { "url": "https://imagery.nationalmap.gov/arcgis/rest/services/USGSNAIPImagery/ImageServer/exportImage?bbox=-104.85232828333835%2C38.91423675530004%2C-104.84309171666166%2C38.921423244699966&bboxSR=4326&imageSR=4326&size=1000%2C1000&format=jpg&f=image", "host": "imagery.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Aerial setting context only, acquisition date unknown" }, { "url": "https://account.pprbd.org/PublicAccess/Plan_Details.aspx?Plan=C200710", "host": "account.pprbd.org", "published": "", "date": "", "checked": "2026-10-22", "label": "Public plan C200710 address and parcel identifier link" } ], "loc": { "lng": -104.84771, "lat": 38.91783, "precision": "approximate", "basis": "Approximate county GIS reference parcel center linked to published facility address 311 S. Rockrimmon Blvd, Colorado Springs, Colorado 80919. It is not a roof, surveyed legal parcel, title, pod, tenant or full campus boundary. Aerial imagery may predate construction." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "site_acres": 21, "advertised_building_sqft": 249958, "advertised_critical_building_mw_lower_bound": 14 }, "notes": [ "Current operator specification, not measured utilization or total company capacity.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/colorado-springs/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS lists its Colorado Springs facility in its current location directory and offers current facility services. General Colorado operations, advertised power and related-resource dates do not independently certify all capacity or an opening date. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_colocation_service", "scope": "QTS lists its Colorado Springs facility in its current location directory and offers current facility services. General Colorado operations, advertised power and related-resource dates do not independently certify all capacity or an opening date. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS lists its Colorado Springs facility in its current location directory and offers current facility services. General Colorado operations, advertised power and related-resource dates do not independently certify all capacity or an opening date." ], "sources": [ { "url": "https://q.com/data-centers/colorado-springs/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 13, October 22, 2026", "scope": "County GIS reference parcel center only. Approximate remains approximate. No canonical address, status, physical date, quantity, company role, legal jurisdiction, title, roof, pod, tenant, full campus or independent building count is adopted.", "fields": { "location_review_decision": { "location": { "lng": -104.84771, "lat": 38.91783, "precision": "approximate", "basis": "Approximate county GIS reference parcel center linked to published facility address 311 S. Rockrimmon Blvd, Colorado Springs, Colorado 80919. It is not a roof, surveyed legal parcel, title, pod, tenant or full campus boundary. Aerial imagery may predate construction." }, "reference_method": "Approximate county reference parcel center", "reference_parcel": { "identifier": "7313001005", "objectid": 244883, "source_system": "El Paso County general reference parcel", "not_survey_quality": true, "legal_title_verified": false, "independent_building_identity": false }, "operator_coordinates_adopted": false, "census_range_adopted": false } }, "notes": [ "The operator numeric service address and the public regional building plan numeric address agree. The plan explicitly links that address to parcel 7313001005, which matches one county parcel feature. The rejected Census street point is outside that reference parcel.", "County simplified reference polygon only. The regional plan links an address to this parcel identifier; it does not establish title, completed construction or a full campus boundary.", "The county reference polygon and its calculated center are approximate context only. The center is not a roof or a surveyed legal boundary. Operator coordinates and Census street ranges are excluded.", "The official aerial setting image was actually viewed. Acquisition date is unknown and may predate construction. Appearance does not establish a tenant, current operation, physical milestone, title or a full campus." ], "sources": [ { "url": "https://q.com/data-centers/colorado-springs/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official Colorado Springs facility service address" }, { "url": "https://gisservices.elpasoco.com/arcgis2/rest/services/HubPublic/Parcels/FeatureServer/0/query?where=PARCEL%3D%277313001005%27&outFields=%2A&returnGeometry=true&outSR=4326&f=json", "host": "gisservices.elpasoco.com", "published": "", "date": "", "checked": "2026-10-22", "label": "County general reference parcel 7313001005" }, { "url": "https://imagery.nationalmap.gov/arcgis/rest/services/USGSNAIPImagery/ImageServer/exportImage?bbox=-104.85232828333835%2C38.91423675530004%2C-104.84309171666166%2C38.921423244699966&bboxSR=4326&imageSR=4326&size=1000%2C1000&format=jpg&f=image", "host": "imagery.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Aerial setting context only, acquisition date unknown" }, { "url": "https://account.pprbd.org/PublicAccess/Plan_Details.aspx?Plan=C200710", "host": "account.pprbd.org", "published": "", "date": "", "checked": "2026-10-22", "label": "Public plan C200710 address and parcel identifier link" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/colorado-springs/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Approximate parcel reference, not a surveyed site or roof", "summary": "Colorado Springs · El Paso · Source context reviewed", "status_scope": "QTS lists its Colorado Springs facility in its current location directory and offers current facility services. General Colorado operations, advertised power and related-resource dates do not independently certify all capacity or an opening date. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." }, { "id": "qts-dane-county-deforest-wi", "state": "wi", "kind": "facility", "name": "QTS Dane County Hyperscale Campus (DeForest)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Dane" ], "city": "DeForest", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. DeForest consolidated annexation procedure and unexecuted commitments. Procedural rejection of two petitions does not establish rejection of entire development. Proposed pre-annexation agreement not signed final award from this account. Village index contains older timelines and records throughFebruary2026; no final current outcome established.50M is pledge, not actual distribution. Conditional future approvals, sewer/service-area amendments and site plans still separate. No numeric IT MW or operating date verified. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.engagedeforest.com/QTS", "host": "engagedeforest.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.deforestwi.gov/m/NewsFlash/Home/Detail/75", "host": "www.deforestwi.gov", "published": "2026-01-27", "date": "2026-01-27", "checked": "2026-10-22", "label": "Reviewed government record" } ], "loc": { "lat": 43.03566, "lng": -89.41554, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "public-institution-review-round11-2026-10-14.json", "scope": "DeForest consolidated annexation procedure and unexecuted commitments", "fields": { "agency": "Village of DeForest, Wisconsin", "company": "QTS", "land_origin": "Town of Vienna, Dane County", "source_stage": "due diligence and proposed public consideration processes", "two_petition_rejection_date": "2025-12-04", "rejection_scope": "replace separate petitions with consolidated annexation petition", "new_notice_of_intention_date": "2025-12-12", "company_community_pledge_usd": 50000000 }, "notes": [ "Procedural rejection of two petitions does not establish rejection of entire development. Proposed pre-annexation agreement not signed final award from this account. Village index contains older timelines and records throughFebruary2026; no final current outcome established.50M is pledge, not actual distribution. Conditional future approvals, sewer/service-area amendments and site plans still separate. No numeric IT MW or operating date verified.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.engagedeforest.com/QTS", "host": "engagedeforest.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "The Village of DeForest project page records a February 3, 2026 unanimous vote rejecting the 1572.5 acre direct annexation petition. Its January 27 release was a prior staff recommendation and conditional expectation of application withdrawal. This later rejection differs from the procedural December 4, 2025 rejection of two petitions in favor of consolidation. This review adds the annexation outcome only. Final application withdrawal and any different proposal or subsequent physical stage remain unverified.", "fields": { "current_stage_evidence": { "outcome": "annexation_rejection_physical_stage_held", "scope": "The Village of DeForest project page records a February 3, 2026 unanimous vote rejecting the 1572.5 acre direct annexation petition. Its January 27 release was a prior staff recommendation and conditional expectation of application withdrawal. This later rejection differs from the procedural December 4, 2025 rejection of two petitions in favor of consolidation. This review adds the annexation outcome only. Final application withdrawal and any different proposal or subsequent physical stage remain unverified." }, "local_rule_context": { "jurisdiction": "Village of DeForest", "annexation_origin": "Town of Vienna", "scope": "The village explains annexation, comprehensive plan, zoning, service area, sewer, conditional use, subdivision and site plan processes as separate potential approvals. No completed service extension or full set of permits is inferred.", "annexation_rejected_on": "2026-02-03", "other_application_withdrawal_verified": false }, "annexation_event_adoption_hold": { "date": "2026-02-03", "kind": "denied", "reason": "The native schema supports denial events but the generic adopter currently does not. The dated decision remains in the source bound observation and concern without a mislabeled timeline event." } }, "notes": [ "The Village of DeForest project page records a February 3, 2026 unanimous vote rejecting the 1572.5 acre direct annexation petition. Its January 27 release was a prior staff recommendation and conditional expectation of application withdrawal. This later rejection differs from the procedural December 4, 2025 rejection of two petitions in favor of consolidation. This review adds the annexation outcome only. Final application withdrawal and any different proposal or subsequent physical stage remain unverified.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://www.engagedeforest.com/QTS", "host": "www.engagedeforest.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed government record" }, { "url": "https://www.deforestwi.gov/m/NewsFlash/Home/Detail/75", "host": "www.deforestwi.gov", "published": "2026-01-27", "date": "2026-01-27", "checked": "2026-10-22", "label": "Reviewed government record" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "DeForest · Dane · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "55025" } }, { "id": "qts-eagle-mountain-ii-fairfield-ut", "state": "ut", "kind": "facility", "name": "QTS Eagle Mountain II", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Utah" ], "city": "Fairfield", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. QTS preferred-site mismatch andproposed CRA-boundary amendment. PreferredrecordnamesQTSII/Fairfield,butthispacketconcernsEagleMountainexistingSweetwaterQTSproperty. Exactsitecrosswalkheld. Staffrecommendationnotvoteorfinalamendment. Historical200acreownershipscope notcurrent193acresmarketingconflict silentlycorrected. NoITMWoractualtaxrefund. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.utah.gov/pmn/files/1003911.pdf", "host": "utah.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 40.06354, "lng": -111.66532, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "government-primary-review-round7-2026-10-14.json", "scope": "QTS preferred-site mismatch andproposed CRA-boundary amendment", "fields": { "source_project": "SweetwaterIndustrialParkCRA3", "source_owner_operator": "QTS", "source_historical_ownership_area_acres_approx": 200, "proposed_cra_amendment_agenda_date": "2023-08-01" }, "notes": [ "PreferredrecordnamesQTSII/Fairfield,butthispacketconcernsEagleMountainexistingSweetwaterQTSproperty. Exactsitecrosswalkheld. Staffrecommendationnotvoteorfinalamendment. Historical200acreownershipscope notcurrent193acresmarketingconflict silentlycorrected. NoITMWoractualtaxrefund.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.utah.gov/pmn/files/1003911.pdf", "host": "utah.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Fairfield · Utah · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "49049" } }, { "id": "qts-eagle-mountain-ut", "state": "ut", "kind": "facility", "name": "QTS Eagle Mountain Data Center Campus", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Utah" ], "city": "Eagle Mountain", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. named operator source. Future campus and reported construction stages, not completed operation. Cooling savings are a developer design comparison to a traditional baseline, not measured water consumption. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. QTS proposed administrative amendment with separate CRA context. Blankvotechecklist/signaturelines do notproveadoption. TripleTailCRA1170.44acres isseparateprojectareaagenda item, not automaticallyTractdatacenterfootprintorQTSsite. QTSIparticipationpapers notproofnewFairfieldQTSIIsite. No proposedreimbursementformulaasactualpaymentor currentaward. Full132pagePDFrecoverednormally after4MBhold.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/eagle-mountain/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.utah.gov/pmn/files/1158232.pdf", "host": "utah.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 40.1749, "lng": -111.6281, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "first_phase_acres_approx": 193, "first_phase_buildings": 5, "announced_planned_investment_usd": 6000000000, "forecast_construction_jobs_lower_bound": 2000, "forecast_permanent_positions_approx": 100, "permanent_position_scope": "QTS, tenant and contractors", "operator_reported_buildings_under_construction": [ 1, 2, 3 ], "completion_target_calendar_date": null, "completion_target_source_basis": "end of the year, undated page; calendar year not independently anchored" }, "notes": [ "Future campus and reported construction stages, not completed operation. Cooling savings are a developer design comparison to a traditional baseline, not measured water consumption.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/eagle-mountain/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "government-primary-review-round7-2026-10-14.json", "scope": "QTS proposed administrative amendment with separate CRA context", "fields": { "qts_proposed_amendment_agenda_date": "2024-08-20", "qts_proposed_amendment_subject": "permitcustomerpersonalpropertytaxreimbursementdirectlytoendclients", "document_status": "agenda,staffrecommendation,draftresolution andproposedamendment; executionnotestablished" }, "notes": [ "Blankvotechecklist/signaturelines do notproveadoption. TripleTailCRA1170.44acres isseparateprojectareaagenda item, not automaticallyTractdatacenterfootprintorQTSsite. QTSIparticipationpapers notproofnewFairfieldQTSIIsite. No proposedreimbursementformulaasactualpaymentor currentaward. Full132pagePDFrecoverednormally after4MBhold.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.utah.gov/pmn/files/1158232.pdf", "host": "utah.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists its named Eagle Mountain campus as in development. This does not adopt a Fairfield alias, verify the separate Eagle Mountain II research context, or certify a construction or commissioning outcome. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists its named Eagle Mountain campus as in development. This does not adopt a Fairfield alias, verify the separate Eagle Mountain II research context, or certify a construction or commissioning outcome. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists its named Eagle Mountain campus as in development. This does not adopt a Fairfield alias, verify the separate Eagle Mountain II research context, or certify a construction or commissioning outcome." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Eagle Mountain · Utah · Source context reviewed", "status_scope": "QTS explicitly lists its named Eagle Mountain campus as in development. This does not adopt a Fairfield alias, verify the separate Eagle Mountain II research context, or certify a construction or commissioning outcome. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "49049" } }, { "id": "qts-east-windsor-nj", "state": "nj", "kind": "facility", "name": "QTS East Windsor", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Mercer" ], "city": "East Windsor", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Requested Jersey City URL returned the all-locations archive. The named East Windsor entry supports only a narrow directory claim. Dedicated source and correct-site crosswalk required. Archive Richmond values also differ from its dedicated page; never apply archive totals indiscriminately. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. named operator source. Expansion investment is additional planned scope, not confirmed spending. Onsite solar generation is not IT power and must not be added to critical capacity.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/jersey-city/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/east-windsor/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0/query?where=COUNTY%3D%27MERCER%27+AND+UPPER%28PROP_LOC%29+LIKE+%27159%25PRINCETON%25%27&outFields=OBJECTID%2CPAMS_PIN%2CPCL_MUN%2CPCLBLOCK%2CPCLLOT%2CCOUNTY%2CMUN_NAME%2CPROP_LOC%2CST_ADDRESS&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact public county or assessor reference parcel" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-74.5588310785863%2C40.27378591088753%2C-74.5505889214137%2C40.28007408911247&bboxSR=4326&imageSR=3857&size=1000%2C1000&format=png&f=image", "host": "basemap.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Actually viewed setting only, acquisition date unknown" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0?f=pjson", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel field definitions and attribution" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0/query?where=PCL_MUN%3D%271101%27+AND+PCLBLOCK%3D%2763%27+AND+PCLLOT%3D%276%27&outFields=OBJECTID%2CPAMS_PIN%2CPCLQCODE%2CPROP_LOC%2CCOUNTY%2CMUN_NAME&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "All exact municipality block and lot qualifiers, QFARM retained" } ], "loc": { "lng": -74.55471, "lat": 40.27693, "precision": "approximate", "basis": "Approximate reference parcel center for QTS Data Centers service address 159 Princeton-Hightstown Road, East Windsor, New Jersey 08520. Official reference 1101_63_6_QFARM only, not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction. Existing native status remains operating." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "operator_archive_entry": { "site": "East Windsor", "acres": 52, "mw_lower_bound": 70, "power_basis": "archive label not separately defined" } }, "notes": [ "Requested Jersey City URL returned the all-locations archive. The named East Windsor entry supports only a narrow directory claim. Dedicated source and correct-site crosswalk required. Archive Richmond values also differ from its dedicated page; never apply archive totals indiscriminately.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/jersey-city/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "critical_power_capacity_mw_lower_bound": 70, "planned_additional_investment_usd": 600000000, "solar_generation_mw": 14, "solar_field_acres": 50 }, "notes": [ "Expansion investment is additional planned scope, not confirmed spending. Onsite solar generation is not IT power and must not be added to critical capacity.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/east-windsor/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "QTS describes its East Windsor 1 data center as supporting business continuity and disaster recovery. The same page separately describes plans for one additional data center in an early planning stage. The operating phase label applies to the existing service context only. It does not commission the expansion or certify an opening day, all campus capacity or metered resource use.", "fields": { "current_stage_evidence": { "outcome": "operating_phase", "scope": "QTS describes its East Windsor 1 data center as supporting business continuity and disaster recovery. The same page separately describes plans for one additional data center in an early planning stage. The operating phase label applies to the existing service context only. It does not commission the expansion or certify an opening day, all campus capacity or metered resource use." } }, "notes": [ "QTS describes its East Windsor 1 data center as supporting business continuity and disaster recovery. The same page separately describes plans for one additional data center in an early planning stage. The operating phase label applies to the existing service context only. It does not commission the expansion or certify an opening day, all campus capacity or metered resource use." ], "sources": [ { "url": "https://q.com/data-centers/east-windsor/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The named East Windsor 1 service introduction supports this provider relationship. Its expansion FAQ is marked work in progress and supplies no adopted status, resource, cost or completion finding.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The named East Windsor 1 service introduction supports this provider relationship. Its expansion FAQ is marked work in progress and supplies no adopted status, resource, cost or completion finding." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The named East Windsor 1 service introduction supports this provider relationship. Its expansion FAQ is marked work in progress and supplies no adopted status, resource, cost or completion finding.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/east-windsor/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 27, October 23, 2026", "scope": "Approximate remains approximate. One bounded official reference parcel only. Existing native status remains operating.", "fields": { "location_review_decision": { "location": { "lng": -74.55471, "lat": 40.27693, "precision": "approximate", "basis": "Approximate reference parcel center for QTS Data Centers service address 159 Princeton-Hightstown Road, East Windsor, New Jersey 08520. Official reference 1101_63_6_QFARM only, not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction. Existing native status remains operating." }, "reference_method": "Approximate county reference parcel center", "reference_parcel": { "identifier": "1101_63_6_QFARM", "identifier_field": "PAMS_PIN", "objectid": 1303226, "agency": "New Jersey Office of Information Technology Office of GIS and contributing county and municipal governments", "reference_method": "calculated_polygon_centroid", "not_survey_quality": true, "legal_title_verified": false, "independent_building_identity": false, "full_campus_verified": false, "operator_ownership_verified": false, "tax_qualifier": "QFARM" }, "operator_coordinates_adopted": false, "census_range_adopted": false } }, "notes": [ "This is one explicitly reviewed approximate tax or fee reference parcel, not a surveyed roof, legal title, property ownership, tenant unit, independent building or complete campus boundary.", "All original identity, native status, physical dates, quantities, roles, canonical address and jurisdiction wrappers remain exact. No current operation, construction, technical quantity or physical milestone is adopted from the location evidence.", "Official aerial setting was actually viewed. Acquisition date is unknown and may predate construction. No residential roof is selected. Raw parcel geometry is not exported.", "The current QTS East Windsor Location section gives 159 Princeton Hightstown Road. One exact county reference is PAMS PIN 1101_63_6_QFARM, municipality 1101, block 63, lot 6, qualifier QFARM. The all qualifier query returns the same geometry only. QFARM remains part of the reference identity, not proof of present farm use, facility roof, expansion parcel or full campus. Current operator future expansion, power, water and investment statements are not adopted. The county owner mailing field 12851 Foster Street is excluded." ], "sources": [ { "url": "https://q.com/data-centers/east-windsor/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Current named operator service address section" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0/query?where=COUNTY%3D%27MERCER%27+AND+UPPER%28PROP_LOC%29+LIKE+%27159%25PRINCETON%25%27&outFields=OBJECTID%2CPAMS_PIN%2CPCL_MUN%2CPCLBLOCK%2CPCLLOT%2CCOUNTY%2CMUN_NAME%2CPROP_LOC%2CST_ADDRESS&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact public county or assessor reference parcel" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-74.5588310785863%2C40.27378591088753%2C-74.5505889214137%2C40.28007408911247&bboxSR=4326&imageSR=3857&size=1000%2C1000&format=png&f=image", "host": "basemap.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Actually viewed setting only, acquisition date unknown" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0?f=pjson", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel field definitions and attribution" }, { "url": "https://maps.nj.gov/arcgis/rest/services/Framework/Cadastral/MapServer/0/query?where=PCL_MUN%3D%271101%27+AND+PCLBLOCK%3D%2763%27+AND+PCLLOT%3D%276%27&outFields=OBJECTID%2CPAMS_PIN%2CPCLQCODE%2CPROP_LOC%2CCOUNTY%2CMUN_NAME&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "maps.nj.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "All exact municipality block and lot qualifiers, QFARM retained" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Approximate reference parcel, not a surveyed building or full campus", "summary": "East Windsor · Mercer · Source context reviewed", "status_scope": "QTS describes its East Windsor 1 data center as supporting business continuity and disaster recovery. The same page separately describes plans for one additional data center in an early planning stage. The operating phase label applies to the existing service context only. It does not commission the expansion or certify an opening day, all campus capacity or metered resource use." }, { "id": "qts-eisenhower-augusta-ga", "state": "ga", "kind": "facility", "name": "QTS Project Eisenhower", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Richmond" ], "city": "Augusta", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read public named-source context only; no whole-record certification. See public-preview, identity and date limitations.. Historical pause is not proof of a moratorium still effective October 14; no later extension or current rule is assumed. Exclusion from the pause is not all permits or commissioning. The proposed one-year extension requested by residents was not the adopted 49-day measure. Neighbor concerns are not health/property-value findings, and nearby Columbia/McDuffie campuses are separate. Original approvals and later observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.wrdw.com/2026/06/02/augustans-urge-city-leaders-put-data-centers-hold/", "host": "wrdw.com", "date": "2026-06-02", "published": "2026-06-02", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/augusta/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 33.36, "lng": -82.07419, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "regional-development-review-round30-2026-10-14.json", "scope": "Personally read public named-source context only; no whole-record certification. See public-preview, identity and date limitations.", "fields": { "reported_context": "WRDW reports Augusta's 49-day pause on new projects and explicit exclusion of the existing QTS Eisenhower proposal, where groundwork had been observed.", "independently_verified_current_operating_status": null, "reported_moratorium_days": 49, "reported_action_date": "2026-06-02", "source_says_this_project_excluded": true, "moratorium_currently_effective": null }, "notes": [ "Historical pause is not proof of a moratorium still effective October 14; no later extension or current rule is assumed. Exclusion from the pause is not all permits or commissioning. The proposed one-year extension requested by residents was not the adopted 49-day measure. Neighbor concerns are not health/property-value findings, and nearby Columbia/McDuffie campuses are separate.", "Original approvals and later observed outcomes take precedence; future dates have no assumed result.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.wrdw.com/2026/06/02/augustans-urge-city-leaders-put-data-centers-hold/", "host": "wrdw.com", "date": "2026-06-02", "published": "2026-06-02", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "QTS describes planned Augusta campuses and an early concept design with a future first building target. This page does not identify Project Eisenhower by code. Neither a citywide discussion nor the displayed June 24 event without a verified year establishes the exact named project stage, an accomplished event or satisfaction of conditions.", "fields": { "current_stage_evidence": { "outcome": "unresolved", "scope": "QTS describes planned Augusta campuses and an early concept design with a future first building target. This page does not identify Project Eisenhower by code. Neither a citywide discussion nor the displayed June 24 event without a verified year establishes the exact named project stage, an accomplished event or satisfaction of conditions." } }, "notes": [ "QTS describes planned Augusta campuses and an early concept design with a future first building target. This page does not identify Project Eisenhower by code. Neither a citywide discussion nor the displayed June 24 event without a verified year establishes the exact named project stage, an accomplished event or satisfaction of conditions." ], "sources": [ { "url": "https://q.com/data-centers/augusta/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Augusta · Richmond · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "13245" } }, { "id": "qts-hillsboro-1-or", "state": "or", "kind": "facility", "name": "QTS Hillsboro 1", "group": "operating", "status": "Operator-listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Separate Tower Solar project is 166 MW-dc / 120 MWac generation, not data-center IT load; excluded. Campus critical specification is not measured utilization. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/hillsboro-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=4951+NE+Huffman+St%2C+Hillsboro%2C+OR&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 45.556952872113, "lng": -122.93152732705, "precision": "address", "basis": "Published QTS facility address 4951 NE Huffman St matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 25, "advertised_critical_power_mw_lower_bound": 20, "published_dc1_address": "4951 NE Huffman St, Hillsboro" }, "notes": [ "Separate Tower Solar project is 166 MW-dc / 120 MWac generation, not data-center IT load; excluded. Campus critical specification is not measured utilization.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS offers current deployment, customer office and workspace services at its specifically named Hillsboro 1 facility, separate from Hillsboro 2 and the planned Hillsboro 3 campus. A regional solar project is not proof of facility capacity or energy delivery. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_colocation_service", "scope": "QTS offers current deployment, customer office and workspace services at its specifically named Hillsboro 1 facility, separate from Hillsboro 2 and the planned Hillsboro 3 campus. A regional solar project is not proof of facility capacity or energy delivery. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS offers current deployment, customer office and workspace services at its specifically named Hillsboro 1 facility, separate from Hillsboro 2 and the planned Hillsboro 3 campus. A regional solar project is not proof of facility capacity or energy delivery." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 45.556952872113, "lng": -122.93152732705, "precision": "address", "basis": "Published QTS facility address 4951 NE Huffman St matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "4951 NE Huffman St", "county_fips": [ "41067" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact.", "The official section explicitly names Hillsboro 1 DC1 and prints only 4951 NE Huffman St. The Census query combines this street with named market Hillsboro and retained native state OR. Its returned postal code is not claimed as operator published. No separate building point is inferred." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=4951+NE+Huffman+St%2C+Hillsboro%2C+OR&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Hillsboro · Washington · Source context reviewed", "status_scope": "QTS offers current deployment, customer office and workspace services at its specifically named Hillsboro 1 facility, separate from Hillsboro 2 and the planned Hillsboro 3 campus. A regional solar project is not proof of facility capacity or energy delivery. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." }, { "id": "qts-hillsboro-2-or", "state": "or", "kind": "facility", "name": "QTS Hillsboro 2", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. named operator source. Campus total across multiple buildings. Separate regional TowerSolar166MW-dc/120MWac headline is generation, not site IT capacity. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "http://q.com/data-centers/hillsboro-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/hillsboro-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 45.63343, "lng": -123.07598, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "campus_acres": 51, "critical_campus_capacity_mw_lower_bound": 180 }, "notes": [ "Campus total across multiple buildings. Separate regional TowerSolar166MW-dc/120MWac headline is generation, not site IT capacity.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "http://q.com/data-centers/hillsboro-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "The current QTS page names Hillsboro 2 and four campus buildings. A linked regional solar project supports QTS operations in the region, but that regional description does not establish the current stage of each Hillsboro 2 building. Current facility stage remains unverified. Campus and generation figures are not assigned to a building.", "fields": { "current_stage_evidence": { "outcome": "campus_listing_not_current_building_stage", "scope": "The current QTS page names Hillsboro 2 and four campus buildings. A linked regional solar project supports QTS operations in the region, but that regional description does not establish the current stage of each Hillsboro 2 building. Current facility stage remains unverified. Campus and generation figures are not assigned to a building." } }, "notes": [ "The current QTS page names Hillsboro 2 and four campus buildings. A linked regional solar project supports QTS operations in the region, but that regional description does not establish the current stage of each Hillsboro 2 building. Current facility stage remains unverified. Campus and generation figures are not assigned to a building.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Hillsboro · Washington · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "41067" } }, { "id": "qts-hillsboro-3-or", "state": "or", "kind": "facility", "name": "QTS Hillsboro 3", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Planned campus. Separate solar generation and company portfolio figures excluded; no site MW or commissioned status established. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/hillsboro-3/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 45.51996, "lng": -123.16835, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "planned_campus_acres": 44, "planned_buildings": 2 }, "notes": [ "Planned campus. Separate solar generation and company portfolio figures excluded; no site MW or commissioned status established.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/hillsboro-3/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists Hillsboro 3 as in development, separate from Hillsboro 1 and Hillsboro 2. Shared regional operations and solar-project text do not establish this campus operating. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists Hillsboro 3 as in development, separate from Hillsboro 1 and Hillsboro 2. Shared regional operations and solar-project text do not establish this campus operating. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists Hillsboro 3 as in development, separate from Hillsboro 1 and Hillsboro 2. Shared regional operations and solar-project text do not establish this campus operating." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Hillsboro · Washington · Source context reviewed", "status_scope": "QTS explicitly lists Hillsboro 3 as in development, separate from Hillsboro 1 and Hillsboro 2. Shared regional operations and solar-project text do not establish this campus operating. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "41067" } }, { "id": "qts-irving-1-tx", "state": "tx", "kind": "facility", "name": "QTS Irving 1", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Dallas" ], "city": "Irving", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Campus totals, not Irving 1 building alone. Master plan does not establish six completed buildings; Texas-wide water pledge excluded from site investment. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [ [ "2023-12-20", "QTS published a construction recap reporting that Irving 1 DC3 opened in March 2023. December 20 is the publication date, not the opening date. The recap does not establish operation of all planned campus facilities." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/irving/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://comptroller.texas.gov/taxes/data-centers/data-center-lists.php", "host": "comptroller.texas.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" }, { "url": "https://comptroller.texas.gov/taxes/data-centers/", "host": "comptroller.texas.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" }, { "url": "https://www.tceq.texas.gov/assets/public/permitting/air/publicnotice/38315sop.pdf", "host": "www.tceq.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Texas Commission on Environmental Quality reviewed source" }, { "url": "https://data.texas.gov/resource/t34q-qzi3.json?%24where=%28indus_type_cd_name+like+%27518210%25%27+OR+indus_type_cd_name+like+%27541513%25%27+OR+indus_typ_cd+in+%28%27518210%27%2C%27541513%27%29+OR+indus_typ_cd_1+in+%28%277374%27%2C%277376%27%29+OR+upper%28reg_ent_name%29+like+%27%25DATA%25CENTER%25%27+OR+upper%28reg_ent_name%29+like+%27%25DATA%25CENTRE%25%27+OR+upper%28reg_ent_desc_txt%29+like+%27%25DATA%25CENTER%25%27+OR+upper%28reg_ent_desc_txt%29+like+%27%25DATA%25CENTRE%25%27%29&%24order=ref_num_txt%2Cprogram_code%2Cadditional_id_text%2Cref_num_txt_1%2Caffil_begin_dt&%24limit=5000", "host": "data.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Texas Commission on Environmental Quality source context" }, { "url": "https://q.com/resources/a-year-of-growth-2023-construction-recap-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 32.75883, "lng": -96.82154, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 56, "advertised_critical_campus_mw_lower_bound": 165, "master_planned_facilities": 6 }, "notes": [ "Campus totals, not Irving 1 building alone. Master plan does not establish six completed buildings; Texas-wide water pledge excluded from site investment.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/irving/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "S2-Texas-Comptroller-20261015", "scope": "QTS Irving 1 campus, overlapping DC3 and multi-building program entries.", "fields": { "current_source_scope": "The operator identifies the Irving 1 campus and distinct DC1 through DC6 addresses. The DC3 registration overlaps a larger multi-building Irving 1 entry.", "identity_limits": "The campus is the research unit; a DC3 program entry and a DC3-through-DC6 entry are not two separate campuses.", "texas_program_entries": [ { "registered_name": "QTS Irving DC3 Data Center", "program": "qualifying data center", "registration_anchor": "DC575604-OW1", "program_effective_on": "2024-02-09", "exemption_end_on": "2026-09-03", "listed_owner_names": [ "QTS Irving DC3, LLC" ], "listed_occupant_names": [ "Microsoft Corporation" ], "listed_operator_names": [ "QTS Irving DC3, LLC", "Quality Technology Services, LLC" ] }, { "registered_name": "QTS Irving 1", "program": "qualifying large data center project", "registration_anchor": "LD063973-OW5", "program_effective_on": "2024-02-09", "exemption_end_on": null, "listed_owner_names": [ "QTS Irving DC3, LLC", "QTS Irving DC4, LLC", "QTS Irving DC5, LLC", "QTS Irving DC6, LLC" ], "listed_occupant_names": [ "Microsoft Corporation" ], "listed_operator_names": [ "QTS Irving DC3, LLC", "QTS Irving DC4, LLC", "QTS Irving DC5, LLC", "QTS Irving DC6 LLC" ] } ], "provider_brand": "QTS" }, "notes": [ "The DC3 program exemption-end date is retained as 2026-09-03. This is not interpreted as a closure or proof that the campus stopped operating.", "This review establishes campus/program identity and the operator brand, not a new precise pin, verified parcel, physical-site recall or independent current operating status.", "Program effective and exemption-end dates are not physical opening, energization or closure dates. Listed program participants do not independently verify parcel title, legal corporate relationships or current tenant occupancy.", "No new map coordinates, precise pins, metered use or legacy MW totals are adopted." ], "sources": [ { "url": "https://q.com/data-centers/irving/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed operator source" }, { "url": "https://comptroller.texas.gov/taxes/data-centers/data-center-lists.php", "host": "comptroller.texas.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" }, { "url": "https://comptroller.texas.gov/taxes/data-centers/", "host": "comptroller.texas.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed government record" } ], "checked": "2026-10-15", "whole_record_certified": false }, { "overlay": "overnight-discovery-2026-10-17", "scope": "Source-scoped official discovery and annual-filing comparison; research-context associations do not certify distinct physical sites or current whole-campus activity.", "fields": { "texas_current_program_contexts": { "checked": "2026-10-17", "reference_rows": [ { "association_scope": "Reference-list row association only, using the retained earlier direct-company identity review and unchanged source cells. Not a physical-site, street-address, current-service or tax-benefit certification.", "registered_name": "QTS Irving DC3 Data Center", "program": "Qualifying data center", "registration_number": "DC575604-OW1" }, { "association_scope": "Reference-list row association only, using the retained earlier direct-company identity review and unchanged source cells. Not a physical-site, street-address, current-service or tax-benefit certification.", "registered_name": "QTS Irving 1", "program": "Qualifying large data center project", "registration_number": "LD063973-OW5" } ], "scope": "Current source cells reconciled to earlier explicit associations, plus separately reviewed new bridges. Earlier operator reviews retain their own dates. No current tax savings, physical completion or coordinates inferred." }, "tceq_air_permit_context": { "rn": "RN102166386", "permit_number": "O4771", "document_status": "signed_effective", "issued_on": "2026-06-12", "holder": "Quality Investment Properties Irving, LLC", "scope": "Signed O4771 issued June 12, 2026 to Quality Investment Properties Irving, LLC for QTS Irving, Dallas County. Permit unit references include DC3–DC6 and emergency engines; not separate newly opened buildings.", "identity_scope": "Named QTS Irving permit and current QTS Irving 1 campus page support a broad campus evidence association. Exact permit boundary versus individual QTS buildings is not certified." } }, "notes": [ "No status, address, map point, jurisdiction, operating date or technical quantity is promoted in this review. Annual filings retain their reporting periods; a fresh retrieval is not a fresh physical-site certification." ], "sources": [ { "url": "https://comptroller.texas.gov/taxes/data-centers/data-center-lists.php", "host": "comptroller.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Current qualifying data-center and large-project registered lists" }, { "url": "https://www.tceq.texas.gov/assets/public/permitting/air/publicnotice/38315sop.pdf", "host": "www.tceq.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Texas Commission on Environmental Quality reviewed source" }, { "url": "https://q.com/data-centers/irving/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-17", "label": "QTS reviewed source" } ], "checked": "2026-10-17", "whole_record_certified": false }, { "overlay": "texas-registry-2026-10-17", "scope": "Official Texas registry source context, with initial eligibility and component triage. Not a physical-site census or current-stage review.", "fields": { "texas_registry_air_context": { "regulated_entity": "RN102166386", "registry_name": [ "QUALITY INVESTMENT PROPERTIES IRVING" ], "program_contexts": [ { "program": "AIREI", "identifiers": [ "DB2003E" ] }, { "program": "AIRNSR", "identifiers": [ "163702", "18972", "4811300817", "83125", "DB2003E" ] }, { "program": "AIROP", "identifiers": [ "", "4771", "4817" ] } ], "association_scope": "Same RN as signed QTS Irving O4771 and the prior QTS campus review. Multiple historical customers and program entries remain overlapping context, not extra sites.", "limits": "Registry authorizations, emissions reporting and historical customer affiliations can overlap. ACTIVE is a registry value, not proof of signed permit issuance, current operation, title or complete campus buildout. No generator MW, coordinates, street address or physical stage is promoted." } }, "notes": [ "AIRNSR and AIROP entries are registry contexts, not substitutes for signed permits. AIREI is emissions reporting, not a permit. Customer and status dates are not opening, completion or current ownership dates.", "The extract is a selected portion of Central Registry and the name/industry query is incomplete for all generator permits. Nonmatches are not evidence of absence." ], "sources": [ { "url": "https://data.texas.gov/resource/t34q-qzi3.json?%24where=%28indus_type_cd_name+like+%27518210%25%27+OR+indus_type_cd_name+like+%27541513%25%27+OR+indus_typ_cd+in+%28%27518210%27%2C%27541513%27%29+OR+indus_typ_cd_1+in+%28%277374%27%2C%277376%27%29+OR+upper%28reg_ent_name%29+like+%27%25DATA%25CENTER%25%27+OR+upper%28reg_ent_name%29+like+%27%25DATA%25CENTRE%25%27+OR+upper%28reg_ent_desc_txt%29+like+%27%25DATA%25CENTER%25%27+OR+upper%28reg_ent_desc_txt%29+like+%27%25DATA%25CENTRE%25%27%29&%24order=ref_num_txt%2Cprogram_code%2Cadditional_id_text%2Cref_num_txt_1%2Caffil_begin_dt&%24limit=5000", "host": "data.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Texas Commission on Environmental Quality source context" }, { "url": "https://q.com/data-centers/irving/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-17", "label": "QTS source context" }, { "url": "https://www.tceq.texas.gov/assets/public/permitting/air/publicnotice/38315sop.pdf", "host": "www.tceq.texas.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Texas Commission on Environmental Quality source context" } ], "checked": "2026-10-17", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "QTS reported the opening of Irving 1 DC3 in March 2023 and currently lists Irving 1 as a data center campus with facility tours. Operating phase describes an operator reported existing phase within the named campus. It does not establish that all six master planned facilities are operating or an exact opening day.", "fields": { "current_stage_evidence": { "outcome": "operator_reported_operating_phase", "scope": "QTS reported the opening of Irving 1 DC3 in March 2023 and currently lists Irving 1 as a data center campus with facility tours. Operating phase describes an operator reported existing phase within the named campus. It does not establish that all six master planned facilities are operating or an exact opening day." } }, "notes": [ "QTS reported the opening of Irving 1 DC3 in March 2023 and currently lists Irving 1 as a data center campus with facility tours. Operating phase describes an operator reported existing phase within the named campus. It does not establish that all six master planned facilities are operating or an exact opening day.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/irving/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" }, { "url": "https://q.com/resources/a-year-of-growth-2023-construction-recap-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check44, October23,2026", "scope": "QTS identifies the named Irving 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source distinguishes six named building addresses and a master planned campus. No statement here certifies all six buildings as commissioned or places the whole campus at the shared DC1 and DC2 street.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS identifies the named Irving 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source distinguishes six named building addresses and a master planned campus. No statement here certifies all six buildings as commissioned or places the whole campus at the shared DC1 and DC2 street." }, "provider_role": "operator" }, "notes": [ "QTS identifies the named Irving 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source distinguishes six named building addresses and a master planned campus. No statement here certifies all six buildings as commissioned or places the whole campus at the shared DC1 and DC2 street." ], "sources": [ { "url": "https://q.com/data-centers/irving/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Irving · Dallas · Source context reviewed", "status_scope": "QTS reported the opening of Irving 1 DC3 in March 2023 and currently lists Irving 1 as a data center campus with facility tours. Operating phase describes an operator reported existing phase within the named campus. It does not establish that all six master planned facilities are operating or an exact opening day.", "event_evidence": [ { "date": "2023-12-20", "text": "QTS published a construction recap reporting that Irving 1 DC3 opened in March 2023. December 20 is the publication date, not the opening date. The recap does not establish operation of all planned campus facilities.", "kind": "announced", "sources": [ { "url": "https://q.com/resources/a-year-of-growth-2023-construction-recap-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ] } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "48113" } }, { "id": "qts-jersey-city-nj", "state": "nj", "kind": "facility", "name": "QTS Jersey City (JCY1)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Hudson" ], "city": "Jersey City", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.. The introduction says more than5MW/50,000squarefeet added while the body says these are totals. Both capacity and floor-area increment-versus-total remain unresolved, with no additive sum or current IT adoption. Old global/company fleet counts and expected delivery do not establish2026operation. Original approvals and later observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.datacenterknowledge.com/operations-and-management/qts-expands-jersey-city-data-center", "host": "datacenterknowledge.com", "date": "2011-03-17", "published": "2011-03-17", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 40.73255, "lng": -74.09538, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "regional-development-review-round32-2026-10-14.json", "scope": "Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.", "fields": { "reported_context": "Data Center Knowledge reports planned QTS Jersey City power/raised-floor upgrades with second-quarter2011delivery targeted.", "independently_verified_current_operating_status": null, "canonical_it_mw": null, "canonical_raised_floor_sqft": null, "source_increment_vs_total_conflict": true }, "notes": [ "The introduction says more than5MW/50,000squarefeet added while the body says these are totals. Both capacity and floor-area increment-versus-total remain unresolved, with no additive sum or current IT adoption. Old global/company fleet counts and expected delivery do not establish2026operation.", "Original approvals and later observed outcomes take precedence; future dates have no assumed result.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.datacenterknowledge.com/operations-and-management/qts-expands-jersey-city-data-center", "host": "datacenterknowledge.com", "date": "2011-03-17", "published": "2011-03-17", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Jersey City · Hudson · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "34017" } }, { "id": "qts-lancium-hall-county-tx", "state": "tx", "kind": "facility", "name": "QTS-Lancium Hall County Data Center Campus", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Hall" ], "city": "Turkey", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. QTS and Lancium Hall County roles and forecasts. Not10Bspent,current350QTSemployees or7000permanentjobs. No ITMWor observed opening adopted. Cooling-water claim excludes domestic use and external generation impacts. Private infrastructure funding commitment not executed municipal agreement reviewed; linkedOctober9communityagreement is a later lead. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/news/qts-and-lancium-announce-data-center-campus-in-hall-county-texas/", "host": "q.com", "date": "2026-07-13", "published": "2026-07-13", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 34.53074, "lng": -100.68135, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-discovery-review-round8-2026-10-14.json", "scope": "QTS and Lancium Hall County roles and forecasts", "fields": { "announcement_date": "2026-07-13", "planned_regional_capital_investment_usd_min_exclusive": 10000000000, "expected_peak_construction_jobs_max": 7000, "expected_permanent_jobs_approx": 350, "permanent_jobs_scope": "QTS,maintenance,security andtenant positions combined", "site_owner_infrastructure_developer": "Lancium", "data_center_developer_operator": "QTS", "published_location": "near Turkey, Hall County, Texas" }, "notes": [ "Not10Bspent,current350QTSemployees or7000permanentjobs. No ITMWor observed opening adopted. Cooling-water claim excludes domestic use and external generation impacts. Private infrastructure funding commitment not executed municipal agreement reviewed; linkedOctober9communityagreement is a later lead.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/news/qts-and-lancium-announce-data-center-campus-in-hall-county-texas/", "host": "q.com", "date": "2026-07-13", "published": "2026-07-13", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists Hall County in Texas as in development. The existing named QTS and Lancium research context is retained; partnership, land and power plans do not establish commissioned operation. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists Hall County in Texas as in development. The existing named QTS and Lancium research context is retained; partnership, land and power plans do not establish commissioned operation. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists Hall County in Texas as in development. The existing named QTS and Lancium research context is retained; partnership, land and power plans do not establish commissioned operation." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Company role source check 09, October 23, 2026", "scope": "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted. The Hall County announcement assigns planned data center building design and construction to QTS, while describing Lancium separately as campus and infrastructure partner. Only the QTS developer role is adopted here; the source does not establish that either party has completed those works.", "fields": { "company_association": { "name": "QTS", "role": "developer", "identity_scope": "provider_brand_only", "scope": "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted. The Hall County announcement assigns planned data center building design and construction to QTS, while describing Lancium separately as campus and infrastructure partner. Only the QTS developer role is adopted here; the source does not establish that either party has completed those works." }, "provider_role": "developer" }, "notes": [ "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted. The Hall County announcement assigns planned data center building design and construction to QTS, while describing Lancium separately as campus and infrastructure partner. Only the QTS developer role is adopted here; the source does not establish that either party has completed those works.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/news/qts-and-lancium-announce-data-center-campus-in-hall-county-texas/", "host": "q.com", "published": "2026-07-13", "date": "2026-07-13", "checked": "2026-10-23", "label": "Dated first party named campus announcement, planned developer role only" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Turkey · Hall · Source context reviewed", "status_scope": "QTS explicitly lists Hall County in Texas as in development. The existing named QTS and Lancium research context is retained; partnership, land and power plans do not establish commissioned operation. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "48191" } }, { "id": "qts-marvel-bessemer-al", "state": "al", "kind": "facility", "name": "QTS Bessemer (Project Marvel)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Jefferson" ], "city": "Bessemer", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.. This is2025reporting, not a2026vote. QTS is not identified in the readable body. The claimed100-acre site and other land/building descriptions are inconsistent and not reconciled. Opponents' water, power, incentives and environmental claims are not approved amounts, measured impacts or current IT demand. No later rezoning result adopted. Original approvals and later observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://tuscaloosathread.com/bessemer-data-center-concerns/", "host": "tuscaloosathread.com", "date": "2025-10-14", "published": "2025-10-14", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/bessemer/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 33.57463, "lng": -86.91847, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "regional-development-review-round32-2026-10-14.json", "scope": "Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.", "fields": { "reported_context": "Tuscaloosa Thread describes Project Marvel's October7 zoning-use action and a future November18 rezoning hearing, with local opposition and developer details incomplete.", "independently_verified_current_operating_status": null, "operator_or_exact_site_identity_needs_crosswalk": true }, "notes": [ "This is2025reporting, not a2026vote. QTS is not identified in the readable body. The claimed100-acre site and other land/building descriptions are inconsistent and not reconciled. Opponents' water, power, incentives and environmental claims are not approved amounts, measured impacts or current IT demand. No later rezoning result adopted.", "Original approvals and later observed outcomes take precedence; future dates have no assumed result.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://tuscaloosathread.com/bessemer-data-center-concerns/", "host": "tuscaloosathread.com", "date": "2025-10-14", "published": "2025-10-14", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 2", "scope": "The QTS Bessemer page reports equipment mobilization, clearing, earthwork and preparatory surveys. This is a primary city project lead. The page does not identify Project Marvel by name, and the inherited news source did not identify QTS. An exact application or site crosswalk is still required before transferring that construction statement to this record.", "fields": { "current_stage_evidence": { "outcome": "unresolved", "scope": "The QTS Bessemer page reports equipment mobilization, clearing, earthwork and preparatory surveys. This is a primary city project lead. The page does not identify Project Marvel by name, and the inherited news source did not identify QTS. An exact application or site crosswalk is still required before transferring that construction statement to this record." } }, "notes": [ "The QTS Bessemer page reports equipment mobilization, clearing, earthwork and preparatory surveys. This is a primary city project lead. The page does not identify Project Marvel by name, and the inherited news source did not identify QTS. An exact application or site crosswalk is still required before transferring that construction statement to this record." ], "sources": [ { "url": "https://q.com/data-centers/bessemer/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Bessemer · Jefferson · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "01073" } }, { "id": "qts-mia1-sweetwater-fl", "state": "fl", "kind": "facility", "name": "QTS Miami (MIA1)", "group": "operating", "status": "Operator-listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Miami-Dade" ], "city": "Sweetwater", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Operator postal address is Miami; imported Sweetwater municipality still requires a jurisdiction check. Structural wind rating is not Tier or operational certification. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/miami/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=11234+NW+20th+Street%2C+Miami%2C+Florida+33172&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 25.792285723778, "lng": -80.378103015504, "precision": "address", "basis": "Published QTS facility address 11234 NW 20th Street, Miami, Florida 33172 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "site_acres": 1, "advertised_critical_power_mw": 2, "published_address": "11234 NW 20th Street, Miami, FL 33172" }, "notes": [ "Operator postal address is Miami; imported Sweetwater municipality still requires a jurisdiction check. Structural wind rating is not Tier or operational certification.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/miami/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS offers current networking and infrastructure services for customers at its specifically named Miami 1 facility. No advertised critical power, hurricane resilience or legal jurisdiction is independently certified. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_colocation_service", "scope": "QTS offers current networking and infrastructure services for customers at its specifically named Miami 1 facility. No advertised critical power, hurricane resilience or legal jurisdiction is independently certified. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS offers current networking and infrastructure services for customers at its specifically named Miami 1 facility. No advertised critical power, hurricane resilience or legal jurisdiction is independently certified." ], "sources": [ { "url": "https://q.com/data-centers/miami/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 25.792285723778, "lng": -80.378103015504, "precision": "address", "basis": "Published QTS facility address 11234 NW 20th Street, Miami, Florida 33172 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "11234 NW 20th Street, Miami, Florida 33172", "county_fips": [ "12086" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact." ], "sources": [ { "url": "https://q.com/data-centers/miami/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=11234+NW+20th+Street%2C+Miami%2C+Florida+33172&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/miami/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Sweetwater · Miami-Dade · Source context reviewed", "status_scope": "QTS offers current networking and infrastructure services for customers at its specifically named Miami 1 facility. No advertised critical power, hurricane resilience or legal jurisdiction is independently certified. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." }, { "id": "qts-new-albany-1-franklin-county-oh", "state": "oh", "kind": "facility", "name": "QTS New Albany 1", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Licking" ], "city": "New Albany", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property. Upstream ID/county label says Franklin, but cited parcel is in the Licking County cadastral service and Jersey Township. Resolve county to the matched physical site before publication; do not retain the imported Franklin label as verified. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. named operator source. No exact MW, opening event or site capital value adopted. Three-million-dollar electricity-assistance commitment is across Ohio over three years, not this individual campus. County conflict remains in the separate cadastral review.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=Parcel%3D'094-106404-00.011'&outFields=*&f=json&returnGeometry=true&outSR=4326", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/new-albany-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 40.14909, "lng": -82.46501, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "cadastral_response_features": 1, "cadastral_error": null, "parcel_assertions": [ { "PID": 98685, "Parcel": "094-106404-00.011", "OwnerName": "QTS NEW ALBANY I DC1 LLC", "SiteAddress": "1235 BEECH RD SW", "SitePostalCity": "NEW ALBANY", "Jurisdiction": "New Albany City", "Municipality": "New Albany", "Township": "Jersey", "TaxAcres": 18.1 } ] }, "notes": [ "Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property.", "Upstream ID/county label says Franklin, but cited parcel is in the Licking County cadastral service and Jersey Township. Resolve county to the matched physical site before publication; do not retain the imported Franklin label as verified.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=Parcel%3D'094-106404-00.011'&outFields=*&f=json&returnGeometry=true&outSR=4326", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "operator_named_listing": "New Albany1" }, "notes": [ "No exact MW, opening event or site capital value adopted. Three-million-dollar electricity-assistance commitment is across Ohio over three years, not this individual campus. County conflict remains in the separate cadastral review.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/new-albany-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists New Albany 1 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists New Albany 1 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists New Albany 1 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "New Albany · Licking · Source context reviewed", "status_scope": "QTS explicitly lists New Albany 1 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "39089" } }, { "id": "qts-new-albany-2-franklin-county-oh", "state": "oh", "kind": "facility", "name": "QTS New Albany 2", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Licking" ], "city": "New Albany", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property. Upstream ID/county label says Franklin, but cited parcel is in the Licking County cadastral service and Jersey Township. Resolve county to the matched physical site before publication; do not retain the imported Franklin label as verified. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. named operator source. No exact MW, opening event or site capital value adopted. Shared statewide assistance commitment cannot be counted again for this campus. County conflict remains unresolved.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=Parcel%3D'094-107502-00.003'&outFields=*&f=json&returnGeometry=true&outSR=4326", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/new-albany-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 40.05996, "lng": -82.53757, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "cadastral_response_features": 1, "cadastral_error": null, "parcel_assertions": [ { "PID": 96153, "Parcel": "094-107502-00.003", "OwnerName": "QTS NEW ALBANY II DC1 LLC", "SiteAddress": "BEECH RD SW", "SitePostalCity": "NEW ALBANY", "Jurisdiction": "New Albany City", "Municipality": "New Albany", "Township": "Jersey", "TaxAcres": 18.85 } ] }, "notes": [ "Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property.", "Upstream ID/county label says Franklin, but cited parcel is in the Licking County cadastral service and Jersey Township. Resolve county to the matched physical site before publication; do not retain the imported Franklin label as verified.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=Parcel%3D'094-107502-00.003'&outFields=*&f=json&returnGeometry=true&outSR=4326", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "operator_named_listing": "New Albany2" }, "notes": [ "No exact MW, opening event or site capital value adopted. Shared statewide assistance commitment cannot be counted again for this campus. County conflict remains unresolved.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/new-albany-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists New Albany 2 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists New Albany 2 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists New Albany 2 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "New Albany · Licking · Source context reviewed", "status_scope": "QTS explicitly lists New Albany 2 as in development in its current location directory. This does not establish a physical construction phase or commissioning; the inherited county and address associations are not reverified by this review. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "39089" } }, { "id": "qts-new-albany-3-franklin-county-oh", "state": "oh", "kind": "facility", "name": "QTS New Albany III", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Franklin" ], "city": "New Albany", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://gis.franklincountyohio.gov/hosting/rest/services/ParcelFeatures/Parcel_Features/FeatureServer/0/query?where=UPPER(OWNERNME1)+LIKE+'%25QTS%25'&outFields=*&returnCentroid=true&outSR=4326&f=json", "host": "gis.franklincountyohio.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 39.96349, "lng": -83.04383, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "cadastral_response_features": 1, "cadastral_error": null, "parcel_assertions": [ { "PARCELID": "222-005361", "ACRES": 78.24176124, "SITEADDRESS": "5760 - 5780 BABBITT RD", "OWNERNME1": "QTS NEW ALBANY III LLC", "BLDGAREA": null } ] }, "notes": [ "Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://gis.franklincountyohio.gov/hosting/rest/services/ParcelFeatures/Parcel_Features/FeatureServer/0/query?where=UPPER(OWNERNME1)+LIKE+'%25QTS%25'&outFields=*&returnCentroid=true&outSR=4326&f=json", "host": "gis.franklincountyohio.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "New Albany · Franklin · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "39049" } }, { "id": "qts-new-albany-4-licking-county-oh", "state": "oh", "kind": "facility", "name": "QTS New Albany IV", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Licking" ], "city": "New Albany", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=UPPER(OwnerName)+LIKE+'%25QTS+NEW+ALBANY+IV%25'&outFields=*&returnCentroid=true&outSR=4326&f=json", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 40.07747, "lng": -82.41903, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "cadastral_response_features": 1, "cadastral_error": null, "parcel_assertions": [ { "PID": 97052, "Parcel": "095-111570-01.000", "OwnerName": "QTS NEW ALBANY IV LLC", "SiteAddress": "13335 MILLER RD ", "SitePostalCity": "NEW ALBANY", "Jurisdiction": "New Albany City", "Municipality": "New Albany", "Township": "Jersey", "TaxAcres": 161.26 } ] }, "notes": [ "Public cadastral attributes are ownership/address/assessment evidence, not operating data-center status, end-user identity or a surveyed building pin. Acres and building area retain original field basis. No geometry is promoted; broad company queries can include unrelated property.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://gis.lickingcounty.gov/server/rest/services/Auditor/Parcels/FeatureServer/0/query?where=UPPER(OwnerName)+LIKE+'%25QTS+NEW+ALBANY+IV%25'&outFields=*&returnCentroid=true&outSR=4326&f=json", "host": "gis.lickingcounty.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "New Albany · Licking · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "39089" } }, { "id": "qts-phoenix-2-az", "state": "az", "kind": "facility", "name": "QTS Phoenix 2", "group": "proposed", "status": "Operator-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Maricopa" ], "city": "Phoenix", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Multi-building campus total. Same postal address is listed for multiple buildings; no multiplication of 210 MW or automatic address-based collapsing. No commissioned-load inference. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/phoenix-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 33.54795, "lng": -112.25545, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 80, "advertised_critical_campus_mw_lower_bound": 210, "published_multi_building_address": "1200 N 40th St, Phoenix, AZ 85008" }, "notes": [ "Multi-building campus total. Same postal address is listed for multiple buildings; no multiplication of 210 MW or automatic address-based collapsing. No commissioned-load inference.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/phoenix-2/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly lists Phoenix 2 as in development, separate from Phoenix 3 and Phoenix 4. Conflicting building-address wording in the detailed page is not promoted to a location or parcel. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS explicitly lists Phoenix 2 as in development, separate from Phoenix 3 and Phoenix 4. Conflicting building-address wording in the detailed page is not promoted to a location or parcel. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly lists Phoenix 2 as in development, separate from Phoenix 3 and Phoenix 4. Conflicting building-address wording in the detailed page is not promoted to a location or parcel." ], "sources": [ { "url": "https://q.com/data-centers/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Phoenix · Maricopa · Source context reviewed", "status_scope": "QTS explicitly lists Phoenix 2 as in development, separate from Phoenix 3 and Phoenix 4. Conflicting building-address wording in the detailed page is not promoted to a location or parcel. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "04013" } }, { "id": "qts-phoenix-4-tolleson-az", "state": "az", "kind": "facility", "name": "QTS Phoenix 4", "group": "proposed", "status": "In development", "raw_status": "in development", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Maricopa" ], "city": "Tolleson", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Generic anticipated jobs and water-free design goals are not measured outcomes or an operating-status confirmation. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Named-site current agency/operator stage, reviewed October 15, 2026. The broad In development label does not distinguish permitting from construction. Corporate portfolio operational claims do not prove this site is open. Address text does not confirm inherited coordinates. Publication date of this current page is not established; the review date is not an event date. Displayed status uses the explicitly reviewed current status field; it is a source statement, not a physical inspection.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/phoenix-4/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 33.36222, "lng": -112.80924, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "published_address": "11753 W Lower Buckeye Rd, Tolleson, AZ 85353", "operator_stage": "establishing new campus" }, "notes": [ "Generic anticipated jobs and water-free design goals are not measured outcomes or an operating-status confirmation.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/phoenix-4/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Atlas targeted primary-source follow-up", "scope": "Named-site current agency/operator stage, reviewed October 15, 2026", "fields": { "current_status": "in development", "status_basis": "The Phoenix 4 page says QTS is establishing a new data-center campus and lists a Tolleson location.", "filter_scope": "Grouped with proposed/development projects; no final permit or exact construction stage is inferred." }, "notes": [ "The broad In development label does not distinguish permitting from construction. Corporate portfolio operational claims do not prove this site is open. Address text does not confirm inherited coordinates. Publication date of this current page is not established; the review date is not an event date." ], "sources": [ { "url": "https://q.com/data-centers/phoenix-4/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "checked": "2026-10-15", "capture_sha256": "c5bd8fa5d2c657b4bceae96ebd4faab75fd93f5826a365e6089f20801a2bafee", "events": [], "whole_record_certified": false }, { "overlay": "Company role source check45, October23,2026", "scope": "QTS identifies the named Phoenix 4 campus at its published Tolleson service street and states that it is establishing new campuses. Developer per source identifies the QTS provider brand for the planned project. The previously empty company field is populated only from this exact first party campus page. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. A development statement does not establish construction, completion, commissioned operation, legal title or a future tenant. Forecast jobs, cooling claims and environmental commitments are not measured outcomes. The source publication date is unknown.", "fields": { "company_association": { "name": "QTS", "role": "developer", "identity_scope": "provider_brand_only", "scope": "QTS identifies the named Phoenix 4 campus at its published Tolleson service street and states that it is establishing new campuses. Developer per source identifies the QTS provider brand for the planned project. The previously empty company field is populated only from this exact first party campus page. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. A development statement does not establish construction, completion, commissioned operation, legal title or a future tenant. Forecast jobs, cooling claims and environmental commitments are not measured outcomes. The source publication date is unknown." }, "provider_role": "developer" }, "notes": [ "QTS identifies the named Phoenix 4 campus at its published Tolleson service street and states that it is establishing new campuses. Developer per source identifies the QTS provider brand for the planned project. The previously empty company field is populated only from this exact first party campus page. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. A development statement does not establish construction, completion, commissioned operation, legal title or a future tenant. Forecast jobs, cooling claims and environmental commitments are not measured outcomes. The source publication date is unknown." ], "sources": [ { "url": "https://q.com/data-centers/phoenix-4/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Tolleson · Maricopa · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "04013" } }, { "id": "qts-piscataway-1-nj", "state": "nj", "kind": "facility", "name": "QTS Piscataway 1", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Middlesex" ], "city": "Piscataway", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Expansion is a source-described addition with no independently checked commissioning date. Do not add 15 to 65 without an explicit baseline; 2 MW solar is generation, not additional IT load. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/piscataway/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=101+Possumtown+Road%2C+Piscataway%2C+New+Jersey+08854&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 40.556868681731, "lng": -74.488838412769, "precision": "address", "basis": "Published QTS facility address 101 Possumtown Road, Piscataway, New Jersey 08854 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 38, "advertised_critical_power_mw_lower_bound": 65, "additional_expansion_sqft": 50000, "additional_expansion_mw": 15, "onsite_rooftop_solar_mw": 2, "published_address": "101 Possumtown Road, Piscataway, NJ 08854" }, "notes": [ "Expansion is a source-described addition with no independently checked commissioning date. Do not add 15 to 65 without an explicit baseline; 2 MW solar is generation, not additional IT load.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/piscataway/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS offers current services for customer needs at Piscataway 1 while retaining additional expansion and future capacity. This supports a service phase, not certification of all planned power or the expansion. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operating_phase", "scope": "QTS offers current services for customer needs at Piscataway 1 while retaining additional expansion and future capacity. This supports a service phase, not certification of all planned power or the expansion. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS offers current services for customer needs at Piscataway 1 while retaining additional expansion and future capacity. This supports a service phase, not certification of all planned power or the expansion." ], "sources": [ { "url": "https://q.com/data-centers/piscataway/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 40.556868681731, "lng": -74.488838412769, "precision": "address", "basis": "Published QTS facility address 101 Possumtown Road, Piscataway, New Jersey 08854 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "101 Possumtown Road, Piscataway, New Jersey 08854", "county_fips": [ "34023" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact." ], "sources": [ { "url": "https://q.com/data-centers/piscataway/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=101+Possumtown+Road%2C+Piscataway%2C+New+Jersey+08854&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. Current and future campus expansion claims remain separate and are not adopted as commissioning evidence.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. Current and future campus expansion claims remain separate and are not adopted as commissioning evidence." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. Current and future campus expansion claims remain separate and are not adopted as commissioning evidence.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/piscataway/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Piscataway · Middlesex · Source context reviewed", "status_scope": "QTS offers current services for customer needs at Piscataway 1 while retaining additional expansion and future capacity. This supports a service phase, not certification of all planned power or the expansion. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." }, { "id": "qts-richmond-1-dc1-ric1-white-oak-technology-park-va", "state": "va", "kind": "facility", "name": "QTS Richmond 1 DC1 (RIC1, White Oak Technology Park)", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Henrico" ], "city": "Sandston", "address": "6000 Technology Blvd, Sandston, VA 23150", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Values describe the Richmond 1 campus, not DC1 alone. Master planned six facilities does not establish all are built. DC1/DC2/DC3 share listed address, so address-based deduplication cannot collapse all buildings or multiply campus totals. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/richmond-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Virginia DEQ air-site registry" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Tax_Parcels/MapServer/0/query?where=HOUSE_NUMBER%3D6000+AND+UPPER%28ST_NAME%29%3D%27TECHNOLOGY%27&outFields=OBJECTID%2CGPIN%2CADDRESS_KEY%2CFULL_ADDRESS%2CHOUSE_NUMBER%2CPRE_DIR%2CST_NAME%2CST_TYPE%2CSUF_DIR%2CUNIT%2CPARCEL_TYPE%2CMETHOD%2CEFFECTIVE_DATE%2CGPIN_CHANGED&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact bounded county reference parcel" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-77.24907255048015%2C37.48767591088753%2C-77.24114744951984%2C37.49396408911247&bboxSR=4326&imageSR=3857&size=1000%2C1000&format=png&f=image", "host": "basemap.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Actually viewed parcel setting only, acquisition date unknown" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Tax_Parcels/MapServer/0?f=pjson", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel field definitions and attribution" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Master_Address_Points/MapServer/0/query?where=ADDRESS_KEY%3D1714182&outFields=OBJECTID%2CADDRESS_KEY%2CHOUSE_NUMBER%2CPRE_DIR%2CST_NAME%2CST_TYPE%2CSUF_DIR%2CUNIT%2CFULL_ADDRESS%2CADDR_TYPE%2CADDR_STATUS&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Exact physical service address with matching address key" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Master_Address_Points/MapServer/0?f=pjson", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official address field definitions and domains" } ], "loc": { "lng": -77.24511, "lat": 37.49082, "precision": "approximate", "basis": "Approximate reference parcel center for the named QTS Richmond 1 DC1 service address 6000 Technology Boulevard. Official GPIN 846-704-9972 only. Not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction. Existing native status remains operating." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 207, "critical_campus_capacity_mw": 238, "master_plan_facilities": 6, "campus_current_space_sqft": 2300000, "published_dc1_address": "6000 Technology Blvd, Sandston, VA 23150" }, "notes": [ "Values describe the Richmond 1 campus, not DC1 alone. Master planned six facilities does not establish all are built. DC1/DC2/DC3 share listed address, so address-based deduplication cannot collapse all buildings or multiply campus totals.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/richmond-1/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "S2-Virginia-DEQ-20261015", "scope": "Existing RIC1 DC1-DC3 component at 6000 Technology Blvd; broader campus remains a separate scope.", "fields": { "agency_registration_number": "51232", "agency_air_operational_status": "Operating", "agency_registered_address": "6000 Technology Blvd, Sandston, VA, 23150", "agency_principal_product": "Data Center and Ofc Space", "published_address": "6000 Technology Blvd, Sandston, VA 23150", "current_status": "partly operating" }, "notes": [ "The operator lists a multi-building campus and a six-facility master plan. Its 238 MW campus headline is not assigned as installed IT load for DC1. DC4 has another address.", "The DEQ dataset warns of source errors, collection-scale and currency limits. A registration operational classification is separate from an issued permit, whole-campus completion and parcel precision." ], "sources": [ { "url": "https://q.com/data-centers/richmond-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-15", "label": "Reviewed operator source" }, { "url": "https://gisdata.deq.virginia.gov/arcgis/rest/services/public/EDMA/MapServer/294/query?where=PLA_DATA_CENTER_YN%3D%27Y%27&f=json&outFields=%2A&outSR=4326&returnGeometry=true&orderByFields=OBJECTID&resultRecordCount=1000", "host": "gisdata.deq.virginia.gov", "published": "", "date": "", "checked": "2026-10-15", "label": "Virginia DEQ air-site registry" } ], "checked": "2026-10-15", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 29, October 23, 2026", "scope": "Approximate remains approximate. One bounded official reference parcel only. Existing native status remains operating.", "fields": { "location_review_decision": { "location": { "lng": -77.24511, "lat": 37.49082, "precision": "approximate", "basis": "Approximate reference parcel center for the named QTS Richmond 1 DC1 service address 6000 Technology Boulevard. Official GPIN 846-704-9972 only. Not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction. Existing native status remains operating." }, "reference_method": "Approximate county reference parcel center", "reference_parcel": { "identifier": "846-704-9972", "identifier_field": "GPIN", "objectid": 545711, "agency": "Henrico County GIS", "reference_method": "calculated_polygon_centroid", "not_survey_quality": true, "legal_title_verified": false, "independent_building_identity": false, "full_campus_verified": false, "operator_ownership_verified": false, "official_address_feature_sha256": "b5cbaedebf6abffc0cc4ca9c1ef9b9201be564d92a7a22885d1d28ed1deaa8a9", "address_key": 1714182, "record_scope": "Richmond 1 DC1 named record reference only", "independent_dc1_roof_verified": false }, "operator_coordinates_adopted": false, "census_range_adopted": false } }, "notes": [ "The retained native record explicitly identifies Richmond 1 DC1. The current QTS Richmond 1 named section gives DC1 through DC3 at 6000 Technology Boulevard, with distinct later building addresses on Portugee Road. Only the exact DC1 street reference is used; the other buildings are not located or counted. The exact Henrico parcel GPIN 846-704-9972 and county address OBJECTID 38586061 share ADDRESS_KEY 1714182 and physical situs 6000 Technology Boulevard. The address point lies inside the reference polygon. County numeric PARCEL_TYPE 11, METHOD 3, ADDR_TYPE 1 and ADDR_STATUS 0 remain source attributes without undocumented domain inference. County source effective and edit timestamps remain context only, not physical construction or operating dates. This parcel reference does not certify a distinct DC1 roof, tenant unit, DC2 or DC3 building, or full QTS campus. The zero Census match remains original history.", "All original identity, native status, physical dates, quantities, roles, canonical address and jurisdiction wrappers remain exact.", "Official aerial setting was actually viewed. Acquisition date is unknown and may predate construction. No residential roof is selected. Raw parcel geometry is not exported." ], "sources": [ { "url": "https://q.com/data-centers/richmond-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Exact current named operator code and service address section" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Tax_Parcels/MapServer/0/query?where=HOUSE_NUMBER%3D6000+AND+UPPER%28ST_NAME%29%3D%27TECHNOLOGY%27&outFields=OBJECTID%2CGPIN%2CADDRESS_KEY%2CFULL_ADDRESS%2CHOUSE_NUMBER%2CPRE_DIR%2CST_NAME%2CST_TYPE%2CSUF_DIR%2CUNIT%2CPARCEL_TYPE%2CMETHOD%2CEFFECTIVE_DATE%2CGPIN_CHANGED&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact bounded county reference parcel" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-77.24907255048015%2C37.48767591088753%2C-77.24114744951984%2C37.49396408911247&bboxSR=4326&imageSR=3857&size=1000%2C1000&format=png&f=image", "host": "basemap.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Actually viewed parcel setting only, acquisition date unknown" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Tax_Parcels/MapServer/0?f=pjson", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel field definitions and attribution" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Master_Address_Points/MapServer/0/query?where=ADDRESS_KEY%3D1714182&outFields=OBJECTID%2CADDRESS_KEY%2CHOUSE_NUMBER%2CPRE_DIR%2CST_NAME%2CST_TYPE%2CSUF_DIR%2CUNIT%2CFULL_ADDRESS%2CADDR_TYPE%2CADDR_STATUS&returnGeometry=true&outSR=4326&resultRecordCount=25&f=json", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Exact physical service address with matching address key" }, { "url": "https://portal.henrico.gov/mapping/rest/services/Layers/Master_Address_Points/MapServer/0?f=pjson", "host": "portal.henrico.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official address field definitions and domains" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Company role source check44, October23,2026", "scope": "QTS identifies the named Richmond 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source explicitly calls the Richmond campus operated by QTS and includes DC1 in its component address block. The DC1 record stays distinct from DC2 through DC6 and the master planned campus. Advertised campus capacity and area are not newly attributed to DC1.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS identifies the named Richmond 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source explicitly calls the Richmond campus operated by QTS and includes DC1 in its component address block. The DC1 record stays distinct from DC2 through DC6 and the master planned campus. Advertised campus capacity and area are not newly attributed to DC1." }, "provider_role": "operator" }, "notes": [ "QTS identifies the named Richmond 1 data center campus and its service addresses in the main body of its own location page, with QTS facility services and contact information. The operator per source relationship records the QTS provider brand only. Existing who value and its complete source wrapper remain exact. The service street is identity context only and does not newly admit a location, parcel or roof. Existing status, location, address, county, quantities, dates and component identity remain exact. Advertised campus area, planned capacity, design features, sustainability claims and tour availability are not independently verified quantities, current computing load or legal title. The source publication date is unknown. The source explicitly calls the Richmond campus operated by QTS and includes DC1 in its component address block. The DC1 record stays distinct from DC2 through DC6 and the master planned campus. Advertised campus capacity and area are not newly attributed to DC1." ], "sources": [ { "url": "https://q.com/data-centers/richmond-1/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Approximate reference parcel, not a surveyed building or full campus", "summary": "Sandston · Henrico · Source context reviewed", "status_scope": "Existing RIC1 DC1-DC3 component at 6000 Technology Blvd; broader campus remains a separate scope." }, { "id": "qts-sacramento-ca", "state": "ca", "kind": "facility", "name": "QTS Sacramento", "group": "operating", "status": "Operator-listed service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Sacramento" ], "city": "Sacramento", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Redundancy, structural seismic standard and capacity do not establish measured power use or present utilization. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/sacramento/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=1100+N+Market+Blvd%2C+Sacramento%2C+California+95834&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 38.647209326921, "lng": -121.484675598261, "precision": "address", "basis": "Published QTS facility address 1100 N Market Blvd, Sacramento, California 95834 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "site_acres": 7, "advertised_critical_power_mw_lower_bound": 4 }, "notes": [ "Redundancy, structural seismic standard and capacity do not establish measured power use or present utilization.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/sacramento/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "overnight-status-2026-10-16", "scope": "Named project and operator-service status review; phase and source limits retained.", "fields": { "current_stage_evidence": { "outcome": "supported_label", "label": "Operator-listed service", "basis": "The current Sacramento 1 property page offers customer colocation facilities, on-site service features and tours.", "checked_on": "2026-10-16" }, "stage_review_limits": "Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review." }, "notes": [ "Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review.", "Current service and project labels are source-scoped research contexts. No entire record, physical site, technical quantity or exact parcel is certified." ], "sources": [ { "url": "https://q.com/data-centers/sacramento/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Reviewed current operator evidence" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 38.647209326921, "lng": -121.484675598261, "precision": "address", "basis": "Published QTS facility address 1100 N Market Blvd, Sacramento, California 95834 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "1100 N Market Blvd, Sacramento, California 95834", "county_fips": [ "06067" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact." ], "sources": [ { "url": "https://q.com/data-centers/sacramento/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=1100+N+Market+Blvd%2C+Sacramento%2C+California+95834&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/sacramento/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Sacramento · Sacramento · Source context reviewed", "status_scope": "Primary source review checked 2026-10-16. The current Sacramento 1 property page offers customer colocation facilities, on-site service features and tours. Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review." }, { "id": "qts-salem-township-luzerne-pa", "state": "pa", "kind": "facility", "name": "QTS Salem Township Data Center Campus (Salem 2)", "group": "proposed", "status": "Developer-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Luzerne" ], "city": "Salem Township", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.. The reported more-than500-million-USD Salem2land proceeds are not full construction cost or Salem3spending. Salem3land-value descriptions differ at1.2/1.4billion; retain conflict. Developer survey results are self-reported from78respondents, not an independent regional economic-impact study. Generic pay ranges and statewide forecasts are not actual site jobs. Later hearing outcomes, critical IT and contractual nuclear supply are not independently verified. Original approvals and later observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.timesleader.com/news/1752841/developers-tout-impacts-of-3-data-center-campuses-zoning-meeting-set-for-wednesday-on-4-3-glenbrook-group-project", "host": "timesleader.com", "date": "2026-08-22", "published": "2026-08-22", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/salem-township/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 41.21295, "lng": -75.96152, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "regional-development-review-round32-2026-10-14.json", "scope": "Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.", "fields": { "reported_context": "The Times Leader separates Salem's AWS campus, QTS/4-3Salem2land transaction and proposed4-3GlennbrookSalem3campus, with the latter awaiting an overlay decision.", "independently_verified_current_operating_status": null }, "notes": [ "The reported more-than500-million-USD Salem2land proceeds are not full construction cost or Salem3spending. Salem3land-value descriptions differ at1.2/1.4billion; retain conflict. Developer survey results are self-reported from78respondents, not an independent regional economic-impact study. Generic pay ranges and statewide forecasts are not actual site jobs. Later hearing outcomes, critical IT and contractual nuclear supply are not independently verified.", "Original approvals and later observed outcomes take precedence; future dates have no assumed result.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.timesleader.com/news/1752841/developers-tout-impacts-of-3-data-center-campuses-zoning-meeting-set-for-wednesday-on-4-3-glenbrook-group-project", "host": "timesleader.com", "date": "2026-08-22", "published": "2026-08-22", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "QTS describes its named Salem Township campus as proposed and in early planning. This is the QTS proposal only, separate from the AWS campus and the 4 3 Glenbrook proposal. It does not establish final permitting, a construction start, operation or the fulfillment of forecast investment and jobs.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_proposal", "scope": "QTS describes its named Salem Township campus as proposed and in early planning. This is the QTS proposal only, separate from the AWS campus and the 4 3 Glenbrook proposal. It does not establish final permitting, a construction start, operation or the fulfillment of forecast investment and jobs." } }, "notes": [ "QTS describes its named Salem Township campus as proposed and in early planning. This is the QTS proposal only, separate from the AWS campus and the 4 3 Glenbrook proposal. It does not establish final permitting, a construction start, operation or the fulfillment of forecast investment and jobs.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/salem-township/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Salem Township · Luzerne · Source context reviewed", "status_scope": "QTS describes its named Salem Township campus as proposed and in early planning. This is the QTS proposal only, separate from the AWS campus and the 4 3 Glenbrook proposal. It does not establish final permitting, a construction start, operation or the fulfillment of forecast investment and jobs.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "42079" } }, { "id": "qts-santa-clara-1-ca", "state": "ca", "kind": "facility", "name": "QTS Santa Clara 1", "group": "operating", "status": "Operator-listed service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Santa Clara" ], "city": "Santa Clara", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Multi-building campus specification, not individual building totals or measured utilization. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/data-centers/santa-clara/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=2805+Mission+College+Boulevard%2C+Santa+Clara%2C+California+95054&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "loc": { "lat": 37.392316455478, "lng": -121.976866013524, "precision": "address", "basis": "Published QTS facility address 2805 Mission College Boulevard, Santa Clara, California 95054 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "campus_acres": 4, "advertised_critical_campus_mw": 7.5 }, "notes": [ "Multi-building campus specification, not individual building totals or measured utilization.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/data-centers/santa-clara/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "overnight-status-2026-10-16", "scope": "Named project and operator-service status review; phase and source limits retained.", "fields": { "current_stage_evidence": { "outcome": "supported_label", "label": "Operator-listed service", "basis": "The current Santa Clara 1 property page offers customer colocation facilities, on-site service features and tours.", "checked_on": "2026-10-16" }, "stage_review_limits": "Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review." }, "notes": [ "Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review.", "Current service and project labels are source-scoped research contexts. No entire record, physical site, technical quantity or exact parcel is certified." ], "sources": [ { "url": "https://q.com/data-centers/santa-clara/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Reviewed current operator evidence" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 10, October 22, 2026", "scope": "Official facility street reference only. No canonical address, status, physical date, quantity, company role, jurisdiction, title, parcel, full campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 37.392316455478, "lng": -121.976866013524, "precision": "address", "basis": "Published QTS facility address 2805 Mission College Boulevard, Santa Clara, California 95054 matched to one Census street range inside the existing county. Calculated street reference, not a surveyed parcel, roof, suite, floor, full campus or property ownership finding." }, "reference_method": "Census interpolated street address", "published_address": "2805 Mission College Boulevard, Santa Clara, California 95054", "county_fips": [ "06085" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The current official operator numeric address section identifies this existing record. Corporate headquarters and related facility cards are excluded. The blank native address wrapper remains exact.", "The numeric street, name, type and directions are explicitly matched to the single Census result. State and existing county agree. This is a calculated street reference, not a roof, parcel, suite, independent building count or full campus boundary. Status, dates, quantities, roles, jurisdiction and all earlier source wrappers remain exact." ], "sources": [ { "url": "https://q.com/data-centers/santa-clara/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility numeric street section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=2805+Mission+College+Boulevard%2C+Santa+Clara%2C+California+95054&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street range and county context" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-22", "label": "Census calculated street method and limits" } ], "checked": "2026-10-22", "whole_record_certified": false }, { "overlay": "Company role source check 08, October 23, 2026", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source expressly describes a campus with multiple buildings. The relationship attaches to the retained campus record and does not count buildings or certify every phase.", "fields": { "company_association": { "name": "QTS", "role": "operator", "identity_scope": "provider_brand_only", "scope": "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source expressly describes a campus with multiple buildings. The relationship attaches to the retained campus record and does not count buildings or certify every phase." }, "provider_role": "operator" }, "notes": [ "QTS presents this named facility or campus as part of its data center service offering on its first party location page. Operator is the attributed provider brand role, not an independently established legal operating entity or property owner. Company capacity, resilience, sustainability and community claims do not establish measured effects. No status, location, physical date, technical figure, certification or environmental outcome is promoted. The source expressly describes a campus with multiple buildings. The relationship attaches to the retained campus record and does not count buildings or certify every phase.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/data-centers/santa-clara/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility service page, scoped provider context reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Published address reference, not a surveyed building or parcel", "summary": "Santa Clara · Santa Clara · Source context reviewed", "status_scope": "Primary source review checked 2026-10-16. The current Santa Clara 1 property page offers customer colocation facilities, on-site service features and tours. Operator-listed service does not certify every building, exact occupied or energized capacity, a completion date or property boundaries. Technical specifications and published addresses are not promoted by this status review." }, { "id": "qts-van-wert-oh", "state": "oh", "kind": "facility", "name": "QTS Van Wert Data Center Campus", "group": "proposed", "status": "Operator-listed planning", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Van Wert" ], "city": "Van Wert", "address": "", "who": "QTS", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Field or source context only. Developer-issued release. Revenue/jobs are forecasts. Cooling no-consumption claim describes future cooling operations, not all facility water use or measured WUE. Its June 11 event is historical by check date. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://q.com/news/city-of-van-wert-and-qts-announce-data-center-campus-in-northwest-ohio/", "host": "q.com", "date": "2026-05-29", "published": "2026-05-29", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/van-wert/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "loc": { "lat": 40.85543, "lng": -84.58613, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "neighbor-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "planned_capital_investment_usd_approx": 10000000000, "forecast_tax_revenue_usd": 200000000, "forecast_tax_revenue_period_years": 20, "forecast_construction_jobs_lower_bound": 1500, "forecast_full_time_qts_jobs_approx": 200, "initial_career_training_commitment_usd": 100000, "planned_cooling_design": "closed loop" }, "notes": [ "Developer-issued release. Revenue/jobs are forecasts. Cooling no-consumption claim describes future cooling operations, not all facility water use or measured WUE. Its June 11 event is historical by check date.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://q.com/news/city-of-van-wert-and-qts-announce-data-center-campus-in-northwest-ohio/", "host": "q.com", "date": "2026-05-29", "published": "2026-05-29", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "orchestra-status-2026-10-19", "scope": "QTS explicitly describes its Van Wert campus as early planning with a concept that is not final. Copied Richmond County wording is excluded; no projected investment, tax receipt or construction outcome is adopted. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_planning", "scope": "QTS explicitly describes its Van Wert campus as early planning with a concept that is not final. Copied Richmond County wording is excluded; no projected investment, tax receipt or construction outcome is adopted. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy." } }, "notes": [ "QTS explicitly describes its Van Wert campus as early planning with a concept that is not final. Copied Richmond County wording is excluded; no projected investment, tax receipt or construction outcome is adopted." ], "sources": [ { "url": "https://q.com/data-centers/van-wert/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Operator source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Company role source check 09, October 23, 2026", "scope": "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted.", "fields": { "company_association": { "name": "QTS", "role": "developer", "identity_scope": "provider_brand_only", "scope": "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted." }, "provider_role": "developer" }, "notes": [ "QTS announces plans for this named data center campus in its own dated release. Developer is the attributed provider brand role for the announced project, not proof of construction, operating service, current delivery, legal ownership or a confirmed parcel. The source publication date is not a physical milestone. No status, location, technical figure, investment, jobs, water use, utility cost or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://q.com/news/city-of-van-wert-and-qts-announce-data-center-campus-in-northwest-ohio/", "host": "q.com", "published": "2026-05-29", "date": "2026-05-29", "checked": "2026-10-23", "label": "Dated first party named campus announcement, planned developer role only" } ], "checked": "2026-10-23", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Van Wert · Van Wert · Source context reviewed", "status_scope": "QTS explicitly describes its Van Wert campus as early planning with a concept that is not final. Copied Richmond County wording is excluded; no projected investment, tax receipt or construction outcome is adopted. This supports only the qualified stage described by the source, not an opening date, every hall being operational, full energized capacity, independently verified certification, legal ownership or parcel accuracy.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "39161" } }, { "id": "qts-white-oak-technology-park-ii-henrico-va", "state": "va", "kind": "facility", "name": "QTS White Oak Technology Park II (RIC5)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Henrico" ], "city": "Sandston", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.. Approximately137millionUSD is land consideration, not construction spending. Seller-to-seller transactions and earlier18millionUSD purchases are not additive to that headline total. Existing adjacent White Oak campus, its expansion and network-access point are different. Regional housing fund is not a QTS-specific grant. Utility/infrastructure2026targets are not completed service or current IT. Original approvals and later observed outcomes take precedence; future dates have no assumed result. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://virginiabusiness.com/qts-finishes-purchase-of-rezoned-henrico-tech-park-land/", "host": "virginiabusiness.com", "date": "2024-07-19", "published": "2024-07-19", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/richmond-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 37.49779, "lng": -77.41196, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "regional-development-review-round32-2026-10-14.json", "scope": "Personally read public project context only; no whole-record certification. Identity, date, future-outcome, permit, capacity and financial scopes remain limited.", "fields": { "reported_context": "Virginia Business reports QTS finished acquiring the roughly622-acre White Oak Technology ParkIIsite, with a June28remaining-land transaction and a May14rezoning.", "independently_verified_current_operating_status": null }, "notes": [ "Approximately137millionUSD is land consideration, not construction spending. Seller-to-seller transactions and earlier18millionUSD purchases are not additive to that headline total. Existing adjacent White Oak campus, its expansion and network-access point are different. Regional housing fund is not a QTS-specific grant. Utility/infrastructure2026targets are not completed service or current IT.", "Original approvals and later observed outcomes take precedence; future dates have no assumed result.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://virginiabusiness.com/qts-finishes-purchase-of-rezoned-henrico-tech-park-land/", "host": "virginiabusiness.com", "date": "2024-07-19", "published": "2024-07-19", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "The current QTS Richmond 2 page explicitly describes an operated 85 acre campus with RIC2 buildings. This is not an established identity match to the inherited White Oak Technology Park II land acquisition record. Richmond 2 operation and its planned capacity cannot resolve the separate White Oak II record.", "fields": { "current_stage_evidence": { "outcome": "separate_richmond_2_identity_hold", "scope": "The current QTS Richmond 2 page explicitly describes an operated 85 acre campus with RIC2 buildings. This is not an established identity match to the inherited White Oak Technology Park II land acquisition record. Richmond 2 operation and its planned capacity cannot resolve the separate White Oak II record." } }, "notes": [ "The current QTS Richmond 2 page explicitly describes an operated 85 acre campus with RIC2 buildings. This is not an established identity match to the inherited White Oak Technology Park II land acquisition record. Richmond 2 operation and its planned capacity cannot resolve the separate White Oak II record.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/richmond-2/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "Sandston · Henrico · Source context reviewed", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "51087" } }, { "id": "qts-york-county-sc", "state": "sc", "kind": "facility", "name": "QTS York County Data Center Campus", "group": "proposed", "status": "Developer-listed development", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "York" ], "city": "", "address": "", "who": "", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Manual source context is available for this inherited inventory record. The inventory label and approximate geography are retained for discovery. This is not certification of current operation, ownership, a separate physical building, technical capacity or a precise parcel. Missing fields remain unknown. named operator source. Four buildings is the first phase, nine is the three-phase plan, not a numerical conflict. Later land beyond approved campus would require additional investment; current estimate is not all spent. Per-billion tax examples are estimates, not guaranteed annual collections. Old May event has no verified current upcoming date. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "http://q.com/data-centers/york/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://q.com/data-centers/york/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "loc": { "lat": 34.97497, "lng": -81.18444, "precision": "county", "basis": "Shown at county level only. The dot is placed inside the county for the map and is not the site, its address or a parcel." }, "reviewed_evidence": [ { "overlay": "direct-operators-round5-2026-10-14.json", "scope": "named operator source", "fields": { "planned_total_buildings": 9, "planned_phases": 3, "first_phase_buildings": 4, "first_phase_acres_approx": 109, "second_phase_construction_target": "early2027", "planned_approved_campus_investment_usd_approx": 8000000000, "forecast_construction_jobs": 1000, "forecast_permanent_jobs": 200 }, "notes": [ "Four buildings is the first phase, nine is the three-phase plan, not a numerical conflict. Later land beyond approved campus would require additional investment; current estimate is not all spent. Per-billion tax examples are estimates, not guaranteed annual collections. Old May event has no verified current upcoming date.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "http://q.com/data-centers/york/", "host": "q.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 5", "scope": "QTS says it is developing the named York County campus. The developer listed development label describes that proposal and phased planning. The page does not independently establish an observed construction start, completion of all planned buildings or operation. Its May event listing has no verified occurrence in this review.", "fields": { "current_stage_evidence": { "outcome": "operator_listed_development", "scope": "QTS says it is developing the named York County campus. The developer listed development label describes that proposal and phased planning. The page does not independently establish an observed construction start, completion of all planned buildings or operation. Its May event listing has no verified occurrence in this review." } }, "notes": [ "QTS says it is developing the named York County campus. The developer listed development label describes that proposal and phased planning. The page does not independently establish an observed construction start, completion of all planned buildings or operation. Its May event listing has no verified occurrence in this review.", "An agency decision or a source publication date does not certify an opening, a physical site count or a technical quantity." ], "sources": [ { "url": "https://q.com/data-centers/york/", "host": "q.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Reviewed operator source" } ], "checked": "2026-10-22", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Exact site not published; shown at county level", "summary": "York · Source context reviewed", "status_scope": "QTS says it is developing the named York County campus. The developer listed development label describes that proposal and phased planning. The page does not independently establish an observed construction start, completion of all planned buildings or operation. Its May event listing has no verified occurrence in this review.", "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "withheld_unreviewed_point", "scope": "The available point evidence does not establish a supported site location. No site pin, nearby distance or aerial destination is published. The original coordinate and its provenance remain in research history.", "county_display": "45091" } } ], "compilation_license": "withheld_pending_owner_decision" }