{ "schema_version": 1, "source_compilation_context": { "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" } }, "scope": "Source compiled state collection. 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": "states", "key": "or", "label": "Oregon" }, "records": [ { "id": "abundant-mines-cascadelocks-or", "state": "or", "kind": "facility", "name": "Abundant Mines - Cascade Locks Facility", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": true, "type": "Crypto/HPC (inventory classification)", "counties": [ "Hood River" ], "city": "Cascade Locks", "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. public landlord tenant listing. Port office 427 Portage Road is not automatically tenant site address. Lease listing not independent measured MW or AI conversion. Do not merge with cancelled Roundhouse project. 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.portofcascadelocks.gov/port-tenants", "host": "portofcascadelocks.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.5191, "lng": -121.6512, "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": "public landlord tenant listing", "fields": { "government_listed_tenant": "Good Life Realty LLC dba Abundant Mines", "listed_tenant_space": "Herman Creek Business Park, Flex1 Suite101", "listed_activity": "Bitcoin mining and related high-performance computing" }, "notes": [ "Port office 427 Portage Road is not automatically tenant site address. Lease listing not independent measured MW or AI conversion. Do not merge with cancelled Roundhouse project.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.portofcascadelocks.gov/port-tenants", "host": "portofcascadelocks.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 42", "scope": "The Port current tenant page lists Abundant Mines in Herman Creek Business Park and describes its Bitcoin mining and related computing specialty. This is an official landlord tenant profile. It does not expressly establish that mining computers are energized at the inherited facility today, a particular opening day, independent sustainable performance, service quantities or current operating compliance. The unrelated other business profiles are excluded.", "fields": { "current_stage_evidence": { "outcome": "current_named_tenant_profile_not_actual_computing_stage", "scope": "The Port current tenant page lists Abundant Mines in Herman Creek Business Park and describes its Bitcoin mining and related computing specialty. This is an official landlord tenant profile. It does not expressly establish that mining computers are energized at the inherited facility today, a particular opening day, independent sustainable performance, service quantities or current operating compliance. The unrelated other business profiles are excluded." } }, "notes": [ "The Port current tenant page lists Abundant Mines in Herman Creek Business Park and describes its Bitcoin mining and related computing specialty. This is an official landlord tenant profile. It does not expressly establish that mining computers are energized at the inherited facility today, a particular opening day, independent sustainable performance, service quantities or current operating compliance. The unrelated other business profiles are excluded.", "Identity, organization roles, locations, jurisdictions, quantities and physical opening fields stay unchanged. Source checks and prospective dates never establish an opening." ], "sources": [ { "url": "https://www.portofcascadelocks.gov/port-tenants", "host": "www.portofcascadelocks.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "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": "Cascade Locks · Hood River · 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": "41027" } }, { "id": "aligned-pdx-01-or", "state": "or", "kind": "facility", "name": "Aligned PDX-01", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Aligned Data Centers", "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 state enterprise-zone eligibility does not prove this site award. Generator/UPS per-unit ratings not totalMW;TierIII design not certification. Operator names27acrecampus atroadintersection, not parcel-confirmed address. Only the listed fields were checked; imported geography, current operation, capacity and incentives require their own evidence. 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://aligneddc.com/hillsboro-data-centers/", "host": "aligneddc.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.56017, "lng": -123.09896, "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": "field-verification-2026-10-14.json", "scope": "Field or source context only", "fields": { "city": "Hillsboro", "street_description": "NE30thAve andNEEvergreenRd", "campus_acres": 27 }, "notes": [ "Generic state enterprise-zone eligibility does not prove this site award.", "Generator/UPS per-unit ratings not totalMW;TierIII design not certification.", "Operator names27acrecampus atroadintersection, not parcel-confirmed address.", "Only the listed fields were checked; imported geography, current operation, capacity and incentives require their own evidence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://aligneddc.com/hillsboro-data-centers/", "host": "aligneddc.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check 13, October 23, 2026", "scope": "Aligned Data Centers explicitly lists this named code or campus in its own location portfolio. Operator is the attributed provider brand relationship, not an independently established legal entity, property owner or commissioning finding for every phase. Listed availability, design standards and service guarantees do not prove delivered power or current operation. No status, location, physical date, technical quantity or environmental outcome is promoted.", "fields": { "company_association": { "name": "Aligned Data Centers", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Aligned Data Centers explicitly lists this named code or campus in its own location portfolio. Operator is the attributed provider brand relationship, not an independently established legal entity, property owner or commissioning finding for every phase. Listed availability, design standards and service guarantees do not prove delivered power or current operation. No status, location, physical date, technical quantity or environmental outcome is promoted." }, "provider_role": "operator" }, "notes": [ "Aligned Data Centers explicitly lists this named code or campus in its own location portfolio. Operator is the attributed provider brand relationship, not an independently established legal entity, property owner or commissioning finding for every phase. Listed availability, design standards and service guarantees do not prove delivered power or current operation. No status, location, physical date, technical quantity or environmental outcome is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://aligneddc.com/hillsboro-data-centers/", "host": "aligneddc.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact named code or campus text, scoped provider relationship reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original current provider body names PDX01 in Hillsboro and describes near term power, designed infrastructure, accessibility and service promises. This pass does not independently establish actual computing service or construction completion at the named component. Equipment, power delivery marketing, security descriptions, tax incentives and a service level promise are not substituted for a read current opening or operational account. Exact current physical stage remains held.", "fields": { "current_stage_evidence": { "outcome": "provider_named_pdx01_listing_commissioned_service_held", "scope": "The complete original current provider body names PDX01 in Hillsboro and describes near term power, designed infrastructure, accessibility and service promises. This pass does not independently establish actual computing service or construction completion at the named component. Equipment, power delivery marketing, security descriptions, tax incentives and a service level promise are not substituted for a read current opening or operational account. Exact current physical stage remains held." }, "source_read_scope": { "complete_original_current_hillsboro_body_read": true, "near_term_power_and_service_promises_not_commissioning": true, "no_quote_or_form_submission": true, "no_capacity_or_first_opening_export": true } }, "notes": [ "The complete original current provider body names PDX01 in Hillsboro and describes near term power, designed infrastructure, accessibility and service promises. This pass does not independently establish actual computing service or construction completion at the named component. Equipment, power delivery marketing, security descriptions, tax incentives and a service level promise are not substituted for a read current opening or operational account. Exact current physical stage remains held.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://aligneddc.com/hillsboro-data-centers/", "host": "aligneddc.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "apple-prineville-or", "state": "or", "kind": "facility", "name": "Apple Prineville Data Center Campus", "group": "operating", "status": "Company reported operation", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Crook" ], "city": "Prineville", "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. historical Oregon multi-program incentive context,primaryMorrowprojectnotboundsite. June2023agenda cover conflicts with2022running header; exact document date held. AppletwoLRZprojects not necessarilytwo physical campuses. MainMorrowCounty proposed2.37Bproject and113Mestimatednetbenefit do not belong to either boundApplePrineville orAmazonUmatillacampus. Historical15yearregime notcurrent2026eligibility; no tax savings allocated perbuilding. 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.oregon.gov/biz/Publications/Boards/Business%20Oregon%20Commission/2023/AmazonSIPAgendaItem.pdf", "host": "oregon.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.apple.com/environment/pdf/Apple_Environmental_Progress_Report_2026.pdf", "host": "www.apple.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "loc": { "lat": 44.14222, "lng": -120.35641, "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": "historical Oregon multi-program incentive context,primaryMorrowprojectnotboundsite", "fields": { "historical_umatilla_amazon_sip_approval_year": 2017, "historical_prineville_apple_lrz_exempt_projects": 2, "historical_prineville_apple_lrz_term_years": 15, "historical_reporting_period": "2022-2023" }, "notes": [ "June2023agenda cover conflicts with2022running header; exact document date held. AppletwoLRZprojects not necessarilytwo physical campuses. MainMorrowCounty proposed2.37Bproject and113Mestimatednetbenefit do not belong to either boundApplePrineville orAmazonUmatillacampus. Historical15yearregime notcurrent2026eligibility; no tax savings allocated perbuilding.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.oregon.gov/biz/Publications/Boards/Business%20Oregon%20Commission/2023/AmazonSIPAgendaItem.pdf", "host": "oregon.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 42", "scope": "Apple current 2026 Environmental Progress Report explicitly includes Prineville among the eight data centers that it owns and operates. The Prineville subsection separately reports 2025 electricity use and describes the operating cooling approach. Company reported operation is limited to this named campus account. The Alliance for Water Stewardship abbreviation AWS is not Amazon Web Services. Water certification, energy allocations, offsite generation capacity, every future hall, measured performance and an exact physical opening day are not certified or promoted.", "fields": { "current_stage_evidence": { "outcome": "current_named_apple_prineville_operating_account", "scope": "Apple current 2026 Environmental Progress Report explicitly includes Prineville among the eight data centers that it owns and operates. The Prineville subsection separately reports 2025 electricity use and describes the operating cooling approach. Company reported operation is limited to this named campus account. The Alliance for Water Stewardship abbreviation AWS is not Amazon Web Services. Water certification, energy allocations, offsite generation capacity, every future hall, measured performance and an exact physical opening day are not certified or promoted." }, "source_read_scope": { "text_read": "Page 53 owned and operated site paragraph, page 95 data center context and page 96 Prineville subsection.", "visual_pages": [ 95, 96 ], "whole_report_audited": false, "may_2012_month_not_completed_to_exact_day": true, "other_named_campuses_not_merged": true } }, "notes": [ "Apple current 2026 Environmental Progress Report explicitly includes Prineville among the eight data centers that it owns and operates. The Prineville subsection separately reports 2025 electricity use and describes the operating cooling approach. Company reported operation is limited to this named campus account. The Alliance for Water Stewardship abbreviation AWS is not Amazon Web Services. Water certification, energy allocations, offsite generation capacity, every future hall, measured performance and an exact physical opening day are not certified or promoted.", "Identity, organization roles, locations, jurisdictions, quantities and physical opening fields stay unchanged. Source checks and prospective dates never establish an opening." ], "sources": [ { "url": "https://www.apple.com/environment/pdf/Apple_Environmental_Progress_Report_2026.pdf", "host": "www.apple.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "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": "Prineville · Crook · Source context reviewed", "status_scope": "Apple current 2026 Environmental Progress Report explicitly includes Prineville among the eight data centers that it owns and operates. The Prineville subsection separately reports 2025 electricity use and describes the operating cooling approach. Company reported operation is limited to this named campus account. The Alliance for Water Stewardship abbreviation AWS is not Amazon Web Services. Water certification, energy allocations, offsite generation capacity, every future hall, measured performance and an exact physical opening day are not certified or promoted.", "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": "41013" } }, { "id": "aws-arlington-gilliam-or", "state": "or", "kind": "facility", "name": "AWS Arlington Data Center Campus", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Gilliam" ], "city": "Arlington", "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-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.. Land price is not capex; wind energy purchase in MWh annually is not instantaneous site MW or proof of hourly renewable power. No exact construction/opening date given. Original executed approvals, current operator disclosures and subsequent decisions take precedence. 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://bendbulletin.com/?p=417891", "host": "bendbulletin.com", "date": "2025-02-16", "published": "2025-02-16", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.37821, "lng": -120.2112, "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-round22-2026-10-14.json", "scope": "Named-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.", "fields": { "reported_context": "Oregonian reporting via Bulletin describes Amazon Arlington land acquisition and additional port land negotiation, with operations potentially years away.", "independently_verified_current_operating_status": null }, "notes": [ "Land price is not capex; wind energy purchase in MWh annually is not instantaneous site MW or proof of hourly renewable power. No exact construction/opening date given.", "Original executed approvals, current operator disclosures and subsequent decisions take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://bendbulletin.com/?p=417891", "host": "bendbulletin.com", "date": "2025-02-16", "published": "2025-02-16", "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": "Arlington · Gilliam · 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": "41021" } }, { "id": "aws-hermiston-or", "state": "or", "kind": "facility", "name": "AWS Hermiston Data Center Campuses", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Umatilla" ], "city": "Hermiston", "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. Hermiston signed urban growth boundary coadoption. Signed county ordinance is boundary/plan action, not all DC building permits, exactAWStenant, occupied campus or criticalIT.810acexpansionnotautomaticallydata-hallfootprint. October15,2025historicnotfutureOctober15,2026meeting. Attached city/exhibit records have separate scopes. 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.co.umatilla.or.us/fileadmin/user_upload/Community_Development/Planning/Ordinances/2025/Ordinance_2025-11.pdf", "host": "co.umatilla.or.us", "date": "2025-10-15", "published": "2025-10-15", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.59161, "lng": -118.73687, "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": "Hermiston signed urban growth boundary coadoption", "fields": { "agency": "Umatilla County, Oregon", "ordinance": "2025-11", "county_adoption_signature_date": "2025-10-15", "coadopted_city_ordinance": "Hermiston2374", "city_ordinance_adoption_date": "2025-09-08", "urban_growth_boundary_added_acres_approx": 810, "land_use_change": "Industrial comprehensive-plan designation, anticipating annexation/rezoning", "area_description": "south of EastFeedvilleRoad, north of FeedCanal, between SouthOttRoad and Highway395" }, "notes": [ "Signed county ordinance is boundary/plan action, not all DC building permits, exactAWStenant, occupied campus or criticalIT.810acexpansionnotautomaticallydata-hallfootprint. October15,2025historicnotfutureOctober15,2026meeting. Attached city/exhibit records have separate scopes.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.co.umatilla.or.us/fileadmin/user_upload/Community_Development/Planning/Ordinances/2025/Ordinance_2025-11.pdf", "host": "co.umatilla.or.us", "date": "2025-10-15", "published": "2025-10-15", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 42", "scope": "The original County ordinance in the inherited source list coadopts a Hermiston urban growth boundary and industrial comprehensive plan amendment. Its first two pages give an October 15, 2025 County action and the separate City ordinance reference. This is a land use boundary action. The selected pages do not establish the physical operating stage, exact component approvals or construction at every AWS Hermiston campus. The attached full City ordinance was not audited.", "fields": { "current_stage_evidence": { "outcome": "inherited_ordinance_is_boundary_policy_not_campus_operation", "scope": "The original County ordinance in the inherited source list coadopts a Hermiston urban growth boundary and industrial comprehensive plan amendment. Its first two pages give an October 15, 2025 County action and the separate City ordinance reference. This is a land use boundary action. The selected pages do not establish the physical operating stage, exact component approvals or construction at every AWS Hermiston campus. The attached full City ordinance was not audited." }, "source_read_scope": { "ordinance_text_pages": [ 1, 2 ], "attached_city_ordinance_not_reviewed": true, "physical_stage_and_parcel_permission_not_inferred": true } }, "notes": [ "The original County ordinance in the inherited source list coadopts a Hermiston urban growth boundary and industrial comprehensive plan amendment. Its first two pages give an October 15, 2025 County action and the separate City ordinance reference. This is a land use boundary action. The selected pages do not establish the physical operating stage, exact component approvals or construction at every AWS Hermiston campus. The attached full City ordinance was not audited.", "Identity, organization roles, locations, jurisdictions, quantities and physical opening fields stay unchanged. Source checks and prospective dates never establish an opening." ], "sources": [ { "url": "https://www.co.umatilla.or.us/fileadmin/user_upload/Community_Development/Planning/Ordinances/2025/Ordinance_2025-11.pdf", "host": "www.co.umatilla.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "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": "Hermiston · Umatilla · 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": "41059" } }, { "id": "aws-pdx154-boardman-airport-or", "state": "or", "kind": "facility", "name": "AWS PDX 154 (Boardman Airport Campus)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Morrow" ], "city": "Boardman", "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-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.. Conditional land-use approval is not permit completion or operational opening. Building and pond areas are separate; settlement about existing regional operations not proof this campus caused pollution. Original executed approvals, current operator disclosures and subsequent decisions take precedence. 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.tricitiesbusinessnews.com/articles/amazon-plans-another-data-center-southwest-of-tri-cities", "host": "tricitiesbusinessnews.com", "date": "2026-04-14", "published": "2026-04-14", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.41893, "lng": -119.58451, "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-round22-2026-10-14.json", "scope": "Named-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.", "fields": { "reported_context": "Tri-Cities reporting says Morrow planning commission approved PDX154 land use March 31 with airport, stormwater and wastewater conditions.", "independently_verified_current_operating_status": null }, "notes": [ "Conditional land-use approval is not permit completion or operational opening. Building and pond areas are separate; settlement about existing regional operations not proof this campus caused pollution.", "Original executed approvals, current operator disclosures and subsequent decisions take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.tricitiesbusinessnews.com/articles/amazon-plans-another-data-center-southwest-of-tri-cities", "host": "tricitiesbusinessnews.com", "date": "2026-04-14", "published": "2026-04-14", "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": "Boardman · Morrow · 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": "41049" } }, { "id": "aws-umatilla-city-or", "state": "or", "kind": "facility", "name": "AWS Umatilla Data Center Campus", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Umatilla" ], "city": "Umatilla", "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. historical Oregon multi-program incentive context,primaryMorrowprojectnotboundsite. June2023agenda cover conflicts with2022running header; exact document date held. AppletwoLRZprojects not necessarilytwo physical campuses. MainMorrowCounty proposed2.37Bproject and113Mestimatednetbenefit do not belong to either boundApplePrineville orAmazonUmatillacampus. Historical15yearregime notcurrent2026eligibility; no tax savings allocated perbuilding. 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.oregon.gov/biz/Publications/Boards/Business%20Oregon%20Commission/2023/AmazonSIPAgendaItem.pdf", "host": "oregon.gov", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.62556, "lng": -118.77393, "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": "historical Oregon multi-program incentive context,primaryMorrowprojectnotboundsite", "fields": { "historical_umatilla_amazon_sip_approval_year": 2017, "historical_prineville_apple_lrz_exempt_projects": 2, "historical_prineville_apple_lrz_term_years": 15, "historical_reporting_period": "2022-2023" }, "notes": [ "June2023agenda cover conflicts with2022running header; exact document date held. AppletwoLRZprojects not necessarilytwo physical campuses. MainMorrowCounty proposed2.37Bproject and113Mestimatednetbenefit do not belong to either boundApplePrineville orAmazonUmatillacampus. Historical15yearregime notcurrent2026eligibility; no tax savings allocated perbuilding.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.oregon.gov/biz/Publications/Boards/Business%20Oregon%20Commission/2023/AmazonSIPAgendaItem.pdf", "host": "oregon.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": "Umatilla · Umatilla · 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": "41059" } }, { "id": "boxminer-la-pine-or", "state": "or", "kind": "facility", "name": "Boxminer La Pine Bitcoin Mining Facility", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": true, "type": "Crypto/HPC (inventory classification)", "counties": [ "Deschutes" ], "city": "La Pine", "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-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.. Land-sale decision is not a permanent citywide ban. Developer revised job forecast and city challenged revenue estimates; no exact reliable investment or delivered jobs adopted. Original executed approvals, current operator disclosures and subsequent decisions take precedence. 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.opb.org/article/2026/05/28/la-pine-rejects-data-center-central-oregon/", "host": "opb.org", "date": "2026-05-29", "published": "2026-05-29", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://www.lapineoregon.gov/DocumentCenter/View/3374/061026-City-Council-Packet", "host": "www.lapineoregon.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "loc": { "lat": 43.91443, "lng": -121.2271, "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-round22-2026-10-14.json", "scope": "Named-site excerpt/source review; historical or proposed claims remain attributed. No entire-record certification.", "fields": { "reported_context": "OPB reports La Pine council unanimously declined pursuing Boxminer land sale after May 27 meeting.", "independently_verified_current_operating_status": null }, "notes": [ "Land-sale decision is not a permanent citywide ban. Developer revised job forecast and city challenged revenue estimates; no exact reliable investment or delivered jobs adopted.", "Original executed approvals, current operator disclosures and subsequent decisions take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.opb.org/article/2026/05/28/la-pine-rejects-data-center-central-oregon/", "host": "opb.org", "date": "2026-05-29", "published": "2026-05-29", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 42", "scope": "The City June 10 agenda packet contains a May 27, 2026 meeting account describing staff questions about the proposed Boxminer land sale and reporting a motion to conclude the purchase and sale matter. The Mayor and Recorder signature lines on those minutes are blank. This is a City published account with an unsigned minutes limitation. It does not certify later approval of those minutes, a completed property conveyance, current site construction, all future proposals being cancelled or a physical shutdown.", "fields": { "current_stage_evidence": { "outcome": "unsigned_city_meeting_account_and_land_sale_motion_not_current_physical_stage", "scope": "The City June 10 agenda packet contains a May 27, 2026 meeting account describing staff questions about the proposed Boxminer land sale and reporting a motion to conclude the purchase and sale matter. The Mayor and Recorder signature lines on those minutes are blank. This is a City published account with an unsigned minutes limitation. It does not certify later approval of those minutes, a completed property conveyance, current site construction, all future proposals being cancelled or a physical shutdown." }, "source_read_scope": { "text_pages": [ 4, 5, 6, 7 ], "visual_pages": [ 6, 8 ], "packet_pages_total": 112, "private_resident_names_and_forms_excluded": true, "remaining_packet_not_reviewed": true, "minutes_signature_fields_blank": true } }, "notes": [ "The City June 10 agenda packet contains a May 27, 2026 meeting account describing staff questions about the proposed Boxminer land sale and reporting a motion to conclude the purchase and sale matter. The Mayor and Recorder signature lines on those minutes are blank. This is a City published account with an unsigned minutes limitation. It does not certify later approval of those minutes, a completed property conveyance, current site construction, all future proposals being cancelled or a physical shutdown.", "Identity, organization roles, locations, jurisdictions, quantities and physical opening fields stay unchanged. Source checks and prospective dates never establish an opening." ], "sources": [ { "url": "https://www.lapineoregon.gov/DocumentCenter/View/3374/061026-City-Council-Packet", "host": "www.lapineoregon.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed government record" } ], "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": "La Pine · Deschutes · 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": "41017" } }, { "id": "copia-charlestown-data-center-hermiston-or", "state": "or", "kind": "facility", "name": "Charlestown Data Center and Battery Energy Storage System", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Umatilla" ], "city": "Hermiston", "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 content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.. Federal land application not approval or building. Related Snake River, Rhea and Nevada projects separate; no capacity given for Charlestown. Conflicting111vs140statecounts not reconciled as one census. Subsequent original decisions and current operator disclosures take precedence. 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.opb.org/article/2026/09/29/data-centers-proposed-federal-land-eastern-oregon/", "host": "opb.org", "date": "2026-09-29", "published": "2026-09-29", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.52081, "lng": -118.73066, "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-round24-2026-10-14.json", "scope": "Named content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.", "fields": { "reported_context": "Oregon Capital Chronicle via OPB reports Copia Charlestown application on106BLMacres and May8draft development plan.", "independently_verified_current_operating_status": null }, "notes": [ "Federal land application not approval or building. Related Snake River, Rhea and Nevada projects separate; no capacity given for Charlestown. Conflicting111vs140statecounts not reconciled as one census.", "Subsequent original decisions and current operator disclosures take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.opb.org/article/2026/09/29/data-centers-proposed-federal-land-eastern-oregon/", "host": "opb.org", "date": "2026-09-29", "published": "2026-09-29", "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": "Hermiston · Umatilla · 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": "41059" } }, { "id": "crane-pdx01-forest-grove-or", "state": "or", "kind": "facility", "name": "Crane PDX01", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Forest Grove", "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 content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.. First-building8MWinitial up-to47MWcap and approximate100MWwhole-site plan not additive. Air cooling applies first building only. Required road completion before occupancy and later phase uncertainty retained; no current opening inferred. Subsequent original decisions and current operator disclosures take precedence. 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://forestgrovenewstimes.com/2025/08/18/construction-boots-up-on-first-data-center-in-forest-grove/", "host": "forestgrovenewstimes.com", "date": "2025-08-18", "published": "2025-08-18", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://www.cranedc.com/data-centers/oregon-data-center", "host": "www.cranedc.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Reviewed operator source" } ], "loc": { "lat": 45.57581, "lng": -123.11603, "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-round24-2026-10-14.json", "scope": "Named content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.", "fields": { "reported_context": "Forest Grove News-Times reports July2025 Crane groundbreaking with2026first-building completion forecast.", "independently_verified_current_operating_status": null }, "notes": [ "First-building8MWinitial up-to47MWcap and approximate100MWwhole-site plan not additive. Air cooling applies first building only. Required road completion before occupancy and later phase uncertainty retained; no current opening inferred.", "Subsequent original decisions and current operator disclosures take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://forestgrovenewstimes.com/2025/08/18/construction-boots-up-on-first-data-center-in-forest-grove/", "host": "forestgrovenewstimes.com", "date": "2025-08-18", "published": "2025-08-18", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 42", "scope": "Crane current original Oregon page labels the campus Active Development and separately describes PDX01 phases and PDX02. Its advertised 2026 third quarter ready for service period has passed, but the page does not explicitly report actual commissioning or completion of the inherited PDX01 phase. Marketing specifications, remote hands terms and a passed target do not establish operation. The separate PDX02 scope, promised capacity and certifications are not merged or promoted.", "fields": { "current_stage_evidence": { "outcome": "current_active_development_page_and_past_ready_target_not_completion", "scope": "Crane current original Oregon page labels the campus Active Development and separately describes PDX01 phases and PDX02. Its advertised 2026 third quarter ready for service period has passed, but the page does not explicitly report actual commissioning or completion of the inherited PDX01 phase. Marketing specifications, remote hands terms and a passed target do not establish operation. The separate PDX02 scope, promised capacity and certifications are not merged or promoted." } }, "notes": [ "Crane current original Oregon page labels the campus Active Development and separately describes PDX01 phases and PDX02. Its advertised 2026 third quarter ready for service period has passed, but the page does not explicitly report actual commissioning or completion of the inherited PDX01 phase. Marketing specifications, remote hands terms and a passed target do not establish operation. The separate PDX02 scope, promised capacity and certifications are not merged or promoted.", "Identity, organization roles, locations, jurisdictions, quantities and physical opening fields stay unchanged. Source checks and prospective dates never establish an opening." ], "sources": [ { "url": "https://www.cranedc.com/data-centers/oregon-data-center", "host": "www.cranedc.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": "Forest Grove · 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": "crane-pdx02-forest-grove-or", "state": "or", "kind": "facility", "name": "Crane PDX02", "group": "proposed", "status": "Provider listed proposal", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Forest Grove", "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. Crane Forest Grove site phases and campus mismatch. NamedPDX02notwholecampus100plus.24+24+48=96doesnotreconcileheadline100plus,phase/scoperoundingheld. PowerbasisnotexplicitcriticalITforcapacities. Q32026targetnotobservedservice. PUEdesignnotmeasuredannualaverage. Incentive/LEEDclaimsnotindependentapprovedaward/certifierinspection. 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.cranedc.com/data-centers/oregon-data-center", "host": "cranedc.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.52756, "lng": -123.0961, "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-round10-2026-10-14.json", "scope": "Crane Forest Grove site phases and campus mismatch", "fields": { "operator": "Crane Data Centers", "market": "Forest Grove, Oregon", "named_phases": [ { "site": "PDX01 phase1", "capacity_mw": 24, "whitespace_sqft": 36000, "adjacent_flex_sqft": 6400 }, { "site": "PDX01 phase2", "additional_capacity_mw": 24, "additional_whitespace_sqft": 36000, "additional_flex_sqft": 6400 }, { "site": "PDX02", "capacity_mw_approx": 48, "area_sqft_approx": 150000 } ], "campus_headline_capacity_mw_min_exclusive": 100, "historical_service_target_quarter": "2026-Q3", "design_pue_at_full_it_load": 1.3 }, "notes": [ "NamedPDX02notwholecampus100plus.24+24+48=96doesnotreconcileheadline100plus,phase/scoperoundingheld. PowerbasisnotexplicitcriticalITforcapacities. Q32026targetnotobservedservice. PUEdesignnotmeasuredannualaverage. Incentive/LEEDclaimsnotindependentapprovedaward/certifierinspection.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.cranedc.com/data-centers/oregon-data-center", "host": "cranedc.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 69", "scope": "The complete original provider page labels its Forest Grove campus active development and specifically lists PDX02 separately from PDX01 phases. This supports a provider listed proposal for the named component. The displayed third quarter of 2026 ready for service forecast does not independently establish accomplished commissioning, actual construction completion or existing computing service. No PDX01 phase or technical design quantity is transferred to PDX02.", "fields": { "current_stage_evidence": { "outcome": "provider_listed_specific_pdx02_proposal", "scope": "The complete original provider page labels its Forest Grove campus active development and specifically lists PDX02 separately from PDX01 phases. This supports a provider listed proposal for the named component. The displayed third quarter of 2026 ready for service forecast does not independently establish accomplished commissioning, actual construction completion or existing computing service. No PDX01 phase or technical design quantity is transferred to PDX02." }, "source_read_scope": { "complete_original_oregon_campus_body_read": true, "pdx01_phases_and_pdx02_separate": true, "passed_ready_for_service_forecast_not_completion": true, "no_measured_capacity_or_first_opening_export": true } }, "notes": [ "The complete original provider page labels its Forest Grove campus active development and specifically lists PDX02 separately from PDX01 phases. This supports a provider listed proposal for the named component. The displayed third quarter of 2026 ready for service forecast does not independently establish accomplished commissioning, actual construction completion or existing computing service. No PDX01 phase or technical design quantity is transferred to PDX02.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.cranedc.com/data-centers/oregon-data-center", "host": "www.cranedc.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "Forest Grove · Washington · Source context reviewed", "status_scope": "The complete original provider page labels its Forest Grove campus active development and specifically lists PDX02 separately from PDX01 phases. This supports a provider listed proposal for the named component. The displayed third quarter of 2026 ready for service forecast does not independently establish accomplished commissioning, actual construction completion or existing computing service. No PDX01 phase or technical design quantity is transferred to PDX02.", "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": "digital-realty-pdx10-or", "state": "or", "kind": "facility", "name": "Digital Realty PDX10", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "3825 NW Aloclek Street, Hillsboro, OR 97124", "who": "Digital Realty", "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. Named facility page and total-building-size field matched. Gross building size is not IT white space. Current advertisement does not certify utilization, uptime, opening date or independently measured power. 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.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "digitalrealty.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=3825+NW+Aloclek+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-16", "label": "Published-address street-range query for Digital Realty PDX10" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census geocoder method: calculated address-range locations, not surveyed buildings" } ], "loc": { "lat": 45.59199, "lng": -123.07456, "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_facility_code": "PDX10", "published_address": "3825 NW Aloclek Street, Hillsboro, OR 97124", "advertised_building_sqft": 48000 }, "notes": [ "Named facility page and total-building-size field matched. Gross building size is not IT white space. Current advertisement does not certify utilization, uptime, opening date or independently measured power.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "digitalrealty.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Digital Realty U.S. property review October 16", "scope": "Explicit current provider-code, service-component and published-address review. No physical-site census, ownership, current metered demand, full-campus delivery or coordinate certification.", "fields": { "operator_location_codes": [ "PDX10" ], "current_service_scope": "Digital Realty currently markets colocation and connectivity services under PDX10. This supports an operating service component in the existing research context, not complete campus delivery, full-building operation, legal ownership, present vacancy or a commissioned IT-load figure.", "identity_scope": "The provider-qualified code and published locality match this existing ID. Codes used by CoreSite, Equinix, NTT or other providers are not interchangeable. Shared street addresses or carrier hotels do not certify separate physical sites or establish whole-building ownership.", "technical_scope": "The current listing is a commercial service/specification source. No current critical IT MW, utility-service authorization, annual energy, measured water series or construction/opening day is normalized from generic power, cooling, density, certification or renewable-energy claims.", "location_scope": "The published address is source context only. Inherited coordinates, precision, city/county jurisdiction and parcel identity are unchanged; the point has not been matched to the street address.", "published_address_PDX10": "3825 NW Aloclek Street, Hillsboro, OR 97124" }, "notes": [ "Operating phase refers to a currently marketed service component at the named code/address, not a site inspection or complete campus.", "The current property pages are undated. Review date is not a publication day, physical opening day or technical-capacity as-of date. Existing addresses were blank; no inherited point is upgraded by assumption." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Current Digital Realty PDX10 property page" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "Digital Realty address and location review October 16", "scope": "Explicit provider-qualified address and location review. Street-range points and partial county reference areas are different methods; neither certifies a roof, owner, complete campus or distinct physical site.", "fields": { "published_coordinate_context": { "code": "PDX10", "operator_point": [ -122.892017, 45.547609 ], "scope": "Publisher map metadata, not a surveyed roof, parcel boundary, title, technical-capacity or opening assertion." }, "census_address_context": { "query_address": "3825 NW Aloclek Street, Hillsboro, OR 97124", "match_count": 1, "match": { "matchedAddress": "3825 NW ALOCLEK PL, HILLSBORO, OR, 97124", "coordinates": { "x": -122.891087088882, "y": 45.547264552374 }, "addressComponents": { "zip": "97124", "streetName": "ALOCLEK", "preType": "", "city": "HILLSBORO", "preDirection": "NW", "suffixDirection": "", "fromAddress": "3601", "state": "OR", "suffixType": "PL", "toAddress": "3999", "suffixQualifier": "", "preQualifier": "" }, "tigerLine": { "side": "L", "tigerLineId": "158201258" } }, "benchmark": "Public_AR_Current", "vintage": "Current_Current", "scope": "Calculated address-range point, not a building center, parcel, suite or actual operation verification." }, "coordinate_comparison": { "operator_to_census_m": 81.9, "operator_to_inherited_m": 3.3, "scope": "Derived distance comparison only; proximity alone does not resolve provider or physical-site identity." }, "location_hold": { "decision": "retain_approximate_pending_explicit_review", "reason": "Published Aloclek Street is returned as Aloclek Place. The literal suffix difference is retained; no address or point is normalized by assumption." } }, "notes": [ "Current marketed-service stage, operator code, published address, all technical quantities and dated events remain unchanged.", "Publication dates are unknown. Retrieval dates, Census Current_Current naming, county tax year, edit timestamps and physical milestones are separate scopes." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Current Digital Realty PDX10 property page" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=3825+NW+Aloclek+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-16", "label": "Published-address street-range query for Digital Realty PDX10" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "overnight-locations-2026-10-17", "scope": "Published-address and street-location review only. Existing stage, identity, quantities and legal jurisdiction remain separate; no physical-site census or parcel certification.", "fields": { "published_address_review": { "provider": "Digital Realty", "code": "PDX10", "published_address": "3825 NW Aloclek Street, Hillsboro, OR 97124", "visible_address_context": "PDX10\n3825 NW Aloclek Street, Hillsboro, OR 97124", "scope": "Named provider service/address context; current ownership, delivered whole-campus capacity and distinct physical-site identity are not certified." }, "census_street_reference": { "query": { "address": { "address": "3825 NW Aloclek Street, Hillsboro, OR 97124" }, "vintage": { "isDefault": true, "id": "4", "vintageName": "Current_Current", "vintageDescription": "Current Vintage - Current Benchmark" }, "benchmark": { "isDefault": true, "benchmarkDescription": "Public Address Ranges - Current Benchmark", "id": "4", "benchmarkName": "Public_AR_Current" } }, "matches": [ { "tigerLine": { "side": "L", "tigerLineId": "158201258" }, "coordinates": { "x": -122.891087088882, "y": 45.547264552374 }, "addressComponents": { "zip": "97124", "streetName": "ALOCLEK", "preType": "", "city": "HILLSBORO", "preDirection": "NW", "suffixDirection": "", "fromAddress": "3601", "state": "OR", "suffixType": "PL", "toAddress": "3999", "suffixQualifier": "", "preQualifier": "" }, "matchedAddress": "3825 NW ALOCLEK PL, HILLSBORO, OR, 97124" } ], "method": "Interpolated Census street address range, not roof, parcel or proof a structure exists." }, "operator_coordinate_context": { "point": [ -122.892017, 45.547609 ], "operator_to_census_m": 81.9, "adopted": false, "scope": "Embedded operator map coordinates retained as a separate source claim; not independently certified building or parcel geometry." }, "location_review_decision": { "decision": "hold_approximate", "reason": "Operator publishes Street while Census matches Place; no primary bridge resolving the suffix discrepancy.", "prior_to_census_m": 78.7, "not_a_roof_or_parcel": true, "physical_site_count_eligible": false, "held_scope": "Specific location/address discrepancy, not inferred closure or absence of a facility." } }, "notes": [ "Operator publishes Street while Census matches Place; no primary bridge resolving the suffix discrepancy." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-17", "label": "Current Digital Realty PDX10 named property and published address" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=3825+NW+Aloclek+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census address-range response for PDX10" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census geocoder method: calculated address-range locations, not surveyed buildings" } ], "checked": "2026-10-17", "whole_record_certified": false }, { "overlay": "Company role source check52, October24,2026", "scope": "Digital Realty identifies the named PDX10 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. Hillsboro is the service municipality; Portland is the market. PDX10 and PDX12 remain distinct.", "fields": { "company_association": { "name": "Digital Realty", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Digital Realty identifies the named PDX10 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. Hillsboro is the service municipality; Portland is the market. PDX10 and PDX12 remain distinct." }, "provider_role": "operator" }, "notes": [ "Digital Realty identifies the named PDX10 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. Hillsboro is the service municipality; Portland is the market. PDX10 and PDX12 remain distinct." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx10", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "Digital Realty currently markets colocation and connectivity services under PDX10. This supports an operating service component in the existing research context, not complete campus delivery, full-building operation, legal ownership, present vacancy or a commissioned IT-load figure.", "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": "digital-realty-pdx12-or", "state": "or", "kind": "facility", "name": "Digital Realty PDX12", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "5870 NE Schaaf Street, Hillsboro, OR 97124", "who": "Digital Realty", "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. Named facility page and total-building-size field matched. Gross building size is not IT white space. Current advertisement does not certify utilization, uptime, opening date or independently measured power. 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.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "digitalrealty.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=5870+NE+Schaaf+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-16", "label": "Published-address street-range query for Digital Realty PDX12" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census geocoder method: calculated address-range locations, not surveyed buildings" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Washington_County_Taxlots/FeatureServer/0/query?where=TLNO%3D%271N215D090012%27&outFields=OBJECTID%2CTLNO%2CMAPNO%2CTLNO5&returnGeometry=true&outSR=4326&resultRecordCount=20&f=json", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact public reference parcel feature" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-122.92438119234639%2C45.56530591088753%2C-122.9153988076536%2C45.571594089112466&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, acquisition date unknown" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Washington_County_Taxlots/FeatureServer/0?f=pjson", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel method and attribution" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Intermap/Situs_address_WMAS/MapServer/0/query?where=HOUSE_NUMBER%3D%275870%27+AND+UPPER%28STREET_NAME%29%3D%27SCHAAF%27&outFields=OBJECTID%2CA_ID%2CSTATUS%2CHOUSE_NUMBER%2CPRE_DIRECTION%2CSTREET_NAME%2CSTREET_TYPE%2CCITY%2CSTATE%2CZIP%2CTAXLOT%2CFULLADDRESS%2CADDRESS_1%2CUNIT_NUMBER%2CBUILDING_NUMBER&returnGeometry=true&outSR=4326&resultRecordCount=30&f=json", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Exact official service situs linked to this same reference parcel" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Intermap/Situs_address_WMAS/MapServer/0?f=pjson", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Official situs field definitions and dataset attribution" }, { "url": "https://www.washingtoncountyor.gov/gis", "host": "www.washingtoncountyor.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official agency dataset use, update or boundary limits" } ], "loc": { "lng": -122.91989, "lat": 45.56845, "precision": "approximate", "basis": "Approximate reference parcel center for Digital Realty service address 5870 NE Schaaf Street, Hillsboro, OR 97124. Official county tax reference 1N215D090012 only, not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "operator_facility_code": "PDX12", "published_address": "5870 NE Schaaf Street, Hillsboro, OR 97124", "advertised_building_sqft": 546000 }, "notes": [ "Named facility page and total-building-size field matched. Gross building size is not IT white space. Current advertisement does not certify utilization, uptime, opening date or independently measured power.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "digitalrealty.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Digital Realty U.S. property review October 16", "scope": "Explicit current provider-code, service-component and published-address review. No physical-site census, ownership, current metered demand, full-campus delivery or coordinate certification.", "fields": { "operator_location_codes": [ "PDX12" ], "current_service_scope": "Digital Realty currently markets colocation and connectivity services under PDX12. This supports an operating service component in the existing research context, not complete campus delivery, full-building operation, legal ownership, present vacancy or a commissioned IT-load figure.", "identity_scope": "The provider-qualified code and published locality match this existing ID. Codes used by CoreSite, Equinix, NTT or other providers are not interchangeable. Shared street addresses or carrier hotels do not certify separate physical sites or establish whole-building ownership.", "technical_scope": "The current listing is a commercial service/specification source. No current critical IT MW, utility-service authorization, annual energy, measured water series or construction/opening day is normalized from generic power, cooling, density, certification or renewable-energy claims.", "location_scope": "The published address is source context only. Inherited coordinates, precision, city/county jurisdiction and parcel identity are unchanged; the point has not been matched to the street address.", "published_address_PDX12": "5870 NE Schaaf Street, Hillsboro, OR 97124" }, "notes": [ "Operating phase refers to a currently marketed service component at the named code/address, not a site inspection or complete campus.", "The current property pages are undated. Review date is not a publication day, physical opening day or technical-capacity as-of date. Existing addresses were blank; no inherited point is upgraded by assumption." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Current Digital Realty PDX12 property page" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "Digital Realty address and location review October 16", "scope": "Explicit provider-qualified address and location review. Street-range points and partial county reference areas are different methods; neither certifies a roof, owner, complete campus or distinct physical site.", "fields": { "published_coordinate_context": { "code": "PDX12", "operator_point": [ -122.9183796, 45.56792049 ], "scope": "Publisher map metadata, not a surveyed roof, parcel boundary, title, technical-capacity or opening assertion." }, "census_address_context": { "query_address": "5870 NE Schaaf Street, Hillsboro, OR 97124", "match_count": 0, "match": null, "benchmark": "Public_AR_Current", "vintage": "Current_Current", "scope": "Calculated address-range point, not a building center, parcel, suite or actual operation verification." }, "coordinate_comparison": { "operator_to_census_m": null, "operator_to_inherited_m": 179.1, "scope": "Derived distance comparison only; proximity alone does not resolve provider or physical-site identity." }, "location_hold": { "decision": "retain_approximate_pending_explicit_review", "reason": "No Census match for the exact published query. Operator metadata alone is not adopted; inherited approximate location remains." } }, "notes": [ "Current marketed-service stage, operator code, published address, all technical quantities and dated events remain unchanged.", "Publication dates are unknown. Retrieval dates, Census Current_Current naming, county tax year, edit timestamps and physical milestones are separate scopes." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-16", "label": "Current Digital Realty PDX12 property page" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=5870+NE+Schaaf+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-16", "label": "Published-address street-range query for Digital Realty PDX12" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "overnight-locations-2026-10-17", "scope": "Published-address and street-location review only. Existing stage, identity, quantities and legal jurisdiction remain separate; no physical-site census or parcel certification.", "fields": { "published_address_review": { "provider": "Digital Realty", "code": "PDX12", "published_address": "5870 NE Schaaf Street, Hillsboro, OR 97124", "visible_address_context": "PDX12\n5870 NE Schaaf Street, Hillsboro, OR 97124", "scope": "Named provider service/address context; current ownership, delivered whole-campus capacity and distinct physical-site identity are not certified." }, "census_street_reference": { "query": { "address": { "address": "5870 NE Schaaf Street, Hillsboro, OR 97124" }, "vintage": { "isDefault": true, "id": "4", "vintageName": "Current_Current", "vintageDescription": "Current Vintage - Current Benchmark" }, "benchmark": { "isDefault": true, "benchmarkDescription": "Public Address Ranges - Current Benchmark", "id": "4", "benchmarkName": "Public_AR_Current" } }, "matches": [], "method": "Interpolated Census street address range, not roof, parcel or proof a structure exists." }, "operator_coordinate_context": { "point": [ -122.9183796, 45.56792049 ], "operator_to_census_m": null, "adopted": false, "scope": "Embedded operator map coordinates retained as a separate source claim; not independently certified building or parcel geometry." }, "location_review_decision": { "decision": "hold_approximate", "reason": "The current full published address returns zero Census address-range matches; no substitute street point chosen.", "prior_to_census_m": null, "not_a_roof_or_parcel": true, "physical_site_count_eligible": false, "held_scope": "Specific location/address discrepancy, not inferred closure or absence of a facility." } }, "notes": [ "The current full published address returns zero Census address-range matches; no substitute street point chosen." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-17", "label": "Current Digital Realty PDX12 named property and published address" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=5870+NE+Schaaf+Street%2C+Hillsboro%2C+OR+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census address-range response for PDX12" }, { "url": "https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-17", "label": "Census geocoder method: calculated address-range locations, not surveyed buildings" } ], "checked": "2026-10-17", "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 26, October 23, 2026", "scope": "Approximate remains approximate. One source bound county reference parcel only. All protected native facts remain exact.", "fields": { "location_review_decision": { "location": { "lng": -122.91989, "lat": 45.56845, "precision": "approximate", "basis": "Approximate reference parcel center for Digital Realty service address 5870 NE Schaaf Street, Hillsboro, OR 97124. Official county tax reference 1N215D090012 only, not a roof, surveyed title, tenant unit or full campus. Aerial acquisition date is unknown and may predate construction." }, "reference_method": "Approximate county reference parcel center", "reference_parcel": { "identifier": "1N215D090012", "identifier_field": "TLNO", "objectid": 200128, "agency": "Washington County Oregon Cartography Division and GIS", "agency_situs_field": null, "agency_situs": null, "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": "32553dd6d69829440340f5e4e59028ba44f26bfaee73711029df89450a808957" }, "operator_coordinates_adopted": false, "census_range_adopted": false } }, "notes": [ "The exact current named operator service street joins to one bounded county reference parcel. The mathematical area center remains approximate, not a surveyed roof, title, ownership finding, tenant unit, independent building or full campus boundary.", "All original native identity, status, physical dates, quantities, roles, canonical address and jurisdiction wrappers remain exact. Inherited location and source history remain retained. Raw parcel geometry is not exported.", "Official aerial setting was actually viewed. Acquisition date is unknown and may predate construction. No residential roof or unverified completion milestone is selected.", "The current Washington County situs point gives 5870 NE Schaaf Street, Hillsboro, OR 97124 and tax lot 1N215D090012. It lies inside the exact same tax lot polygon. County metadata says tax lots are dissolved multipart features, some are not digitized and some heads up digitization may lack the precision represented by imagery. Tax lot numbering does not certify a condominium tenant unit, separate roof, title or full campus. The mathematical parcel center remains approximate." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Current exact named facility service address section" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Washington_County_Taxlots/FeatureServer/0/query?where=TLNO%3D%271N215D090012%27&outFields=OBJECTID%2CTLNO%2CMAPNO%2CTLNO5&returnGeometry=true&outSR=4326&resultRecordCount=20&f=json", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "One exact public reference parcel feature" }, { "url": "https://basemap.nationalmap.gov/arcgis/rest/services/USGSImageryOnly/MapServer/export?bbox=-122.92438119234639%2C45.56530591088753%2C-122.9153988076536%2C45.571594089112466&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, acquisition date unknown" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Washington_County_Taxlots/FeatureServer/0?f=pjson", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Official reference parcel method and attribution" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Intermap/Situs_address_WMAS/MapServer/0/query?where=HOUSE_NUMBER%3D%275870%27+AND+UPPER%28STREET_NAME%29%3D%27SCHAAF%27&outFields=OBJECTID%2CA_ID%2CSTATUS%2CHOUSE_NUMBER%2CPRE_DIRECTION%2CSTREET_NAME%2CSTREET_TYPE%2CCITY%2CSTATE%2CZIP%2CTAXLOT%2CFULLADDRESS%2CADDRESS_1%2CUNIT_NUMBER%2CBUILDING_NUMBER&returnGeometry=true&outSR=4326&resultRecordCount=30&f=json", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Exact official service situs linked to this same reference parcel" }, { "url": "https://pappgiswa1.co.washington.or.us/arcgispub/rest/services/Intermap/Situs_address_WMAS/MapServer/0?f=pjson", "host": "pappgiswa1.co.washington.or.us", "published": "", "date": "", "checked": "2026-10-23", "label": "Official situs field definitions and dataset attribution" }, { "url": "https://www.washingtoncountyor.gov/gis", "host": "www.washingtoncountyor.gov", "published": "", "date": "", "checked": "2026-10-23", "label": "Official agency dataset use, update or boundary limits" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Company role source check52, October24,2026", "scope": "Digital Realty identifies the named PDX12 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. The stated floor area is advertising context only. PDX12 remains distinct from the PDX10 component.", "fields": { "company_association": { "name": "Digital Realty", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Digital Realty identifies the named PDX12 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. The stated floor area is advertising context only. PDX12 remains distinct from the PDX10 component." }, "provider_role": "operator" }, "notes": [ "Digital Realty identifies the named PDX12 facility and its published service street in the main body of its own location page and advertises its colocation space and facility services. Operator per source records the Digital Realty provider brand for that component 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 area, redundancy, renewable percentages, certifications, sustainability and market superlatives are not independently verified measurements, legal title or environmental outcomes. Metropolitan market labels do not replace the service municipality. The source publication date is unknown. The stated floor area is advertising context only. PDX12 remains distinct from the PDX10 component." ], "sources": [ { "url": "https://www.digitalrealty.com/data-centers/americas/portland/pdx12", "host": "www.digitalrealty.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "Hillsboro · Washington · Source context reviewed", "status_scope": "Digital Realty currently markets colocation and connectivity services under PDX12. This supports an operating service component in the existing research context, not complete campus delivery, full-building operation, legal ownership, present vacancy or a commissioned IT-load figure." }, { "id": "dmg-blockchain-boardman-or", "state": "or", "kind": "facility", "name": "DMG Blockchain Boardman Facility", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": true, "type": "Crypto/HPC (inventory classification)", "counties": [ "Morrow" ], "city": "Boardman", "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 content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.. Not evidence closing occurred.50MWcriticalIT refers to ChristinaLakeCANADA, not BoardmanOregon. AI-generated host summary excluded in favor of reproduced issuer body. Subsequent original decisions and current operator disclosures take precedence. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Canadian AI facilities and plans are separate. Later issuer MD&A supersedes initial timing expectations. Original issuer-authored filing retained via CEO.ca SEDAR-document mirror. No claim mirror is issuer domain or regulatory attestation. Pages3,6,23 visually inspected. Connected3.75 MW described on page3 is not critical IT or evidence DMG acquired/commissioned the building. Later August27 results link was403 and not retried; latest unreviewed results could contain later developments.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.stocktitan.net/news/DMGGF/dmg-blockchain-solutions-announces-ai-strategy-update-and-november-291zgfegqhps.html", "host": "stocktitan.net", "date": "2025-12-04", "published": "2025-12-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://www.dmgblockchain.com/p/dmg-expands-to-the-u-s-announces-asset-purchase-for-oregon-data-center", "host": "dmgblockchain.com", "date": "2025-11-04", "published": "2025-11-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://ceo.ca/api/sedar-document/DMGI-2026-05-26-interim-mda-english-bd9f.pdf", "host": "ceo.ca", "date": "2026-05-26", "published": "2026-05-26", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.44803, "lng": -119.61627, "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-round24-2026-10-14.json", "scope": "Named content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.", "fields": { "reported_context": "Issuer release reproduced by StockTitan says Boardman purchase still expected in coming weeks.", "independently_verified_current_operating_status": null }, "notes": [ "Not evidence closing occurred.50MWcriticalIT refers to ChristinaLakeCANADA, not BoardmanOregon. AI-generated host summary excluded in favor of reproduced issuer body.", "Subsequent original decisions and current operator disclosures take precedence.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.stocktitan.net/news/DMGGF/dmg-blockchain-solutions-announces-ai-strategy-update-and-november-291zgfegqhps.html", "host": "stocktitan.net", "date": "2025-12-04", "published": "2025-12-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "regional-development-review-round24-2026-10-14.json", "scope": "Named content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.", "fields": { "reported_context": "Issuer announces intended letter-agreement purchase of 27600-square-foot building with 3.75 MW access, not a closed acquisition.", "critical_it_mw": null }, "notes": [ "Canadian AI facilities and plans are separate. Later issuer MD&A supersedes initial timing expectations.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.dmgblockchain.com/p/dmg-expands-to-the-u-s-announces-asset-purchase-for-oregon-data-center", "host": "dmgblockchain.com", "date": "2025-11-04", "published": "2025-11-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "regional-development-review-round24-2026-10-14.json", "scope": "Named content personally reviewed; no whole-record certification. Dates and forecasts remain source-specific.", "fields": { "reported_context": "Issuer MD&A for six months ended March31,2026 repeats February6 withdrawal of acquisition timing guidance and states completion uncertain.", "acquisition_completion_verified": false, "acquisition_timing_guidance_withdrawn_date": "2026-02-06", "critical_it_mw": null }, "notes": [ "Original issuer-authored filing retained via CEO.ca SEDAR-document mirror. No claim mirror is issuer domain or regulatory attestation.", "Pages3,6,23 visually inspected. Connected3.75 MW described on page3 is not critical IT or evidence DMG acquired/commissioned the building.", "Later August27 results link was403 and not retried; latest unreviewed results could contain later developments.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://ceo.ca/api/sedar-document/DMGI-2026-05-26-interim-mda-english-bd9f.pdf", "host": "ceo.ca", "date": "2026-05-26", "published": "2026-05-26", "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": "Boardman · Morrow · 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": "41049" } }, { "id": "edgeconnex-por01-por02-hillsboro-campus-or", "state": "or", "kind": "facility", "name": "EdgeConneX POR01/POR02 (Hillsboro campus)", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "EdgeConneX", "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. POR01/02campus with plannedPOR03context. POR02total16850floorincludesplannedhall2. POR03plannedup21MWisseparateaddition, notonlinePOR01/02capacity. NoaggregateoperatingcampusMW. 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.edgeconnex.com/locations/americas/portland-or/", "host": "edgeconnex.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.5521, "lng": -123.14455, "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": "captured-operator-review-round6-2026-10-14.json", "scope": "POR01/02campus with plannedPOR03context", "fields": { "por01": { "facility_area_sqft": 39400, "raised_floor_sqft": 18700 }, "por02": { "phase1_raised_floor_sqft": 8300, "planned_hall2_raised_floor_sqft": 8550, "initial_power_mw": 3, "planned_total_power_mw": 6 }, "power_basis": "N+1power not explicitcriticalIT" }, "notes": [ "POR02total16850floorincludesplannedhall2. POR03plannedup21MWisseparateaddition, notonlinePOR01/02capacity. NoaggregateoperatingcampusMW.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.edgeconnex.com/locations/americas/portland-or/", "host": "edgeconnex.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": "EdgeConneX describes current cloud access at POR01 and POR02 while keeping POR02 additional halls and POR03 as planned. Only an operating phase of this 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": "EdgeConneX describes current cloud access at POR01 and POR02 while keeping POR02 additional halls and POR03 as planned. Only an operating phase of this 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": [ "EdgeConneX describes current cloud access at POR01 and POR02 while keeping POR02 additional halls and POR03 as planned. Only an operating phase of this existing campus is supported." ], "sources": [ { "url": "https://www.edgeconnex.com/locations/americas/portland-or/", "host": "www.edgeconnex.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 check24, October23,2026", "scope": "EdgeConneX names this facility or the retained campus components on its current website and offers colocation and facility services there. Operator per source is the attributed provider brand relationship only, not a finding of the legal operating entity or property title. No physical status, coordinates, street address, quantity, cooling volume, air permit, certification, measured reliability, environmental compliance, tenant identity or completed expansion is adopted. First publication dates remain unknown; retrieval does not establish a physical opening date. The existing combined POR01 and POR02 campus record is retained. The page identifies both and separately labels POR03 a planned addition. No new physical count, POR03 operation, individual hall completion or combined capacity is inferred.", "fields": { "company_association": { "name": "EdgeConneX", "role": "operator", "identity_scope": "provider_brand_only", "scope": "EdgeConneX names this facility or the retained campus components on its current website and offers colocation and facility services there. Operator per source is the attributed provider brand relationship only, not a finding of the legal operating entity or property title. No physical status, coordinates, street address, quantity, cooling volume, air permit, certification, measured reliability, environmental compliance, tenant identity or completed expansion is adopted. First publication dates remain unknown; retrieval does not establish a physical opening date. The existing combined POR01 and POR02 campus record is retained. The page identifies both and separately labels POR03 a planned addition. No new physical count, POR03 operation, individual hall completion or combined capacity is inferred." }, "provider_role": "operator" }, "notes": [ "EdgeConneX names this facility or the retained campus components on its current website and offers colocation and facility services there. Operator per source is the attributed provider brand relationship only, not a finding of the legal operating entity or property title. No physical status, coordinates, street address, quantity, cooling volume, air permit, certification, measured reliability, environmental compliance, tenant identity or completed expansion is adopted. First publication dates remain unknown; retrieval does not establish a physical opening date. The existing combined POR01 and POR02 campus record is retained. The page identifies both and separately labels POR03 a planned addition. No new physical count, POR03 operation, individual hall completion or combined capacity is inferred." ], "sources": [ { "url": "https://www.edgeconnex.com/locations/americas/portland-or/", "host": "www.edgeconnex.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Current first party named facility, provider relationship 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": "Exact site not published; shown at county level", "summary": "Hillsboro · Washington · Source context reviewed", "status_scope": "EdgeConneX describes current cloud access at POR01 and POR02 while keeping POR02 additional halls and POR03 as planned. Only an operating phase of this 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.", "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": "flexential-portland-hillsboro-1-pdx01-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 1 (PDX01)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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 facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime. 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.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.53239, "lng": -123.05528, "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-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 1 (PDX01)", "publisher_reported_footprint_sqft": 85388, "publisher_reported_critical_power_mw": 5.3, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false }, "notes": [ "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check65, October24,2026", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 62 and 63. The Hillsboro 1 profile identifies the retained named Flexential service location. It remains separate from Hillsboro 2 and 3and does not establish a new surveyed property or measured performance finding. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted.", "fields": { "company_association": { "name": "Flexential", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 62 and 63. The Hillsboro 1 profile identifies the retained named Flexential service location. It remains separate from Hillsboro 2 and 3and does not establish a new surveyed property or measured performance finding. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." }, "provider_role": "operator" }, "notes": [ "Flexential identifies the named location in the original fleet guide, PDF pages 62 and 63. The Hillsboro 1 profile identifies the retained named Flexential service location. It remains separate from Hillsboro 2 and 3and does not establish a new surveyed property or measured performance finding. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "flexential-portland-hillsboro-2-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 2", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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 facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime. 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.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.61493, "lng": -123.11368, "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-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 2", "publisher_reported_footprint_sqft": 242683, "publisher_reported_critical_power_mw": 18, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false }, "notes": [ "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check65, October24,2026", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 64 and 65. The Hillsboro 2 profile identifies a distinct named Flexential service context. Named subsea cable connectivity does not admit a fiber route, cable landing property or additional building. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted.", "fields": { "company_association": { "name": "Flexential", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 64 and 65. The Hillsboro 2 profile identifies a distinct named Flexential service context. Named subsea cable connectivity does not admit a fiber route, cable landing property or additional building. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." }, "provider_role": "operator" }, "notes": [ "Flexential identifies the named location in the original fleet guide, PDF pages 64 and 65. The Hillsboro 2 profile identifies a distinct named Flexential service context. Named subsea cable connectivity does not admit a fiber route, cable landing property or additional building. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "flexential-portland-hillsboro-3-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 3", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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 facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime. 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.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Original May28,2026operator paragraph explicitly identifies Hillsboro3at5419NEStarrBoulevard; extracted original text view" }, { "url": "https://www.flexential.com/system/files/file/2024-01/Flexential%20-%202023%20ISO%2027001%20Surveillance%20-%20Certificate_1831866-4.pdf", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Original issued certificate computing location table, historical street context only" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=5419+NE+Starr+Boulevard%2C+Hillsboro%2C+Oregon+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-24", "label": "Complete unique literal published street range, raw version retained" }, { "url": "https://imagery.nationalmap.gov/arcgis/rest/services/USGSNAIPPlus/ImageServer/exportImage?bbox=-122.94325659921128%2C45.555638288537544%2C-122.92914340078872%2C45.56551971146245&bboxSR=4326&imageSR=3857&size=600%2C600&format=png&f=image", "host": "imagery.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-24", "label": "Actually viewed source setting, acquisition date unknown" } ], "loc": { "lng": -122.9362, "lat": 45.560579, "precision": "address", "basis": "Operator facility documents identify 5419 NE Starr Boulevard, Hillsboro, Oregon 97124. One complete unique Census street range supports this calculated reference inside Washington County. This reference does not select a roof, tenant floor, surveyed parcel or complete campus. Source dates do not establish current operation. Imagery acquisition date is unknown and may predate construction." }, "reviewed_evidence": [ { "overlay": "operator-primary-review-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 3", "publisher_reported_footprint_sqft": 358000, "publisher_reported_critical_power_mw": 36, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false }, "notes": [ "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 2 location cohort 64, 2026-10-24", "scope": "Original operator published computing street identity and calculated street reference only. The explicit Las Vegas street set remains approximate. Existing status, other facts and all historical source limitations stay unchanged. No current certification, technical figure, ownership, roof, floor or complete campus is certified.", "fields": { "location_review_decision": { "location": { "lng": -122.9362, "lat": 45.560579, "precision": "address", "basis": "Operator facility documents identify 5419 NE Starr Boulevard, Hillsboro, Oregon 97124. One complete unique Census street range supports this calculated reference inside Washington County. This reference does not select a roof, tenant floor, surveyed parcel or complete campus. Source dates do not establish current operation. Imagery acquisition date is unknown and may predate construction." }, "reference_method": "Census interpolated street address", "published_address": "5419 NE Starr Boulevard, Hillsboro, Oregon 97124", "county_fips": [ "41067" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "Original operator published computing street identity and calculated street reference only. The explicit Las Vegas street set remains approximate. Existing status, other facts and all historical source limitations stay unchanged. No current certification, technical figure, ownership, roof, floor or complete campus is certified.", "The inherited general area coordinate was not an independently reviewed computing street reference. The original operator published computing location documents and complete unique literal Census street evidence support this bounded reference inside the retained county. The measured correction is 198.0 metres. All original source wordings, dates, predecessor coordinates and versions remain retained. Existing status group unknown and every other fact stay unchanged. This is a reference correction without physical relocation, a new operation, selected roof, tenant floor, legal title or complete campus certification.", "Fields and scattered buildings lie north of a large commercial roof, parking and an adjacent area of graded ground and structural work. With acquisition date unknown, this does not establish a current construction milestone, roof location or complete campus." ], "sources": [ { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Original May28,2026operator paragraph explicitly identifies Hillsboro3at5419NEStarrBoulevard; extracted original text view" }, { "url": "https://www.flexential.com/system/files/file/2024-01/Flexential%20-%202023%20ISO%2027001%20Surveillance%20-%20Certificate_1831866-4.pdf", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Original issued certificate computing location table, historical street context only" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=5419+NE+Starr+Boulevard%2C+Hillsboro%2C+Oregon+97124&benchmark=Public_AR_Current&vintage=Current_Current&format=json", "host": "geocoding.geo.census.gov", "published": "", "date": "", "checked": "2026-10-24", "label": "Complete unique literal published street range, raw version retained" }, { "url": "https://imagery.nationalmap.gov/arcgis/rest/services/USGSNAIPPlus/ImageServer/exportImage?bbox=-122.94325659921128%2C45.555638288537544%2C-122.92914340078872%2C45.56551971146245&bboxSR=4326&imageSR=3857&size=600%2C600&format=png&f=image", "host": "imagery.nationalmap.gov", "published": "", "date": "", "checked": "2026-10-24", "label": "Actually viewed source setting, acquisition date unknown" } ], "checked": "2026-10-24", "whole_record_certified": false }, { "overlay": "Company role source check65, October24,2026", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 66 and 67. The Hillsboro 3 profile identifies this retained service context. Campus totals, future connections, enterprise zone benefits and WUE commitments are not adopted as measured quantities, completed works, awarded incentives or environmental outcomes. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted.", "fields": { "company_association": { "name": "Flexential", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Flexential identifies the named location in the original fleet guide, PDF pages 66 and 67. The Hillsboro 3 profile identifies this retained service context. Campus totals, future connections, enterprise zone benefits and WUE commitments are not adopted as measured quantities, completed works, awarded incentives or environmental outcomes. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." }, "provider_role": "operator" }, "notes": [ "Flexential identifies the named location in the original fleet guide, PDF pages 66 and 67. The Hillsboro 3 profile identifies this retained service context. Campus totals, future connections, enterprise zone benefits and WUE commitments are not adopted as measured quantities, completed works, awarded incentives or environmental outcomes. Only the previously empty provider brand is filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Operator per source describes the guide profile only, not a current operating verification. The publication day is unknown; file metadata is not a physical or publication date. No technical, environmental, tenant or ownership claim is adopted." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "whole_record_certified": false } ], "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": true, "precision_label": "Calculated street reference, not a roof or tenant floor", "summary": "Hillsboro · Washington · Source context reviewed" }, { "id": "flexential-portland-hillsboro-4-pdx04-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 4 (PDX04)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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 facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Footprint conflict: page 68 narrative 138,000 square feet; quick facts 158,000. No single footprint adopted. Planned campus total 54 MW is not an additional 54 MW at this building. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [ [ "2026-05-28", "Flexential published its Hillsboro 4 and Hillsboro 5 real estate announcement May 28, 2026. This dates the issuer publication and its reported acquisition context rather than an independently verified property closing day, computing commissioning, first service day or a new company role." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.flexential.com/data-centers/or/portland/hillsboro4-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.50581, "lng": -123.12719, "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-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 4 (PDX04)", "publisher_reported_footprint_sqft": null, "publisher_reported_critical_power_mw": 18, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false }, "notes": [ "Footprint conflict: page 68 narrative 138,000 square feet; quick facts 158,000. No single footprint adopted. Planned campus total 54 MW is not an additional 54 MW at this building.", "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check66, October24,2026", "scope": "The separate Hillsboro 4 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Design PUE, WUE and future expansion claims are not adopted as measured outcomes or completed works. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification.", "fields": { "company_association": { "name": "Flexential", "role": "operator", "identity_scope": "provider_brand_only", "scope": "The separate Hillsboro 4 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Design PUE, WUE and future expansion claims are not adopted as measured outcomes or completed works. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification." }, "provider_role": "operator" }, "notes": [ "The separate Hillsboro 4 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Design PUE, WUE and future expansion claims are not adopted as measured outcomes or completed works. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification." ], "sources": [ { "url": "https://www.flexential.com/data-centers/or/portland/hillsboro4-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "whole_record_certified": false }, { "overlay": "Codex 3 research followup 2", "scope": "The freshly read original dedicated Hillsboro 4 profile advertises colocation, interconnection, staffing and service levels, while the May 28, 2026 issuer account describes property acquisition and a fully leased facility. That lease and ownership context is not independently verified computing operation. The same current service profile template also markets Hillsboro 6, whose separate dated account describes a proposed future development. Marketing capability, active tour links and complete leasing therefore do not independently establish exact current commissioned computing or a first operating day. The new dated entry is the issuer announcement only.", "fields": { "current_stage_evidence": { "outcome": "current_hillsboro4_profile_and_acquisition_account_physical_stage_held", "scope": "The freshly read original dedicated Hillsboro 4 profile advertises colocation, interconnection, staffing and service levels, while the May 28, 2026 issuer account describes property acquisition and a fully leased facility. That lease and ownership context is not independently verified computing operation. The same current service profile template also markets Hillsboro 6, whose separate dated account describes a proposed future development. Marketing capability, active tour links and complete leasing therefore do not independently establish exact current commissioned computing or a first operating day. The new dated entry is the issuer announcement only." }, "source_read_scope": { "complete_relevant_named_current_operator_profile_sections_read": true, "original_peer_capture_and_actual_retrieval_receipt_reused": true, "no_new_network_request": true, "shared_hillsboro6_marketing_template_not_proof_of_commissioning": true, "service_advertising_lease_and_ownership_not_operation": true, "no_role_location_identity_or_quantity_promotion": true } }, "notes": [ "The freshly read original dedicated Hillsboro 4 profile advertises colocation, interconnection, staffing and service levels, while the May 28, 2026 issuer account describes property acquisition and a fully leased facility. That lease and ownership context is not independently verified computing operation. The same current service profile template also markets Hillsboro 6, whose separate dated account describes a proposed future development. Marketing capability, active tour links and complete leasing therefore do not independently establish exact current commissioned computing or a first operating day. The new dated entry is the issuer announcement only.", "Existing identities, roles, physical placement, jurisdiction assignments, technical quantities and exact first service days remain unchanged. A publication day does not date property closing or physical commissioning." ], "sources": [ { "url": "https://www.flexential.com/data-centers/or/portland/hillsboro4-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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", "event_evidence": [ { "date": "2026-05-28", "text": "Flexential published its Hillsboro 4 and Hillsboro 5 real estate announcement May 28, 2026. This dates the issuer publication and its reported acquisition context rather than an independently verified property closing day, computing commissioning, first service day or a new company role.", "kind": "announced", "sources": [ { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "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": "41067" } }, { "id": "flexential-portland-hillsboro-5-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 5", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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. separate Hillsboro5and6sections. 3935NEAloclekPlace is Hillsboro1acrossfrom newparcel, not verified Hillsboro6streetaddress.5and6are distinct developments; no copying63MWto each. Enterprise-zone marketing not individual incentive award. RegionalCBREmarketpercentages and corporate1Bfundraising excluded. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Redundancy conflicts: page 70 quick facts 4:3 and N+1 cooling; same page sidebar and page 71 say 5:4 UPS, page 71 N+2 cooling. Do not publish a settled redundancy claim. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "date": "", "events": [ [ "2026-05-28", "Flexential published its Hillsboro 4 and Hillsboro 5 real estate announcement May 28, 2026. This dates the issuer publication and its reported acquisition context rather than an independently verified property closing day, computing commissioning, first service day or a new company role." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.prnewswire.com/news-releases/flexential-acquires-prime-property-in-hillsboro-plans-new-data-center-as-next-phase-of-expansion-302546009.html", "host": "prnewswire.com", "date": "2025-09-04", "published": "2025-09-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-5-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.58263, "lng": -123.03746, "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": "issuer-release-review-round6-2026-10-14.json", "scope": "separate Hillsboro5and6sections", "fields": { "hillsboro6_planned_area_sqft": 350000, "hillsboro6_planned_capacity_mw": 27, "hillsboro6_floors": 2, "hillsboro5_area_sqft": 358000, "hillsboro5_planned_capacity_mw": 36, "hillsboro5_stage_at_release": "under construction", "hillsboro5_opening_target_year": 2026, "power_basis": "capacity, not explicitly IT versus gross" }, "notes": [ "3935NEAloclekPlace is Hillsboro1acrossfrom newparcel, not verified Hillsboro6streetaddress.5and6are distinct developments; no copying63MWto each. Enterprise-zone marketing not individual incentive award. RegionalCBREmarketpercentages and corporate1Bfundraising excluded.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.prnewswire.com/news-releases/flexential-acquires-prime-property-in-hillsboro-plans-new-data-center-as-next-phase-of-expansion-302546009.html", "host": "prnewswire.com", "date": "2025-09-04", "published": "2025-09-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "operator-primary-review-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 5", "publisher_reported_footprint_sqft": 358000, "publisher_reported_critical_power_mw": 36, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false }, "notes": [ "Redundancy conflicts: page 70 quick facts 4:3 and N+1 cooling; same page sidebar and page 71 say 5:4 UPS, page 71 N+2 cooling. Do not publish a settled redundancy claim.", "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check66, October24,2026", "scope": "The separate Hillsboro 5 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Leasing and capability wording do not create an exact opening or whole campus completion date. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification.", "fields": { "company_association": { "name": "Flexential", "role": "operator", "identity_scope": "provider_brand_only", "scope": "The separate Hillsboro 5 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Leasing and capability wording do not create an exact opening or whole campus completion date. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification." }, "provider_role": "operator" }, "notes": [ "The separate Hillsboro 5 service profile identifies Flexential for this retained record. The May 28, 2026 acquisition statement is attributed company context, without an independent title finding or an owner role. Leasing and capability wording do not create an exact opening or whole campus completion date. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Operator per source describes the named service profile rather than a current operating verification." ], "sources": [ { "url": "https://www.flexential.com/data-centers/portland-hillsboro-5-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "whole_record_certified": false }, { "overlay": "Codex 3 research followup 2", "scope": "The freshly read original Hillsboro 5 profile advertises a named computing facility and service capabilities. The May 28, 2026 issuer account describes acquisition and connected GPU and CPU ready environments, while the September 4, 2025 account reports construction and forecasts service in the following year. Those different document clocks remain separate. The later ownership and capability wording does not independently date completed computing commissioning, establish every live workload or convert the earlier forecast into an accomplished first opening. Current physical stage remains unresolved. The new dated entry is the May issuer announcement only.", "fields": { "current_stage_evidence": { "outcome": "current_hillsboro5_profile_and_two_dated_accounts_exact_commissioning_held", "scope": "The freshly read original Hillsboro 5 profile advertises a named computing facility and service capabilities. The May 28, 2026 issuer account describes acquisition and connected GPU and CPU ready environments, while the September 4, 2025 account reports construction and forecasts service in the following year. Those different document clocks remain separate. The later ownership and capability wording does not independently date completed computing commissioning, establish every live workload or convert the earlier forecast into an accomplished first opening. Current physical stage remains unresolved. The new dated entry is the May issuer announcement only." }, "source_read_scope": { "complete_relevant_named_current_operator_profile_sections_read": true, "original_peer_capture_and_actual_retrieval_receipt_reused": true, "no_new_network_request": true, "shared_hillsboro6_marketing_template_not_proof_of_commissioning": true, "service_advertising_lease_and_ownership_not_operation": true, "no_role_location_identity_or_quantity_promotion": true } }, "notes": [ "The freshly read original Hillsboro 5 profile advertises a named computing facility and service capabilities. The May 28, 2026 issuer account describes acquisition and connected GPU and CPU ready environments, while the September 4, 2025 account reports construction and forecasts service in the following year. Those different document clocks remain separate. The later ownership and capability wording does not independently date completed computing commissioning, establish every live workload or convert the earlier forecast into an accomplished first opening. Current physical stage remains unresolved. The new dated entry is the May issuer announcement only.", "Existing identities, roles, physical placement, jurisdiction assignments, technical quantities and exact first service days remain unchanged. A publication day does not date property closing or physical commissioning." ], "sources": [ { "url": "https://www.flexential.com/data-centers/portland-hillsboro-5-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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", "event_evidence": [ { "date": "2026-05-28", "text": "Flexential published its Hillsboro 4 and Hillsboro 5 real estate announcement May 28, 2026. This dates the issuer publication and its reported acquisition context rather than an independently verified property closing day, computing commissioning, first service day or a new company role.", "kind": "announced", "sources": [ { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "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": "41067" } }, { "id": "flexential-portland-hillsboro-6-or", "state": "or", "kind": "facility", "name": "Flexential Portland - Hillsboro 6", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "Flexential", "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. separate Hillsboro5and6sections. 3935NEAloclekPlace is Hillsboro1acrossfrom newparcel, not verified Hillsboro6streetaddress.5and6are distinct developments; no copying63MWto each. Enterprise-zone marketing not individual incentive award. RegionalCBREmarketpercentages and corporate1Bfundraising excluded. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.. Marketing section alone does not establish a current operating date. WUE 0 and PUE 1.4 are design/target claims, not measured annual consumption. Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.prnewswire.com/news-releases/flexential-acquires-prime-property-in-hillsboro-plans-new-data-center-as-next-phase-of-expansion-302546009.html", "host": "prnewswire.com", "date": "2025-09-04", "published": "2025-09-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" }, { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.58667, "lng": -123.16316, "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": "issuer-release-review-round6-2026-10-14.json", "scope": "separate Hillsboro5and6sections", "fields": { "hillsboro6_planned_area_sqft": 350000, "hillsboro6_planned_capacity_mw": 27, "hillsboro6_floors": 2, "hillsboro5_area_sqft": 358000, "hillsboro5_planned_capacity_mw": 36, "hillsboro5_stage_at_release": "under construction", "hillsboro5_opening_target_year": 2026, "power_basis": "capacity, not explicitly IT versus gross" }, "notes": [ "3935NEAloclekPlace is Hillsboro1acrossfrom newparcel, not verified Hillsboro6streetaddress.5and6are distinct developments; no copying63MWto each. Enterprise-zone marketing not individual incentive award. RegionalCBREmarketpercentages and corporate1Bfundraising excluded.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.prnewswire.com/news-releases/flexential-acquires-prime-property-in-hillsboro-plans-new-data-center-as-next-phase-of-expansion-302546009.html", "host": "prnewswire.com", "date": "2025-09-04", "published": "2025-09-04", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "operator-primary-review-round14-2026-10-14.json", "scope": "Named facility section; grouped base IDs remain grouped. Undated operator guide captured 2026-10-14.", "fields": { "operator_named_facility": "Flexential Portland - Hillsboro 6", "publisher_reported_footprint_sqft": 350000, "publisher_reported_critical_power_mw": 27, "power_basis": "operator critical load UPS capacity; Douglasville sections call it critical power", "current_measured_demand_mw": null, "commissioning_date": null, "exact_address_verified_by_this_document": false, "status_verified_by_this_document": null }, "notes": [ "Marketing section alone does not establish a current operating date. WUE 0 and PUE 1.4 are design/target claims, not measured annual consumption.", "Attribute ratings to the operator document. Do not treat as current energized IT load, available capacity, permits, independently verified compliance or observed uptime.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.flexential.com/system/files/file/2025-11/flexential-fleet-tour-guide-hvc.pdf?t=1775636396", "host": "flexential.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check66, October24,2026", "scope": "The September 4, 2025 announcement identifies Flexential development of Hillsboro 6. The later profile is marketing capability copy rather than a dated commissioning report. Its 3925 Aloclek Place is a location lead only; 3935 belongs to Hillsboro 1 across from the announced future site. Neither address becomes a new point, parcel or current operation finding. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Developer per source describes the dated development association rather than a completed or operating campus.", "fields": { "company_association": { "name": "Flexential", "role": "developer", "identity_scope": "provider_brand_only", "scope": "The September 4, 2025 announcement identifies Flexential development of Hillsboro 6. The later profile is marketing capability copy rather than a dated commissioning report. Its 3925 Aloclek Place is a location lead only; 3935 belongs to Hillsboro 1 across from the announced future site. Neither address becomes a new point, parcel or current operation finding. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Developer per source describes the dated development association rather than a completed or operating campus." }, "provider_role": "developer" }, "notes": [ "The September 4, 2025 announcement identifies Flexential development of Hillsboro 6. The later profile is marketing capability copy rather than a dated commissioning report. Its 3925 Aloclek Place is a location lead only; 3935 belongs to Hillsboro 1 across from the announced future site. Neither address becomes a new point, parcel or current operation finding. Only the previously empty provider brand and source role evidence are filled. Existing status, location, address, county, quantities, dates and component identity remain exact. This does not newly admit a location, parcel or roof. Publication and checked dates remain separate from physical milestones. Developer per source describes the dated development association rather than a completed or operating campus." ], "sources": [ { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "whole_record_certified": false }, { "overlay": "Codex 3 research followup 2", "scope": "The complete original September 4, 2025 issuer account describes a proposed Hillsboro 6 development on a newly acquired site and future capacity. Its current dedicated profile uses built to support capability wording and the same broad service template as other facilities, without an independently dated construction completion, commissioning or actual computing service statement. The May 2026 account refers back to announced plans rather than reporting a completed physical phase. The neighboring Hillsboro 1 facility, planned Hillsboro 6, design values and utility program statements are not merged. No current operating status or exact opening is inferred.", "fields": { "current_stage_evidence": { "outcome": "named_hillsboro6_plans_and_current_capability_template_stage_held", "scope": "The complete original September 4, 2025 issuer account describes a proposed Hillsboro 6 development on a newly acquired site and future capacity. Its current dedicated profile uses built to support capability wording and the same broad service template as other facilities, without an independently dated construction completion, commissioning or actual computing service statement. The May 2026 account refers back to announced plans rather than reporting a completed physical phase. The neighboring Hillsboro 1 facility, planned Hillsboro 6, design values and utility program statements are not merged. No current operating status or exact opening is inferred." }, "source_read_scope": { "complete_relevant_named_current_operator_profile_sections_read": true, "original_peer_capture_and_actual_retrieval_receipt_reused": true, "no_new_network_request": true, "shared_hillsboro6_marketing_template_not_proof_of_commissioning": true, "service_advertising_lease_and_ownership_not_operation": true, "no_role_location_identity_or_quantity_promotion": true } }, "notes": [ "The complete original September 4, 2025 issuer account describes a proposed Hillsboro 6 development on a newly acquired site and future capacity. Its current dedicated profile uses built to support capability wording and the same broad service template as other facilities, without an independently dated construction completion, commissioning or actual computing service statement. The May 2026 account refers back to announced plans rather than reporting a completed physical phase. The neighboring Hillsboro 1 facility, planned Hillsboro 6, design values and utility program statements are not merged. No current operating status or exact opening is inferred.", "Existing identities, roles, physical placement, jurisdiction assignments, technical quantities and exact first service days remain unchanged. A publication day does not date property closing or physical commissioning." ], "sources": [ { "url": "https://www.flexential.com/data-centers/portland-hillsboro-6-data-center", "host": "www.flexential.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-acquires-prime-property-hillsboro-plans-new-data-center", "host": "www.flexential.com", "published": "2025-09-04", "date": "2025-09-04", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.flexential.com/resources/press-release/flexential-secures-strategic-real-estate-ownership-hillsboro-oregon", "host": "www.flexential.com", "published": "2026-05-28", "date": "2026-05-28", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "fort-rock-data-center-bend-or", "state": "or", "kind": "facility", "name": "Fort Rock Data Center", "group": "operating", "status": "Operator listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Deschutes" ], "city": "Bend", "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. Fort Rock Bend explicit street identity. No numericITMW,areaororiginalopening. SOC2Type1operatorclaimnotindependentreportinspection. Low-risk/sustainabilitywordingnotzero-riskguaranteeormeasuredenergy. 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.fortrockdc.com/about/", "host": "fortrockdc.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 43.94085, "lng": -121.25594, "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-round10-2026-10-14.json", "scope": "Fort Rock Bend explicit street identity", "fields": { "operator": "Fort Rock Data Center", "address": "207 SouthwestColumbiaStreet, Bend, Oregon97702", "operator_described_use": "purpose-built carrier-neutral colocation facility" }, "notes": [ "No numericITMW,areaororiginalopening. SOC2Type1operatorclaimnotindependentreportinspection. Low-risk/sustainabilitywordingnotzero-riskguaranteeormeasuredenergy.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.fortrockdc.com/about/", "host": "fortrockdc.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 69", "scope": "The complete original current provider body names Bend and describes present cabinet configurations, carrier neutral service, business continuity support and remote hands. This supports operator listed colocation service. Resilience, compliance and low risk marketing claims remain attributed descriptions rather than independently certified performance, measured environmental effects, complete computing capacity or a first opening date.", "fields": { "current_stage_evidence": { "outcome": "provider_named_bend_colocation_service", "scope": "The complete original current provider body names Bend and describes present cabinet configurations, carrier neutral service, business continuity support and remote hands. This supports operator listed colocation service. Resilience, compliance and low risk marketing claims remain attributed descriptions rather than independently certified performance, measured environmental effects, complete computing capacity or a first opening date." }, "source_read_scope": { "complete_original_current_about_and_service_body_read": true, "footer_year_not_publication_day": true, "no_support_ticket_quote_request_or_contact": true, "no_capacity_certification_or_opening_export": true } }, "notes": [ "The complete original current provider body names Bend and describes present cabinet configurations, carrier neutral service, business continuity support and remote hands. This supports operator listed colocation service. Resilience, compliance and low risk marketing claims remain attributed descriptions rather than independently certified performance, measured environmental effects, complete computing capacity or a first opening date.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.fortrockdc.com/about/", "host": "www.fortrockdc.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "Bend · Deschutes · Source context reviewed", "status_scope": "The complete original current provider body names Bend and describes present cabinet configurations, carrier neutral service, business continuity support and remote hands. This supports operator listed colocation service. Resilience, compliance and low risk marketing claims remain attributed descriptions rather than independently certified performance, measured environmental effects, complete computing capacity or a first opening date.", "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": "41017" } }, { "id": "google-the-dalles-port-river-road-or", "state": "or", "kind": "facility", "name": "Google The Dalles Data Center - 3500 River Road (Port of The Dalles)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Wasco" ], "city": "The Dalles", "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. Original named-site/context, some road-and-footprint crosswalks limited; not independently certified operator/parcel.. TomPeterson ColumbiaCommunityConnection originalSeptember20,2022, perpublicmetadata; January3,2025modifiedtimestampnotevent. WhitingTurner filedGoogle/DesignLLC3500RiverRd290000sfAPPLICATION; 45dayprocess/months-to-groundbreakingnotactualapproval/construction.600Mpossiblecostnotpaid. Two-project125Mrevenue/147Mabatement20year estimates differ fromonefacility.3Mpersite initialpaymentconditionalonconstruction-in-processsubmission, notverifiedcash; twoifbuilt6Mnotone6M.50%/60%capturesdifferentscopesnotuniversalflatalltaxrebate.28.5MwaterinfrastructurecommitmentnotDCconsumption/currenttariff. Acquisition/proposeduse/phasepower/regulatorreview/explicitstagepreserved, not allfields/IT/currentoperationcertified.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://columbiacommunityconnection.com/the-dalles/google-making-moves-to-break-ground-on-first-new-data-center-in-the-dalles", "host": "columbiacommunityconnection.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.datacenters.google/locations/oregon/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.18975, "lng": -121.2, "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-acquisitions-regulatory-stage-and-site-crosswalks-round81-2026-10-15.json", "scope": "Original named-site/context, some road-and-footprint crosswalks limited; not independently certified operator/parcel.", "fields": {}, "notes": [ "TomPeterson ColumbiaCommunityConnection originalSeptember20,2022, perpublicmetadata; January3,2025modifiedtimestampnotevent. WhitingTurner filedGoogle/DesignLLC3500RiverRd290000sfAPPLICATION; 45dayprocess/months-to-groundbreakingnotactualapproval/construction.600Mpossiblecostnotpaid.", "Two-project125Mrevenue/147Mabatement20year estimates differ fromonefacility.3Mpersite initialpaymentconditionalonconstruction-in-processsubmission, notverifiedcash; twoifbuilt6Mnotone6M.50%/60%capturesdifferentscopesnotuniversalflatalltaxrebate.28.5MwaterinfrastructurecommitmentnotDCconsumption/currenttariff.", "Acquisition/proposeduse/phasepower/regulatorreview/explicitstagepreserved, not allfields/IT/currentoperationcertified." ], "sources": [ { "url": "https://columbiacommunityconnection.com/the-dalles/google-making-moves-to-break-ground-on-first-new-data-center-in-the-dalles", "host": "columbiacommunityconnection.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original current Google Oregon body describes existing computing in The Dalles and historical regional milestones. It does not independently crosswalk that existing service to the inherited new Port River Road project. Regional operation since 2006 and a separate fourth building history do not establish the new project commissioned or complete. No year only milestone becomes an exact first opening, and the existing campus is not merged with new construction.", "fields": { "current_stage_evidence": { "outcome": "existing_google_dalles_service_new_port_river_component_held", "scope": "The complete original current Google Oregon body describes existing computing in The Dalles and historical regional milestones. It does not independently crosswalk that existing service to the inherited new Port River Road project. Regional operation since 2006 and a separate fourth building history do not establish the new project commissioned or complete. No year only milestone becomes an exact first opening, and the existing campus is not merged with new construction." }, "source_read_scope": { "complete_original_current_oregon_location_body_read": true, "regional_operation_not_new_river_road_service": true, "year_only_milestones_not_exact_days": true, "no_location_or_capacity_changes": true } }, "notes": [ "The complete original current Google Oregon body describes existing computing in The Dalles and historical regional milestones. It does not independently crosswalk that existing service to the inherited new Port River Road project. Regional operation since 2006 and a separate fourth building history do not establish the new project commissioned or complete. No year only milestone becomes an exact first opening, and the existing campus is not merged with new construction.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.datacenters.google/locations/oregon/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "The Dalles · Wasco · 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": "41065" } }, { "id": "google-the-dalles-or", "state": "or", "kind": "facility", "name": "Google The Dalles Data Center Campus", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Wasco" ], "city": "The Dalles", "address": "", "who": "Google", "end_user": "", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "Calendar-year 2025 operator-reported location totals. Withdrawal, discharge and consumption are separate quantities; methodology permits estimates and does not establish today’s use.", "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. 7Bstatetotalnotbuilding-onlycapex.2015fourthconstructionnotfourthopening. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building. Google 2026 quarterly performance table; named regional campus scope. Operator-reported period metrics, not an October operating inspection, current MW load or building-specific measurement. Regional values are not assigned to a separate expansion or street-address record. Blank TTM remains unknown. No status, location precision or whole-campus completion upgrade; publication date unknown.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://datacenters.google/locations/oregon/", "host": "datacenters.google", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://datacenters.google/efficiency/", "host": "datacenters.google", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.datacenters.google/locations/oregon/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google official location source" }, { "url": "https://www.datacenters.google/locations/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google official location source" }, { "url": "https://sustainability.google/files/google-2026-environmental-report.pdf", "host": "sustainability.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google 2026 Environmental Report" } ], "loc": { "lat": 45.15992, "lng": -121.16744, "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": "captured-operator-review-round6-2026-10-14.json", "scope": "named operator source", "fields": { "first_data_center_opening_year": 2006, "fourth_data_center_construction_start_year": 2015, "regional_investment_usd_min_exclusive": 7000000000, "investment_scope": "Oregon statewide" }, "notes": [ "7Bstatetotalnotbuilding-onlycapex.2015fourthconstructionnotfourthopening.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://datacenters.google/locations/oregon/", "host": "datacenters.google", "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": "Google 2026 quarterly performance table; named regional campus scope", "fields": { "operator_reported_pue_period": "2026-Q2", "operator_reported_campus_pue": [ { "source_campus_label": "The Dalles, Oregon", "quarterly_pue": 1.1, "trailing_twelve_month_pue": 1.1 }, { "source_campus_label": "The Dalles, Oregon (2nd facility)", "quarterly_pue": 1.07, "trailing_twelve_month_pue": 1.06 }, { "source_campus_label": "The Dalles, Oregon (3rd facility)", "quarterly_pue": 1.08, "trailing_twelve_month_pue": 1.08 } ] }, "notes": [ "Operator-reported period metrics, not an October operating inspection, current MW load or building-specific measurement. Regional values are not assigned to a separate expansion or street-address record. Blank TTM remains unknown. No status, location precision or whole-campus completion upgrade; publication date unknown." ], "sources": [ { "url": "https://datacenters.google/efficiency/", "host": "datacenters.google", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "checked": "2026-10-15", "capture_sha256": "398f42d55ca9e2ebecd3b24e2dede307ad2d9d3b653469d1efebd135488f9c17", "events": [], "whole_record_certified": false }, { "overlay": "S4-Google-Locations-20261016", "scope": "Named Google location research context; regional campus and individual building identity remain separate.", "fields": { "operator_location_scope": "The Dalles, Oregon is named in Google’s current directory and linked location page. Regional entries can include several facilities; directory development flags alone do not establish an operating stage.", "record_association_scope": "The named operator location is associated with this existing research context by provider and named city/county. This is an explicit research association, not proof of a distinct physical site or an exact parcel.", "annual_water_reporting": { "source_location": "The Dalles, OR", "report_year": 2026, "reporting_year": 2025, "source_page": 97, "unit": "Million gallons", "withdrawal": 654.3, "discharge": 185.3, "consumption": 469.0 }, "water_method_scope": "Annual calendar-year 2025 figures for the reported location, not instantaneous use, a daily rate, an approved limit or one building. Google uses metered or invoiced values when available and can estimate missing data; the table does not identify each row’s metering completeness. Consumption is calculated as withdrawal minus discharge; values are rounded. Seawater and brackish water over 1,000 mg/L total dissolved solids are excluded. Unless otherwise specified, withdrawals are potable; Douglas County includes reclaimed wastewater. No litres or daily averages are calculated.", "water_location_association": "The Dalles, OR is associated with this regional campus research context only; no allocation to separate expansion/street-address records or individual buildings.", "current_status_basis": "An operating component is supported at Google’s named The Dalles, Oregon location by its current operator listing and 2025 operational reporting. This is regional campus scope, not verification that every expansion/building is complete, fully commissioned or operating at a stated MW. Annual reporting is historical, not an October operating inspection." }, "notes": [ "A partial operator/field review does not certify every fact or a whole state. No precise address, map point, current IT load or per-campus investment is inferred." ], "sources": [ { "url": "https://www.datacenters.google/locations/oregon/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google official location source" }, { "url": "https://www.datacenters.google/locations/", "host": "www.datacenters.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google official location source" }, { "url": "https://sustainability.google/files/google-2026-environmental-report.pdf", "host": "sustainability.google", "published": "", "date": "", "checked": "2026-10-16", "label": "Google 2026 Environmental Report" } ], "checked": "2026-10-16", "whole_record_certified": false }, { "overlay": "Company role source check 35, October 23, 2026", "scope": "Google identifies its own The Dalles, Oregon data center community in the body of its regional location page, separately from the global location menu. The operator per source relationship records its named provider brand, not independent proof that every building or expansion is operating. The named campus is retained at its existing record scope without assigning individual buildings, lots or street destinations. Regional investment and economic impact figures, targets and community programs are not site quantities. Legal title, sole control and a distinct legal entity are not established. Existing status, location, address, county, quantities, dates and component identity remain exact. The source publication date is unknown.", "fields": { "company_association": { "name": "Google", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Google identifies its own The Dalles, Oregon data center community in the body of its regional location page, separately from the global location menu. The operator per source relationship records its named provider brand, not independent proof that every building or expansion is operating. The named campus is retained at its existing record scope without assigning individual buildings, lots or street destinations. Regional investment and economic impact figures, targets and community programs are not site quantities. Legal title, sole control and a distinct legal entity are not established. Existing status, location, address, county, quantities, dates and component identity remain exact. The source publication date is unknown." }, "provider_role": "operator" }, "notes": [ "Google identifies its own The Dalles, Oregon data center community in the body of its regional location page, separately from the global location menu. The operator per source relationship records its named provider brand, not independent proof that every building or expansion is operating. The named campus is retained at its existing record scope without assigning individual buildings, lots or street destinations. Regional investment and economic impact figures, targets and community programs are not site quantities. Legal title, sole control and a distinct legal entity are not established. Existing status, location, address, county, quantities, dates and component identity remain exact. The source publication date is unknown." ], "sources": [ { "url": "https://www.datacenters.google/locations/oregon/", "host": "www.datacenters.google", "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": "The Dalles · Wasco · Source context reviewed", "status_scope": "An operating component is supported at Google’s named The Dalles, Oregon location by its current operator listing and 2025 operational reporting. This is regional campus scope, not verification that every expansion/building is complete, fully commissioned or operating at a stated MW. Annual reporting is historical, not an October operating inspection.", "typed_water_facts": [ { "measure": "withdrawal", "value": 654.3, "unit": "million gallons", "as_of": null, "as_of_basis": "reporting_period", "reporting_period": { "label": "2025", "start": "2025-01-01", "end": "2025-12-31" }, "observed_on": "2026-10-16", "basis": "operator_reported_total", "scope": "Google 2026 Environmental Report p.97: The Dalles, OR, calendar year 2025 withdrawal; million gallons as reported. This is a rounded annual operator-reported total, not current/daily usage, a permit limit or a building-only allocation. Method pp.82/87 allows metered/invoiced data and estimates where actual data is unavailable; no row-specific metering guarantee. Consumption is withdrawal minus discharge. Seawater/brackish sources excluded.", "sources": [ "https://sustainability.google/files/google-2026-environmental-report.pdf" ] }, { "measure": "discharge", "value": 185.3, "unit": "million gallons", "as_of": null, "as_of_basis": "reporting_period", "reporting_period": { "label": "2025", "start": "2025-01-01", "end": "2025-12-31" }, "observed_on": "2026-10-16", "basis": "operator_reported_total", "scope": "Google 2026 Environmental Report p.97: The Dalles, OR, calendar year 2025 discharge; million gallons as reported. This is a rounded annual operator-reported total, not current/daily usage, a permit limit or a building-only allocation. Method pp.82/87 allows metered/invoiced data and estimates where actual data is unavailable; no row-specific metering guarantee. Consumption is withdrawal minus discharge. Seawater/brackish sources excluded.", "sources": [ "https://sustainability.google/files/google-2026-environmental-report.pdf" ] }, { "measure": "consumption", "value": 469.0, "unit": "million gallons", "as_of": null, "as_of_basis": "reporting_period", "reporting_period": { "label": "2025", "start": "2025-01-01", "end": "2025-12-31" }, "observed_on": "2026-10-16", "basis": "operator_reported_total", "scope": "Google 2026 Environmental Report p.97: The Dalles, OR, calendar year 2025 consumption; million gallons as reported. This is a rounded annual operator-reported total, not current/daily usage, a permit limit or a building-only allocation. Method pp.82/87 allows metered/invoiced data and estimates where actual data is unavailable; no row-specific metering guarantee. Consumption is withdrawal minus discharge. Seawater/brackish sources excluded.", "sources": [ "https://sustainability.google/files/google-2026-environmental-report.pdf" ] } ], "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": "41065" } }, { "id": "h5-data-centers-portland-or", "state": "or", "kind": "facility", "name": "H5 Data Centers Portland", "group": "operating", "status": "Operator-listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Multnomah" ], "city": "Portland", "address": "", "who": "H5 Data Centers", "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. Backup generator capacity is not IT or utility-service capacity. Operator service/design assertions, not an independent uptime or certification audit. Repeated Ashburn42MW/Q32024 promotional footer is excluded from this location. 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://h5datacenters.com/portland-data-center.html", "host": "h5datacenters.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=1233+NW+12th+Avenue%2C+Portland%2C+OR+97209&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.531744792992, "lng": -122.683550324608, "precision": "address", "basis": "Published H5 Data Centers facility address 1233 NW 12th Avenue, Suite 201, Portland, OR 97209 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": "h5-primary-review-round4-2026-10-14.json", "scope": "Field or source context only", "fields": { "published_address": "1233 NW 12th Avenue, Suite201, Portland, OR 97209", "advertised_facility_sqft": 42000, "backup_generator_mw": 2 }, "notes": [ "Backup generator capacity is not IT or utility-service capacity.", "Operator service/design assertions, not an independent uptime or certification audit. Repeated Ashburn42MW/Q32024 promotional footer is excluded from this location.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://h5datacenters.com/portland-data-center.html", "host": "h5datacenters.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": "H5 offers current cabinet and cage licenses and interconnection services at its named Portland facility. Customer quotations are not republished. 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": "H5 offers current cabinet and cage licenses and interconnection services at its named Portland facility. Customer quotations are not republished. 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": [ "H5 offers current cabinet and cage licenses and interconnection services at its named Portland facility. Customer quotations are not republished." ], "sources": [ { "url": "https://h5datacenters.com/portland-data-center.html", "host": "h5datacenters.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 7, October 22, 2026", "scope": "Official facility service street reference only. No canonical address, current operation, physical date, capacity, company role, jurisdiction, parcel, complete campus or distinct building identity is adopted.", "fields": { "location_review_decision": { "location": { "lat": 45.531744792992, "lng": -122.683550324608, "precision": "address", "basis": "Published H5 Data Centers facility address 1233 NW 12th Avenue, Suite 201, Portland, OR 97209 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": "1233 NW 12th Avenue, Suite 201, Portland, OR 97209", "county_fips": [ "41051" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The named operator facility page publishes this service address in its facility location section. Navigation, related facilities, corporate addresses, embedded maps and operator template coordinates are excluded. The canonical address wrapper remains exact; the published address is retained as reviewed location evidence.", "The unique Census street match and retained county boundary agree with the existing county. Street interpolation does not identify a roof, suite, floor, campus boundary, legal parcel, ownership or distinct physical building. Status, dates, quantities and jurisdiction remain unchanged.", "The complete operator suite or floor qualifier remains in visible address evidence. The Census query omits only that qualifier and uses the published street and locality. No suite or floor point is inferred." ], "sources": [ { "url": "https://h5datacenters.com/portland-data-center.html", "host": "h5datacenters.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility street address section" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=1233+NW+12th+Avenue%2C+Portland%2C+OR+97209&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 12, October 23, 2026", "scope": "H5 Data Centers presents this named facility or campus in its own colocation service portfolio. Operator is the attributed provider brand relationship, not an independently established legal operating entity, property owner or confirmation that every building and phase is operating. No status, location, physical date, capacity, certification, outage guarantee, utility price or environmental outcome is promoted. The source includes a suite or floor offering. This does not establish operation or ownership of the whole host building.", "fields": { "company_association": { "name": "H5 Data Centers", "role": "operator", "identity_scope": "provider_brand_only", "scope": "H5 Data Centers presents this named facility or campus in its own colocation service portfolio. Operator is the attributed provider brand relationship, not an independently established legal operating entity, property owner or confirmation that every building and phase is operating. No status, location, physical date, capacity, certification, outage guarantee, utility price or environmental outcome is promoted. The source includes a suite or floor offering. This does not establish operation or ownership of the whole host building." }, "provider_role": "operator" }, "notes": [ "H5 Data Centers presents this named facility or campus in its own colocation service portfolio. Operator is the attributed provider brand relationship, not an independently established legal operating entity, property owner or confirmation that every building and phase is operating. No status, location, physical date, capacity, certification, outage guarantee, utility price or environmental outcome is promoted. The source includes a suite or floor offering. This does not establish operation or ownership of the whole host building.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://h5datacenters.com/portland-data-center.html", "host": "h5datacenters.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named colocation portfolio page, scoped provider relationship 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": "Portland · Multnomah · Source context reviewed", "status_scope": "H5 offers current cabinet and cage licenses and interconnection services at its named Portland facility. Customer quotations are not republished. 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": "meta-prineville-or", "state": "or", "kind": "facility", "name": "Meta Prineville Data Center Campus", "group": "operating", "status": "Operator-reported operation", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Crook" ], "city": "Prineville", "address": "", "who": "Meta", "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 operator info sheet. Investment label retains its city/state scope and does not independently establish expenditures at one building. Jobs/funding are operator figures with no separately established observation end-date. Renewables MW concern separate electricity-generation projects, not site IT demand. Water-positive/restoration statements are goals, not measured site water use. 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://datacenters.atmeta.com/asset/prineville-data-center-info-sheet/", "host": "datacenters.atmeta.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://datacenters.atmeta.com/us-locations/", "host": "datacenters.atmeta.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Original source for the qualified stage" } ], "loc": { "lat": 44.17148, "lng": -120.38835, "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-pdf-review-round5-2026-10-14.json", "scope": "Field or source context only", "fields": { "operator_labeled_data_center_investment_usd": 2000000000, "investment_is_lower_bound": true, "investment_geographic_label": "Oregon", "historic_groundbreaking_year": 2010, "peak_construction_workers": 1000, "operator_reported_operational_jobs_lower_bound": 350, "local_school_nonprofit_direct_funding_usd_lower_bound": 5700000, "direct_funding_county_scope": "Crook" }, "notes": [ "Undated operator info sheet. Investment label retains its city/state scope and does not independently establish expenditures at one building. Jobs/funding are operator figures with no separately established observation end-date. Renewables MW concern separate electricity-generation projects, not site IT demand. Water-positive/restoration statements are goals, not measured site water use.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://datacenters.atmeta.com/asset/prineville-data-center-info-sheet/", "host": "datacenters.atmeta.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "service-status-2026-10-19", "scope": "Meta describes the named Prineville center as part of its global infrastructure and reports supported operational jobs in its currently served factsheet.", "fields": { "current_stage_evidence": { "outcome": "operator_reported_operation", "scope": "Meta describes the named Prineville center as part of its global infrastructure and reports supported operational jobs in its currently served factsheet." } }, "notes": [ "The factsheet is undated and gives no full-campus commissioning date. Its financial, jobs and environmental statements are company claims. Independent certification and current usable capacity remain unverified." ], "sources": [ { "url": "https://datacenters.atmeta.com/asset/prineville-data-center-info-sheet/", "host": "datacenters.atmeta.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Original source for the qualified stage" }, { "url": "https://datacenters.atmeta.com/us-locations/", "host": "datacenters.atmeta.com", "published": "", "date": "", "checked": "2026-10-19", "label": "Original source for the qualified stage" } ], "checked": "2026-10-19", "whole_record_certified": false }, { "overlay": "Company role source check 07, October 23, 2026", "scope": "Meta presents its named data center as part of its own infrastructure and service network in this first party source. Operator is an attributed provider brand role, not an independently established legal entity, property owner or finding about completion of every building or phase. Company resource, rate payer, community and certification claims are not adopted as measured effects or independent findings. No physical date, technical figure, photograph, status or location is promoted.", "fields": { "company_association": { "name": "Meta", "role": "operator", "identity_scope": "provider_brand_only", "scope": "Meta presents its named data center as part of its own infrastructure and service network in this first party source. Operator is an attributed provider brand role, not an independently established legal entity, property owner or finding about completion of every building or phase. Company resource, rate payer, community and certification claims are not adopted as measured effects or independent findings. No physical date, technical figure, photograph, status or location is promoted." }, "provider_role": "operator" }, "notes": [ "Meta presents its named data center as part of its own infrastructure and service network in this first party source. Operator is an attributed provider brand role, not an independently established legal entity, property owner or finding about completion of every building or phase. Company resource, rate payer, community and certification claims are not adopted as measured effects or independent findings. No physical date, technical figure, photograph, status or location is promoted.", "Source dates remain separate from physical milestones and the retained status field." ], "sources": [ { "url": "https://datacenters.atmeta.com/asset/prineville-data-center-info-sheet/", "host": "datacenters.atmeta.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party named facility source, PDF first page visually reviewed where supplied" } ], "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": "Prineville · Crook · Source context reviewed", "status_scope": "Meta describes the named Prineville center as part of its global infrastructure and reports supported operational jobs in its currently served factsheet.", "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": "41013" } }, { "id": "ntt-hillsboro-hi1-data-center-or", "state": "or", "kind": "facility", "name": "NTT Hillsboro HI1 Data Center", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "NTT DATA", "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. Carrier-published label/address context only. Physical operating status, exclusive operator, ownership, IT load and code remain unverified by this source.. Address supports limited facility context; no HI1 code, exact current operator contract or critical IT specification in source. List gives no MW, actual occupancy, commissioning dates, title deeds, contracts or independent physical inspections. Listing is not a guarantee of presently deliverable service. Coming Soon labels on Vancouver1050Pender and Watertown486Arsenal have unspecified scope; not adopted as data-center construction or commissioning statuses. Vancouver is outside the United States cohort. Address rows can represent multiple service providers or tenants in one building. Never sum rows as distinct physical buildings or replace ownership/operator fields automatically. Source has ZIP/name spelling inconsistencies, including LumenSunnyvale98108, QTS SantaClara98054, Cambridge02451 and DigitalFortess. Raw values retained; no postal corrections or geocodes inferred. No issue date printed. Filename 20260206 and PDF modification metadata February6,2026 are file/version indicators, not proof of issue date, site commissioning or a field survey that day. PDF title still references November2025 spreadsheet.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.astound.com/business/wp-content/uploads/2026/02/Astound-Business-Data-Center-List-20260206.pdf", "host": "astound.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.nttdata.com/en-ph/services/global-data-centers/global-locations/americas/hillsboro-hi1-data-center", "host": "www.nttdata.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact building code and named service text, scoped provider relationship reviewed" } ], "loc": { "lat": 45.49386, "lng": -123.06793, "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-carrier-list-address-crosswalk-round92-2026-10-15.json", "scope": "Carrier-published label/address context only. Physical operating status, exclusive operator, ownership, IT load and code remain unverified by this source.", "fields": { "listed_label": "NTT Global", "listed_address": "4050 NE Evergreen Rd", "listed_city": "Hillsboro", "listed_state": "OR" }, "notes": [ "Address supports limited facility context; no HI1 code, exact current operator contract or critical IT specification in source.", "List gives no MW, actual occupancy, commissioning dates, title deeds, contracts or independent physical inspections. Listing is not a guarantee of presently deliverable service.", "Coming Soon labels on Vancouver1050Pender and Watertown486Arsenal have unspecified scope; not adopted as data-center construction or commissioning statuses. Vancouver is outside the United States cohort.", "Address rows can represent multiple service providers or tenants in one building. Never sum rows as distinct physical buildings or replace ownership/operator fields automatically.", "Source has ZIP/name spelling inconsistencies, including LumenSunnyvale98108, QTS SantaClara98054, Cambridge02451 and DigitalFortess. Raw values retained; no postal corrections or geocodes inferred.", "No issue date printed. Filename 20260206 and PDF modification metadata February6,2026 are file/version indicators, not proof of issue date, site commissioning or a field survey that day. PDF title still references November2025 spreadsheet." ], "sources": [ { "url": "https://www.astound.com/business/wp-content/uploads/2026/02/Astound-Business-Data-Center-List-20260206.pdf", "host": "astound.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check 18, October 23, 2026", "scope": "NTT DATA explicitly offers service for this exact named building on its own global data center website. Operator is the attributed provider brand relationship of the NTT DATA global data center business, not independent verification of a legal operating entity, property ownership, whole campus completion or every phase. No current status, precise location, address, physical date, capacity, water, safety, certification, compliance or incentive eligibility is promoted. HI1 is explicitly named in Hillsboro, Oregon, separately from four other planned or campus components. The marketed Cleaner Air Oregon certification does not establish a reviewed air permit, regulatory compliance, measured emissions or absence of concerns. The source is a localized English page on the official corporate domain; its locale is not the facility country or jurisdiction. The page explicitly identifies the retained United States city and code.", "fields": { "company_association": { "name": "NTT DATA", "role": "operator", "identity_scope": "provider_brand_only", "scope": "NTT DATA explicitly offers service for this exact named building on its own global data center website. Operator is the attributed provider brand relationship of the NTT DATA global data center business, not independent verification of a legal operating entity, property ownership, whole campus completion or every phase. No current status, precise location, address, physical date, capacity, water, safety, certification, compliance or incentive eligibility is promoted. HI1 is explicitly named in Hillsboro, Oregon, separately from four other planned or campus components. The marketed Cleaner Air Oregon certification does not establish a reviewed air permit, regulatory compliance, measured emissions or absence of concerns. The source is a localized English page on the official corporate domain; its locale is not the facility country or jurisdiction. The page explicitly identifies the retained United States city and code." }, "provider_role": "operator" }, "notes": [ "NTT DATA explicitly offers service for this exact named building on its own global data center website. Operator is the attributed provider brand relationship of the NTT DATA global data center business, not independent verification of a legal operating entity, property ownership, whole campus completion or every phase. No current status, precise location, address, physical date, capacity, water, safety, certification, compliance or incentive eligibility is promoted. HI1 is explicitly named in Hillsboro, Oregon, separately from four other planned or campus components. The marketed Cleaner Air Oregon certification does not establish a reviewed air permit, regulatory compliance, measured emissions or absence of concerns. The source is a localized English page on the official corporate domain; its locale is not the facility country or jurisdiction. The page explicitly identifies the retained United States city and code.", "First publication dates are not established. Awards, specifications, current retrieval and stated plans are not physical milestones." ], "sources": [ { "url": "https://www.nttdata.com/en-ph/services/global-data-centers/global-locations/americas/hillsboro-hi1-data-center", "host": "www.nttdata.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact building code and named service text, scoped provider relationship reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The selected original carrier roster Oregon page identifies several Hillsboro facilities but does not independently crosswalk the inherited NTT HI1 component to a current provider service claim. A roster omission does not establish closure. The separately held original NTT path is not bypassed through an alternate provider copy, and another Hillsboro company is not substituted.", "fields": { "current_stage_evidence": { "outcome": "original_carrier_oregon_list_exact_ntt_component_held", "scope": "The selected original carrier roster Oregon page identifies several Hillsboro facilities but does not independently crosswalk the inherited NTT HI1 component to a current provider service claim. A roster omission does not establish closure. The separately held original NTT path is not bypassed through an alternate provider copy, and another Hillsboro company is not substituted." }, "source_read_scope": { "original_carrier_roster_physical_page3_read": true, "roster_omission_not_closure": true, "no_company_or_component_merge": true } }, "notes": [ "The selected original carrier roster Oregon page identifies several Hillsboro facilities but does not independently crosswalk the inherited NTT HI1 component to a current provider service claim. A roster omission does not establish closure. The separately held original NTT path is not bypassed through an alternate provider copy, and another Hillsboro company is not substituted.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.astound.com/business/wp-content/uploads/2026/02/Astound-Business-Data-Center-List-20260206.pdf", "host": "www.astound.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "verrus-oakline-mill-creek-salem-or", "state": "or", "kind": "facility", "name": "Oakline at Mill Creek", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Marion" ], "city": "Salem", "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 government source. Directive to terminate is not independently read executed cancellation or finding all adjacent private development impossible. No statewide data-center ban or current operational closure. Exact Verrus/Oakline company match not independently established in this release. No MW or cost. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [ [ "2026-07-30", "The Oregon Governor original release dated July 30, 2026 directs termination of the State land sale contract for the proposed Mill Creek computing project. This dates the public direction rather than independently read completion of that termination, a general computing ban or physical closure." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://apps.oregon.gov/oregon-newsroom/OR/GOV/Posts/Post/governor-kotek-directs-state-to-withdraw-land-for-proposed-salem-data-center-site", "host": "apps.oregon.gov", "date": "2026-07-30", "published": "2026-07-30", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 44.92354, "lng": -122.60623, "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": "named government source", "fields": { "governor_directive_date": "2026-07-30", "directed_action": "terminate state land-sale contract for proposed data-center site", "state_land_area_acres_approx": 32, "published_location": "MillCreekCorporateCenter,southeastSalem,Oregon" }, "notes": [ "Directive to terminate is not independently read executed cancellation or finding all adjacent private development impossible. No statewide data-center ban or current operational closure. Exact Verrus/Oakline company match not independently established in this release. No MW or cost.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://apps.oregon.gov/oregon-newsroom/OR/GOV/Posts/Post/governor-kotek-directs-state-to-withdraw-land-for-proposed-salem-data-center-site", "host": "apps.oregon.gov", "date": "2026-07-30", "published": "2026-07-30", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original Governor release dated July 30, 2026 directs the Department of Administrative Services to terminate the State land sale contract for a proposed Mill Creek computing project in southeast Salem. This is an official land disposition direction, not independently read execution of the contract termination, a statewide computing ban or physical facility closure. The statement does not independently establish each inherited developer role, current building stage or any replacement development. No identity, land location or corporate role is changed.", "fields": { "current_stage_evidence": { "outcome": "original_state_land_disposition_direction_exact_physical_stage_held", "scope": "The complete original Governor release dated July 30, 2026 directs the Department of Administrative Services to terminate the State land sale contract for a proposed Mill Creek computing project in southeast Salem. This is an official land disposition direction, not independently read execution of the contract termination, a statewide computing ban or physical facility closure. The statement does not independently establish each inherited developer role, current building stage or any replacement development. No identity, land location or corporate role is changed." }, "source_read_scope": { "complete_original_governor_release_body_read": true, "direction_not_executed_contract_termination": true, "state_land_decision_not_statewide_ban": true, "exact_developer_roles_unverified_and_unchanged": true } }, "notes": [ "The complete original Governor release dated July 30, 2026 directs the Department of Administrative Services to terminate the State land sale contract for a proposed Mill Creek computing project in southeast Salem. This is an official land disposition direction, not independently read execution of the contract termination, a statewide computing ban or physical facility closure. The statement does not independently establish each inherited developer role, current building stage or any replacement development. No identity, land location or corporate role is changed.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://apps.oregon.gov/oregon-newsroom/OR/GOV/Posts/Post/governor-kotek-directs-state-to-withdraw-land-for-proposed-salem-data-center-site", "host": "apps.oregon.gov", "published": "2026-07-30", "date": "2026-07-30", "checked": "2026-10-24", "label": "Reviewed government record" } ], "checked": "2026-10-24", "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 · Marion · Source context reviewed", "event_evidence": [ { "date": "2026-07-30", "text": "The Oregon Governor original release dated July 30, 2026 directs termination of the State land sale contract for the proposed Mill Creek computing project. This dates the public direction rather than independently read completion of that termination, a general computing ban or physical closure.", "kind": "announced", "sources": [ { "url": "https://apps.oregon.gov/oregon-newsroom/OR/GOV/Posts/Post/governor-kotek-directs-state-to-withdraw-land-for-proposed-salem-data-center-site", "host": "apps.oregon.gov", "published": "2026-07-30", "date": "2026-07-30", "checked": "2026-10-24", "label": "Reviewed government record" } ] } ], "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": "41047" } }, { "id": "percheron-data-center-or", "state": "or", "kind": "facility", "name": "Percheron Data Center", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Morrow" ], "city": "Boardman area (Tower Road)", "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. Rowan Percheron land and phased development chronology. Developerchronologynotindependentsignedrezoning/recordeddeedinspection.300MWplannednotoperatingIT. Boardmanofficialquotenotexactprojectparcelorendorsementbyallresidents. No exactfirstRFSday. 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://rowan.digital/portfolio/percheron/", "host": "rowan.digital", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.35825, "lng": -119.57918, "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-round10-2026-10-14.json", "scope": "Rowan Percheron land and phased development chronology", "fields": { "developer": "Rowan Digital Infrastructure", "project": "Percheron", "region": "Oregon Columbia River Gorge", "site_acres": 275, "planned_campus_capacity_mw": 300, "power_basis": "campus capacity, not explicit critical IT", "developer_reported_due_diligence_start": "late2022", "developer_reported_rezoning_approval_year": 2023, "developer_reported_land_closing_year": 2024, "phased_buildout_completion_target_year": 2030 }, "notes": [ "Developerchronologynotindependentsignedrezoning/recordeddeedinspection.300MWplannednotoperatingIT. Boardmanofficialquotenotexactprojectparcelorendorsementbyallresidents. No exactfirstRFSday.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://rowan.digital/portfolio/percheron/", "host": "rowan.digital", "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": "Boardman area (Tower Road) · Morrow · 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": "41049" } }, { "id": "pittock-block-portland-or", "state": "or", "kind": "facility", "name": "Pittock Block (PTOR1)", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Multnomah" ], "city": "Portland", "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. 1547 Pittock carrier hotel area and power scope. Publishedspaceisbuilding/operatorofferingnotexplicitwhitespace.8MWpowernotIT;7MWbackupnotadded.94providersheadlineversus170plus/179servicesand16fiberoperatorsarescopecategoriesnotcurrentcarrier-censusproof. MatawanNJheadquartersnotPittockaddress. No exactopeningdateorcurrentload. 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://1547realty.com/data-centers/portland/", "host": "1547realty.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.54683, "lng": -122.41619, "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-round10-2026-10-14.json", "scope": "1547 Pittock carrier hotel area and power scope", "fields": { "operator_owner_publication": "1547 Critical Systems Realty", "code": "PTOR1", "facility": "Pittock Block", "locality": "Portland, Oregon", "published_space_sqft": 302262, "published_power_capacity_mw": 8, "backup_generation_mw": 7, "onsite_generators": 5 }, "notes": [ "Publishedspaceisbuilding/operatorofferingnotexplicitwhitespace.8MWpowernotIT;7MWbackupnotadded.94providersheadlineversus170plus/179servicesand16fiberoperatorsarescopecategoriesnotcurrentcarrier-censusproof. MatawanNJheadquartersnotPittockaddress. No exactopeningdateorcurrentload.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://1547realty.com/data-centers/portland/", "host": "1547realty.com", "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": "Portland · Multnomah · 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": "41051" } }, { "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": "roundhouse-cascade-locks-or", "state": "or", "kind": "facility", "name": "Roundhouse Cascade Locks Data Center", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Hood River" ], "city": "Cascade Locks", "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. Historical cancellation. Does not describe separate Abundant Mines tenant, nor establish the prior announced power or investment. Port office address is not a facility parcel. Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building.", "date": "", "events": [ [ "2023-07-20", "The Port of Cascade Locks and Roundhouse joint original announcement is dated July 20, 2023 and announces discontinuation of their proposed computing project. This dates the public statement without assigning an unknown earlier underlying decision day, physical facility closure or a citywide computing ban." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://www.portofcascadelocks.gov/july-20-2023-cascade-locks-port-and-roundhouse-inc-jointly-announce-decision-to-discontinue-datacenter-project", "host": "portofcascadelocks.gov", "date": "2023-07-20", "published": "2023-07-20", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "loc": { "lat": 45.53492, "lng": -121.66848, "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": "primary-events-round3-2026-10-14.json", "scope": "Field or source context only", "fields": { "status_event": "project_discontinued", "event_date": "2023-07-20", "actor": "Port of Cascade Locks and Roundhouse joint announcement" }, "notes": [ "Historical cancellation. Does not describe separate Abundant Mines tenant, nor establish the prior announced power or investment. Port office address is not a facility parcel.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.portofcascadelocks.gov/july-20-2023-cascade-locks-port-and-roundhouse-inc-jointly-announce-decision-to-discontinue-datacenter-project", "host": "portofcascadelocks.gov", "date": "2023-07-20", "published": "2023-07-20", "checked": "2026-10-14", "date_kind": "publication", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original Port and Roundhouse joint statement dated July 20, 2023 announces a decision to discontinue the proposed computing project and says the needed community support was not achieved. The statement describes no future computing partnership between those two organizations at that point. It does not establish physical closure of an operating facility, a municipal computing ban, current absence of all other projects or the exact earlier underlying decision day. Community feedback is attributed to the joint participants, without inventing a resident group, petition count or independently measured harm.", "fields": { "current_stage_evidence": { "outcome": "official_joint_project_discontinuation_account_not_physical_closure", "scope": "The complete original Port and Roundhouse joint statement dated July 20, 2023 announces a decision to discontinue the proposed computing project and says the needed community support was not achieved. The statement describes no future computing partnership between those two organizations at that point. It does not establish physical closure of an operating facility, a municipal computing ban, current absence of all other projects or the exact earlier underlying decision day. Community feedback is attributed to the joint participants, without inventing a resident group, petition count or independently measured harm." }, "source_read_scope": { "complete_original_joint_statement_body_read": true, "release_day_not_independently_verified_underlying_decision_day": true, "joint_participant_account_not_direct_resident_testimony": true, "no_private_resident_details_or_petition_count": true, "no_physical_closure_or_general_rule_inferred": true } }, "notes": [ "The complete original Port and Roundhouse joint statement dated July 20, 2023 announces a decision to discontinue the proposed computing project and says the needed community support was not achieved. The statement describes no future computing partnership between those two organizations at that point. It does not establish physical closure of an operating facility, a municipal computing ban, current absence of all other projects or the exact earlier underlying decision day. Community feedback is attributed to the joint participants, without inventing a resident group, petition count or independently measured harm.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.portofcascadelocks.gov/july-20-2023-cascade-locks-port-and-roundhouse-inc-jointly-announce-decision-to-discontinue-datacenter-project", "host": "www.portofcascadelocks.gov", "published": "2023-07-20", "date": "2023-07-20", "checked": "2026-10-24", "label": "Reviewed government record" } ], "checked": "2026-10-24", "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": "Cascade Locks · Hood River · Source context reviewed", "event_evidence": [ { "date": "2023-07-20", "text": "The Port of Cascade Locks and Roundhouse joint original announcement is dated July 20, 2023 and announces discontinuation of their proposed computing project. This dates the public statement without assigning an unknown earlier underlying decision day, physical facility closure or a citywide computing ban.", "kind": "announced", "sources": [ { "url": "https://www.portofcascadelocks.gov/july-20-2023-cascade-locks-port-and-roundhouse-inc-jointly-announce-decision-to-discontinue-datacenter-project", "host": "www.portofcascadelocks.gov", "published": "2023-07-20", "date": "2023-07-20", "checked": "2026-10-24", "label": "Reviewed government record" } ] } ], "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": "41027" } }, { "id": "sabey-umatilla-or", "state": "or", "kind": "facility", "name": "SDC Umatilla Campus", "group": "proposed", "status": "Operator-listed preleasing", "raw_status": "proposed", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Umatilla" ], "city": "Umatilla", "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. Projected schedule, not delivered phases; shell delivery does not mean operating data hall. Power is aggregate, not explicitlyIT. Page1.3estimated versus1.25projectedPUElabels remain forecasts. Enterprise-zone and state tax marketing requires current government evidence; no award value 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://sabeydatacenters.com/locations/sdc-umatilla", "host": "sabeydatacenters.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.66069, "lng": -118.68391, "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": "remaining-operators-review-round5-2026-10-14.json", "scope": "named operator source", "fields": { "planned_aggregate_power_mw_min_exclusive": 120, "projected_schedule": { "groundbreaking_year": 2024, "core_shell_delivery_year": 2026, "first_data_hall_online_year": 2027, "first_data_hall_mw": 9, "second_data_hall_online_year": 2028, "second_data_hall_mw": 9, "later_halls_and_building2_year_min": 2029 } }, "notes": [ "Projected schedule, not delivered phases; shell delivery does not mean operating data hall. Power is aggregate, not explicitlyIT. Page1.3estimated versus1.25projectedPUElabels remain forecasts. Enterprise-zone and state tax marketing requires current government evidence; no award value adopted.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://sabeydatacenters.com/locations/sdc-umatilla", "host": "sabeydatacenters.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": "Sabey explicitly invites preleasing and describes power as coming to its new Umatilla campus. Shared service-menu text does not establish commissioned operation or physical completion. 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_preleasing", "scope": "Sabey explicitly invites preleasing and describes power as coming to its new Umatilla campus. Shared service-menu text does not establish commissioned operation or physical completion. 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": [ "Sabey explicitly invites preleasing and describes power as coming to its new Umatilla campus. Shared service-menu text does not establish commissioned operation or physical completion." ], "sources": [ { "url": "https://sabeydatacenters.com/locations/sdc-umatilla", "host": "sabeydatacenters.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": "Umatilla · Umatilla · Source context reviewed", "status_scope": "Sabey explicitly invites preleasing and describes power as coming to its new Umatilla campus. Shared service-menu text does not establish commissioned operation or physical completion. 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": "41059" } }, { "id": "stack-hillsboro-or", "state": "or", "kind": "facility", "name": "STACK Hillsboro Campus", "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 project context: original issuer statement, local reporting or advocacy concerns, with source role and historical/proposed scope explicit.. Nick LaMora, HillsboroNewsTimes August8,2026 original city records/staff reporting: STACK filed July27at10:14 to REVISE existing2014three-phase approval, not a new permitted building or specified MW.120day July27moratorium reportedly allows this earlier filing to continue review, not approved changes. Aligned NE30th/glencoeswale preapplication about one hour later is NOT formal land-use filing and not exempt, separate unpinned concept. Wagon/Corny July21 applications nearly20/29ac respectively are not independently crosswalked to Hines/DigitalRealty rows.180day SIP-agreement pause separate from120day development pause/state enterprise-zone restrictions. August26/September15/October6rule milestones were future targets; no later adoption observed from this article. Signed enactments uninspected. Not all fields, current operation, permits, exact parcel or critical IT independently verified.", "date": "", "events": [], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://hillsboronewstimes.com/2026/08/08/data-center-proposals-filed-days-hours-before-hillsboro-moratorium-approved/", "host": "hillsboronewstimes.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.stackinfra.com/locations/americas/portland/por01/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.stackinfra.com/locations/americas/portland/por02/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.54225, "lng": -123.01744, "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-issuer-filings-local-plans-and-circular-source-holds-round85-2026-10-15.json", "scope": "Named project context: original issuer statement, local reporting or advocacy concerns, with source role and historical/proposed scope explicit.", "fields": {}, "notes": [ "Nick LaMora, HillsboroNewsTimes August8,2026 original city records/staff reporting: STACK filed July27at10:14 to REVISE existing2014three-phase approval, not a new permitted building or specified MW.120day July27moratorium reportedly allows this earlier filing to continue review, not approved changes. Aligned NE30th/glencoeswale preapplication about one hour later is NOT formal land-use filing and not exempt, separate unpinned concept. Wagon/Corny July21 applications nearly20/29ac respectively are not independently crosswalked to Hines/DigitalRealty rows.180day SIP-agreement pause separate from120day development pause/state enterprise-zone restrictions. August26/September15/October6rule milestones were future targets; no later adoption observed from this article. Signed enactments uninspected.", "Not all fields, current operation, permits, exact parcel or critical IT independently verified." ], "sources": [ { "url": "https://hillsboronewstimes.com/2026/08/08/data-center-proposals-filed-days-hours-before-hillsboro-moratorium-approved/", "host": "hillsboronewstimes.com", "date": "", "published": "", "checked": "2026-10-15", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original current provider roster describes distinct POR01 and POR02 campuses. This pass does not independently crosswalk the inherited generic new Hillsboro proposals to those exact existing components or a further campus. Private reporting about last minute applications before a municipal pause does not establish an original final project entitlement or a physical construction stage. The selected original City policy host was unavailable at robots, so its current ban scope and exact applicability were not independently read or applied to this record.", "fields": { "current_stage_evidence": { "outcome": "current_named_stack_campuses_generic_new_proposal_crosswalk_held", "scope": "The complete original current provider roster describes distinct POR01 and POR02 campuses. This pass does not independently crosswalk the inherited generic new Hillsboro proposals to those exact existing components or a further campus. Private reporting about last minute applications before a municipal pause does not establish an original final project entitlement or a physical construction stage. The selected original City policy host was unavailable at robots, so its current ban scope and exact applicability were not independently read or applied to this record." }, "source_read_scope": { "complete_current_original_por01_and_por02_roster_bodies_read": true, "existing_campuses_not_new_proposals": true, "city_policy_source_hold_retained": true, "no_citywide_ban_or_exact_property_exemption_inferred": true } }, "notes": [ "The complete original current provider roster describes distinct POR01 and POR02 campuses. This pass does not independently crosswalk the inherited generic new Hillsboro proposals to those exact existing components or a further campus. Private reporting about last minute applications before a municipal pause does not establish an original final project entitlement or a physical construction stage. The selected original City policy host was unavailable at robots, so its current ban scope and exact applicability were not independently read or applied to this record.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por01/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.stackinfra.com/locations/americas/portland/por02/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "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": "stack-por01-or", "state": "or", "kind": "facility", "name": "STACK POR01", "group": "unknown", "status": "Status unclear", "raw_status": "", "status_field": "", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "STACK Infrastructure", "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. POR01 campus and two building sections. Campus 80 MW including future expansion does not reconcile with displayed building powers 5 plus 72 MW. Retain scope conflict; no total current IT capacity inferred. 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.stackinfra.com/locations/americas/portland/por01/", "host": "stackinfra.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.63103, "lng": -123.14878, "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": "captured-operator-review-round6-2026-10-14.json", "scope": "POR01 campus and two building sections", "fields": { "campus_advertised_power_mw": 80, "future_expansion_power_mw": 36, "campus_acres": 18, "campus_buildings": 2, "building_sections": [ { "code": "POR01A", "advertised_power_mw": 5, "area_sqft": 65000 }, { "code": "POR01B", "advertised_power_mw": 72, "area_sqft": 215000 } ] }, "notes": [ "Campus 80 MW including future expansion does not reconcile with displayed building powers 5 plus 72 MW. Retain scope conflict; no total current IT capacity inferred.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por01/", "host": "stackinfra.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check 17, October 23, 2026", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. The POR01 page explicitly distinguishes future expansion and POR01A and POR01B. Their capacities and the page total differ in scope and are not reconciled or adopted as delivered figures.", "fields": { "company_association": { "name": "STACK Infrastructure", "role": "operator", "identity_scope": "provider_brand_only", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. The POR01 page explicitly distinguishes future expansion and POR01A and POR01B. Their capacities and the page total differ in scope and are not reconciled or adopted as delivered figures." }, "provider_role": "operator" }, "notes": [ "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. The POR01 page explicitly distinguishes future expansion and POR01A and POR01B. Their capacities and the page total differ in scope and are not reconciled or adopted as delivered figures.", "Global Stack and Fluidstack are not assigned to STACK Infrastructure by substring matching. Retrieval and publication dates remain separate from physical milestones." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por01/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact code or campus text, scoped provider relationship reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The complete original current POR01 campus body lists two component buildings and expressly includes a future expansion within its aggregate. This is a named provider campus listing without an independently read current physical stage or complete commissioned capacity for every component. Future expansion is not existing computing and the listed aggregate and component numbers are not reconciled or exported. No technical capacity, first opening day or new component identity is adopted.", "fields": { "current_stage_evidence": { "outcome": "current_por01_campus_listing_exact_commissioned_scope_held", "scope": "The complete original current POR01 campus body lists two component buildings and expressly includes a future expansion within its aggregate. This is a named provider campus listing without an independently read current physical stage or complete commissioned capacity for every component. Future expansion is not existing computing and the listed aggregate and component numbers are not reconciled or exported. No technical capacity, first opening day or new component identity is adopted." }, "source_read_scope": { "complete_current_original_por01_body_read": true, "future_expansion_not_existing_capacity": true, "aggregate_and_component_quantities_not_reconciled_or_exported": true } }, "notes": [ "The complete original current POR01 campus body lists two component buildings and expressly includes a future expansion within its aggregate. This is a named provider campus listing without an independently read current physical stage or complete commissioned capacity for every component. Future expansion is not existing computing and the listed aggregate and component numbers are not reconciled or exported. No technical capacity, first opening day or new component identity is adopted.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por01/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "stack-por02-or", "state": "or", "kind": "facility", "name": "STACK POR02", "group": "operating", "status": "Provider listed ready colocation capacity", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "STACK Infrastructure", "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. Advertised power basis not explicitly IT. No precise energization date or measured 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://www.stackinfra.com/locations/americas/portland/por02/", "host": "stackinfra.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" }, { "url": "https://www.stackinfra.com/wp-content/uploads/2020/11/POR02A_Brochure_031523.pdf", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.stackinfra.com/wp-content/uploads/2021/03/STACK_PR_Uptime_Institute.pdf", "host": "www.stackinfra.com", "published": "2021-04-08", "date": "2021-04-08", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "loc": { "lat": 45.47125, "lng": -123.11048, "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": "captured-operator-review-round6-2026-10-14.json", "scope": "named operator source", "fields": { "advertised_power_mw": 24, "campus_acres": 15, "campus_buildings": 1, "published_city": "Hillsboro, Oregon" }, "notes": [ "Advertised power basis not explicitly IT. No precise energization date or measured load.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por02/", "host": "stackinfra.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "whole_record_certified": false }, { "overlay": "Company role source check 17, October 23, 2026", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. Current POR02 explicitly names Hillsboro and POR02A. The separate general Hillsboro proposal record and other Portland campus codes are not merged.", "fields": { "company_association": { "name": "STACK Infrastructure", "role": "operator", "identity_scope": "provider_brand_only", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. Current POR02 explicitly names Hillsboro and POR02A. The separate general Hillsboro proposal record and other Portland campus codes are not merged." }, "provider_role": "operator" }, "notes": [ "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. Current POR02 explicitly names Hillsboro and POR02A. The separate general Hillsboro proposal record and other Portland campus codes are not merged.", "Global Stack and Fluidstack are not assigned to STACK Infrastructure by substring matching. Retrieval and publication dates remain separate from physical milestones." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por02/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact code or campus text, scoped provider relationship reviewed" } ], "checked": "2026-10-23", "whole_record_certified": false }, { "overlay": "Codex 3 research cohort 69", "scope": "The original current POR02 roster offers capacity and connectivity at its named single building campus. The original POR02A brochure describes immediately available RackReady data halls, and the separate 2021 issuer account documents earlier operations practice at POR02. Together these support provider listed ready colocation capacity rather than independently measured occupied computing load or current certification. The brochure has no independently established publication day, and its historical quantities and the older operations award are not recertified as current measured facts.", "fields": { "current_stage_evidence": { "outcome": "provider_named_por02_ready_colocation_capacity", "scope": "The original current POR02 roster offers capacity and connectivity at its named single building campus. The original POR02A brochure describes immediately available RackReady data halls, and the separate 2021 issuer account documents earlier operations practice at POR02. Together these support provider listed ready colocation capacity rather than independently measured occupied computing load or current certification. The brochure has no independently established publication day, and its historical quantities and the older operations award are not recertified as current measured facts." }, "source_read_scope": { "complete_current_original_por02_roster_body_read": true, "complete_original_three_page_por02a_brochure_text_read": true, "complete_original_two_page_operations_release_text_read": true, "old_award_not_current_certification": true, "brochure_path_not_publication_day": true, "no_measured_capacity_or_first_opening_export": true } }, "notes": [ "The original current POR02 roster offers capacity and connectivity at its named single building campus. The original POR02A brochure describes immediately available RackReady data halls, and the separate 2021 issuer account documents earlier operations practice at POR02. Together these support provider listed ready colocation capacity rather than independently measured occupied computing load or current certification. The brochure has no independently established publication day, and its historical quantities and the older operations award are not recertified as current measured facts.", "Existing roles, identities, physical placement, jurisdiction assignments, technical quantities and exact first opening days remain unchanged. Source retrieval does not date physical commissioning." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por02/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.stackinfra.com/wp-content/uploads/2020/11/POR02A_Brochure_031523.pdf", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-24", "label": "Reviewed operator source" }, { "url": "https://www.stackinfra.com/wp-content/uploads/2021/03/STACK_PR_Uptime_Institute.pdf", "host": "www.stackinfra.com", "published": "2021-04-08", "date": "2021-04-08", "checked": "2026-10-24", "label": "Reviewed operator source" } ], "checked": "2026-10-24", "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": "The original current POR02 roster offers capacity and connectivity at its named single building campus. The original POR02A brochure describes immediately available RackReady data halls, and the separate 2021 issuer account documents earlier operations practice at POR02. Together these support provider listed ready colocation capacity rather than independently measured occupied computing load or current certification. The brochure has no independently established publication day, and its historical quantities and the older operations award are not recertified as current measured facts.", "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": "stack-por03-or", "state": "or", "kind": "facility", "name": "STACK POR03", "group": "operating", "status": "Operating phase", "raw_status": "partly operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Washington" ], "city": "Hillsboro", "address": "", "who": "STACK Infrastructure", "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. POR03 campus operational versus future components. Explicit 72 MW operational critical capacity separated from near-term and expansion. Listed components total 193 MW versus approximately 200 MW headline. E/F combined area and power not repeated on each building. Water-use description is not measured withdrawal. 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.stackinfra.com/locations/americas/portland/por03/", "host": "stackinfra.com", "date": "", "published": "", "checked": "2026-10-14", "date_kind": "publication date not established", "label": "Reviewed source" } ], "loc": { "lat": 45.61984, "lng": -123.02815, "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": "captured-operator-review-round6-2026-10-14.json", "scope": "POR03 campus operational versus future components", "fields": { "campus_approximate_total_critical_capacity_mw": 200, "operational_critical_capacity_mw": 72, "near_term_capacity_mw": 25, "expansion_capacity_mw": 96, "campus_acres": 55, "campus_buildings": 6, "building_sections": [ { "code": "POR03A", "area_sqft": 182000, "power_mw": 24 }, { "code": "POR03B", "area_sqft": 180000, "power_mw": 24 }, { "code": "POR03C", "area_sqft": 180000, "power_mw": 24 }, { "code": "POR03D", "area_sqft": 198000, "power_mw": 25 }, { "code": "POR03E/F", "combined_area_sqft": 530000, "combined_power_mw": 96 } ] }, "notes": [ "Explicit 72 MW operational critical capacity separated from near-term and expansion. Listed components total 193 MW versus approximately 200 MW headline. E/F combined area and power not repeated on each building. Water-use description is not measured withdrawal.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por03/", "host": "stackinfra.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": "STACK explicitly distinguishes operational critical capacity at POR03 from near-term availability and expansion. This supports an operating phase, without adopting power totals or marking planned halls as commissioned. 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": "STACK explicitly distinguishes operational critical capacity at POR03 from near-term availability and expansion. This supports an operating phase, without adopting power totals or marking planned halls as commissioned. 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": [ "STACK explicitly distinguishes operational critical capacity at POR03 from near-term availability and expansion. This supports an operating phase, without adopting power totals or marking planned halls as commissioned." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por03/", "host": "www.stackinfra.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 17, October 23, 2026", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. POR03 expressly separates operational, near term and expansion capacity and identifies POR03A to POR03F. Provider identity does not certify full campus completion or transfer phase dates, power or water claims.", "fields": { "company_association": { "name": "STACK Infrastructure", "role": "operator", "identity_scope": "provider_brand_only", "scope": "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. POR03 expressly separates operational, near term and expansion capacity and identifies POR03A to POR03F. Provider identity does not certify full campus completion or transfer phase dates, power or water claims." }, "provider_role": "operator" }, "notes": [ "STACK Infrastructure explicitly lists this exact named campus or code in its own source. The operator role is an attributed provider brand relationship, not independently verified legal ownership, whole building control or operation of every phase. Current service and future development stay separate. No status, coordinate, address, physical date, power figure, water figure, safety, certification or environmental outcome is promoted. POR03 expressly separates operational, near term and expansion capacity and identifies POR03A to POR03F. Provider identity does not certify full campus completion or transfer phase dates, power or water claims.", "Global Stack and Fluidstack are not assigned to STACK Infrastructure by substring matching. Retrieval and publication dates remain separate from physical milestones." ], "sources": [ { "url": "https://www.stackinfra.com/locations/americas/portland/por03/", "host": "www.stackinfra.com", "published": "", "date": "", "checked": "2026-10-23", "label": "First party exact code or campus text, scoped provider relationship 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": "Exact site not published; shown at county level", "summary": "Hillsboro · Washington · Source context reviewed", "status_scope": "STACK explicitly distinguishes operational critical capacity at POR03 from near-term availability and expansion. This supports an operating phase, without adopting power totals or marking planned halls as commissioned. 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": "us-signal-or01-bend-or", "state": "or", "kind": "facility", "name": "US Signal OR01 Bend", "group": "operating", "status": "Operator-listed colocation service", "raw_status": "operating", "status_field": "current_status", "crypto": false, "type": "Data center (inventory classification)", "counties": [ "Deschutes" ], "city": "Bend", "address": "", "who": "US Signal", "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. Headline zero counters not usable area or IT capacity. Generator/UPS and utility kVA retained separately; redundancy does not multiply usable IT MW. Year built not exact data-center opening. Source labels UPS as 256 tons, an invalid UPS capacity unit. Quarantine that field rather than convert cooling tons into electrical MW. 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://ussignal.com/data-centers/or01-bend/", "host": "ussignal.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=20845+Sockeye+Place%2C+Bend%2C+OR+97701&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": 44.086522602423, "lng": -121.282839582783, "precision": "address", "basis": "Published US Signal facility address 20845 Sockeye Place, Bend, OR 97701 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": "captured-operator-review-round6-2026-10-14.json", "scope": "named operator source", "fields": { "operator_site_code": "OR01", "published_address": "20845 Sockeye Place, Bend, OR97701", "generator_kw": 2000, "ups_kw": null, "utility_kva": 2500, "operator_reported_year_built": 2010 }, "notes": [ "Headline zero counters not usable area or IT capacity. Generator/UPS and utility kVA retained separately; redundancy does not multiply usable IT MW. Year built not exact data-center opening.", "Source labels UPS as 256 tons, an invalid UPS capacity unit. Quarantine that field rather than convert cooling tons into electrical MW.", "Fields can apply to shared campus, regional or historical context; consult source review before assigning to a building." ], "sources": [ { "url": "https://ussignal.com/data-centers/or01-bend/", "host": "ussignal.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": "US Signal lists its specifically named OR01 Bend facility in its current colocation offering. LEED, disaster-risk and sustainability claims are not 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": "US Signal lists its specifically named OR01 Bend facility in its current colocation offering. LEED, disaster-risk and sustainability claims are not 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": [ "US Signal lists its specifically named OR01 Bend facility in its current colocation offering. LEED, disaster-risk and sustainability claims are not independently certified." ], "sources": [ { "url": "https://ussignal.com/data-centers/or01-bend/", "host": "ussignal.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 8, 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": 44.086522602423, "lng": -121.282839582783, "precision": "address", "basis": "Published US Signal facility address 20845 Sockeye Place, Bend, OR 97701 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": "20845 Sockeye Place, Bend, OR 97701", "county_fips": [ "41017" ], "operator_coordinates_adopted": false, "corporate_address_adopted": false } }, "notes": [ "The named official facility source publishes this service address. Corporate headquarters, related locations and maps are excluded. The blank native address wrapper remains exact, with the facility address retained only in reviewed location evidence.", "The unique Census street match and retained county boundary agree with the existing county. A calculated street reference does not establish a roof, floor, suite, full campus boundary, parcel, title or independent physical building. Status, dates, capacity and jurisdiction remain exact." ], "sources": [ { "url": "https://ussignal.com/data-centers/or01-bend/", "host": "ussignal.com", "published": "", "date": "", "checked": "2026-10-22", "label": "Official named facility street address block" }, { "url": "https://geocoding.geo.census.gov/geocoder/geographies/onelineaddress?address=20845+Sockeye+Place%2C+Bend%2C+OR+97701&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 27, October 23, 2026", "scope": "US Signal identifies the retained OR01 facility on its current provider page. Operator per source records that provider relationship. It does not establish legal property ownership, sole operation of a shared building or a separate legal operating entity. Existing identity, stage, street, county, coordinates and quantities stay unchanged. Publication date is unknown; the source check is not an opening date. Marketing service levels, certification claims and animated zero counters are not adopted as measured facility facts.", "fields": { "company_association": { "name": "US Signal", "role": "operator", "identity_scope": "provider_brand_only", "scope": "US Signal identifies the retained OR01 facility on its current provider page. Operator per source records that provider relationship. It does not establish legal property ownership, sole operation of a shared building or a separate legal operating entity. Existing identity, stage, street, county, coordinates and quantities stay unchanged. Publication date is unknown; the source check is not an opening date. Marketing service levels, certification claims and animated zero counters are not adopted as measured facility facts." }, "provider_role": "operator" }, "notes": [ "US Signal identifies the retained OR01 facility on its current provider page. Operator per source records that provider relationship. It does not establish legal property ownership, sole operation of a shared building or a separate legal operating entity. Existing identity, stage, street, county, coordinates and quantities stay unchanged. Publication date is unknown; the source check is not an opening date. Marketing service levels, certification claims and animated zero counters are not adopted as measured facility facts." ], "sources": [ { "url": "https://ussignal.com/data-centers/or01-bend/", "host": "ussignal.com", "published": "", "date": "", "checked": "2026-10-23", "label": "Current named OR01 provider relationship" } ], "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": "Bend · Deschutes · Source context reviewed", "status_scope": "US Signal lists its specifically named OR01 Bend facility in its current colocation offering. LEED, disaster-risk and sustainability claims are not 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": "western-oregon-computing-solutions-monmouth-or", "state": "or", "kind": "facility", "name": "Western Oregon University Computing Solutions Center", "group": "unknown", "status": "Status unclear", "crypto": false, "type": "Data center research context", "counties": [ "Polk" ], "city": "Monmouth", "address": "", "who": "Western Oregon University", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Official source identifies a named physical or planned data center context. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "date": "", "events": [ [ "2026-10-25", "Added to the atlas. Compilation date only, not opening or construction." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://cdn.wou.edu/board/files/2025/10/FAC-Docket-Mtg-No-42-Nov-4-2025.pdf", "host": "cdn.wou.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Official source retained for premises or county context" }, { "url": "https://wou.edu/ucs/php/WOU_EOC.pdf", "host": "wou.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Official source retained for premises or county context" } ], "loc": { "lat": 44.90344, "lng": -123.41331, "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." }, "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": false, "precision_label": "Exact site not published; shown at county level", "summary": "Monmouth sourced data center research context. County level only.", "reviewed_evidence": [ { "overlay": "Codex 3 inherited discovery review 16", "scope": "Official source identifies a named physical or planned data center context. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "fields": { "source_context": { "name": "Western Oregon University Computing Solutions Center", "operator": "Western Oregon University", "scope": "Official source identifies a named physical or planned data center context. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "address": "", "exact_street_unpublished": true }, "county_association": { "county": "Polk", "county_fips": "41053", "scope": "Emergency plan page7 explicitly places Monmouth campus in PolkCounty; alternate Salem site is in MarionCounty and is not an additional qualified data center." }, "atlas_added_event": { "kind": "atlas_added", "date": "2026-10-25", "scope": "Intended compilation day only. Must equal actual admission day before Native commit; never a physical milestone." } }, "notes": [ "Official source identifies a named physical or planned data center context. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "Historical forecasts, permits, funding and building occupancy do not establish current data center operation." ], "sources": [ { "url": "https://cdn.wou.edu/board/files/2025/10/FAC-Docket-Mtg-No-42-Nov-4-2025.pdf", "host": "cdn.wou.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Official source retained for premises or county context" }, { "url": "https://wou.edu/ucs/php/WOU_EOC.pdf", "host": "wou.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Official source retained for premises or county context" } ], "checked": "2026-10-25", "whole_record_certified": false } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "no_site_point", "county_display": "41053" } }, { "id": "oregon-state-data-center-salem-or", "state": "or", "kind": "facility", "name": "Oregon State Data Center Salem", "group": "unknown", "status": "Status unclear", "crypto": false, "type": "Data center research context", "counties": [ "Marion" ], "city": "Salem", "address": "", "who": "Oregon Enterprise Information Services Data Center Services", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "date": "", "events": [ [ "2026-10-26", "Added to the atlas. Compilation date only, not opening or construction." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://osuosl.org/blog/osl-moving-to-state-data-center/", "host": "osuosl.org", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://www.oregon.gov/jobs/Documents/PD-043850.pdf", "host": "www.oregon.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://cio.oregonstate.edu/year-review-2025", "host": "cio.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://oregonbuys.gov/bso/external/bidDetail.sda?docId=S-10700-00014148&external=true&parentUrl=close", "host": "oregonbuys.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" } ], "loc": { "lat": 44.90327, "lng": -122.58411, "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." }, "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": false, "precision_label": "Exact site not published; shown at county level", "summary": "Salem sourced data center research context. County level only.", "reviewed_evidence": [ { "overlay": "Codex 3 inherited discovery review 17", "scope": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "fields": { "source_context": { "name": "Oregon State Data Center Salem", "operator": "Oregon Enterprise Information Services Data Center Services", "scope": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "address": "", "exact_street_unpublished": true }, "county_association": { "county": "Marion", "county_fips": "41047", "scope": "Independent retained jurisdiction evidence supports county level placement. No exact data center street or point is adopted." }, "atlas_added_event": { "kind": "atlas_added", "date": "2026-10-26", "scope": "Intended compilation day only. Must equal actual admission day before Native commit; never a physical milestone." } }, "notes": [ "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "Historical schedules, permits, funding and announcements do not establish current operation." ], "sources": [ { "url": "https://osuosl.org/blog/osl-moving-to-state-data-center/", "host": "osuosl.org", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://www.oregon.gov/jobs/Documents/PD-043850.pdf", "host": "www.oregon.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://cio.oregonstate.edu/year-review-2025", "host": "cio.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://oregonbuys.gov/bso/external/bidDetail.sda?docId=S-10700-00014148&external=true&parentUrl=close", "host": "oregonbuys.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" } ], "checked": "2026-10-26", "whole_record_certified": false } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "no_site_point", "county_display": "41047" } }, { "id": "osu-kerr-corvallis-data-center-or", "state": "or", "kind": "facility", "name": "Oregon State Kerr Corvallis Data Center", "group": "unknown", "status": "Status unclear", "crypto": false, "type": "Data center research context", "counties": [ "Benton" ], "city": "Corvallis", "address": "", "who": "Oregon State University", "mw": null, "power": "", "power_note": "", "investment": "", "jobs": "", "acres": null, "utility": "", "water": "", "incentives": "", "note": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "date": "", "events": [ [ "2026-10-26", "Added to the atlas. Compilation date only, not opening or construction." ] ], "timeline": [], "opened": "", "tier": "", "sources": [ { "url": "https://osuosl.org/blog/osl-moving-to-state-data-center/", "host": "osuosl.org", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://facilities.oregonstate.edu/taking-back-control", "host": "facilities.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://cio.oregonstate.edu/year-review-2025", "host": "cio.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://www.corvallisoregon.gov/community/page/geography-demographics", "host": "www.corvallisoregon.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" } ], "loc": { "lat": 44.49197, "lng": -123.42917, "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." }, "manual_source_reviewed": true, "whole_record_certified": false, "field_evidence_present": true, "inventory_label_retained": false, "precision_label": "Exact site not published; shown at county level", "summary": "Corvallis sourced data center research context. County level only.", "reviewed_evidence": [ { "overlay": "Codex 3 inherited discovery review 17", "scope": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "fields": { "source_context": { "name": "Oregon State Kerr Corvallis Data Center", "operator": "Oregon State University", "scope": "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "address": "", "exact_street_unpublished": true }, "county_association": { "county": "Benton", "county_fips": "41003", "scope": "Independent retained jurisdiction evidence supports county level placement. No exact data center street or point is adopted." }, "atlas_added_event": { "kind": "atlas_added", "date": "2026-10-26", "scope": "Intended compilation day only. Must equal actual admission day before Native commit; never a physical milestone." } }, "notes": [ "Named data center research context supported by retained official sources. County association only. Current operating stage, exact site point and technical capacity remain unverified.", "Historical schedules, permits, funding and announcements do not establish current operation." ], "sources": [ { "url": "https://osuosl.org/blog/osl-moving-to-state-data-center/", "host": "osuosl.org", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://facilities.oregonstate.edu/taking-back-control", "host": "facilities.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://cio.oregonstate.edu/year-review-2025", "host": "cio.oregonstate.edu", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" }, { "url": "https://www.corvallisoregon.gov/community/page/geography-demographics", "host": "www.corvallisoregon.gov", "published": "", "date": "", "checked": "2026-10-25", "label": "Retained original premises or jurisdiction context" } ], "checked": "2026-10-26", "whole_record_certified": false } ], "location_display": { "policy": "reviewed-map-references-2026-10-23", "decision": "no_site_point", "county_display": "41003" } } ], "compilation_license": "withheld_pending_owner_decision" }