Data Centers Atlas: Oregon

Weekly data center brief: Oregon

Week of: October 26, 2026

Research through: October 29, 2026

Source reviews and additions to the Atlas collection. Review dates do not establish openings or physical events. Scheduled dates are not outcomes.

Read the complete sourced brief

Dated record: Oregon State Data Center Salem

Recorded event date: October 26, 2026

Added to the atlas. Compilation date only, not opening or construction.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

Dated record: Oregon State Kerr Corvallis Data Center

Recorded event date: October 26, 2026

Added to the atlas. Compilation date only, not opening or construction.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

Dated record: Western Oregon University Computing Solutions Center

Recorded event date: October 25, 2026

Added to the atlas. Compilation date only, not opening or construction.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

Dated record: Oakline at Mill Creek

Recorded event date: July 30, 2026

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.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

apps.oregon.gov

News report: Umatilla County

OPB reported residents' noise, light and traffic concerns near Umatilla-area data centers and modeled possible generator emissions during a regional blackout. Its methodology describes assumptions and revised calculations; Amazon disputed the scenario's likelihood. A later governor letter requests a permitting pause for new or expanded facilities. These records do not establish measured exposure, a violation or closure of existing sites.

Record status: unknown. The later disposition of the documented nuisance and regional air concerns is unknown in this bounded review. A modeled scenario, company statement or governor's new/expanded-permit pause request does not establish actual outage emissions, independent compliance, implementation for a particular permit or resolution of every existing-site concern.

Event date: Not established

Source publication date: July 22, 2026

Disposition date: Not established

Concern sources checked: October 18, 2026

Interviews and nuisance episodes have no independently established exact event day. The October 9 date belongs to a separate original statewide policy letter, not a nuisance occurrence, outage or site enforcement action. The item event date remains unknown. The investigation and method display July 22, 2026 publication; the investigation was updated July 23. The separate current report is published October 13 and updated October 14. Original governor letter is dated October 9, but its first public PDF posting day is unknown.

Raised or recorded by OPB.

Company statement reported by an outlet

Amazon Web Services stated, according to OPB, that a territory-wide outage would be extraordinarily rare and that its emergency generators protect service during interruptions. The outlet also reports company plans for pollution-controlled equipment at new sites. Those statements are not independent measurements, completed retrofits or a response for every facility.

The original article expressly presents Amazon statements in response to its regional generator investigation. July 22 is the outlet publication, not an independently verified company-original statement day. The same-day method describes revised math and company exchanges; lack of a later math challenge is not endorsement. October policy objections are not relabeled as a specific nuisance reply.

Response publication date: July 22, 2026

Response sources checked: October 18, 2026

Counts describe attributed documentation, not harm or severity. Allegations, procedural outcomes and published replies retain their separate scope.

Dated record: Flexential Portland - Hillsboro 5

Recorded event date: May 28, 2026

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.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

www.flexential.com

Dated record: Flexential Portland - Hillsboro 4 (PDX04)

Recorded event date: May 28, 2026

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

www.flexential.com

Regulator record: Boxminer La Pine Bitcoin Mining Facility

La Pine City Council recorded staff concerns about the basis for Boxminer power revenues, franchise fees and employment forecasts, the lack of an established utility rate for the proposed load, and missing supporting utility information. The unsigned meeting account also reports a motion to conclude the land sale matter. These are attributed staff assessments and a recorded procedural account, not Atlas findings of fraud, measured grid impacts, delivered jobs, approved tariffs or present physical shutdown.

Record status: unknown. The official packet documents the staff questions and a land transaction motion. Adoption of the unsigned minutes, later project or permit disposition, actual utility conditions and resolution of the concerns remain unverified.

Event date: May 27, 2026

Source publication date: Not established

Disposition date: Not established

Concern sources checked: October 23, 2026

The packet labels this as the May 27, 2026 meeting account. Its minutes signature fields are blank, and the first day the questions were raised is not established. The June 10 agenda date does not establish the exact first online publication day.

Raised or recorded by La Pine City Council.

City of La Pine

Counts describe attributed documentation, not harm or severity. Allegations, procedural outcomes and published replies retain their separate scope.

News report: Morrow County

Oregon Capital Chronicle reported an Amazon settlement announcement over regional groundwater allegations, alongside the company's denial and no admission of liability. Later OPB reporting described court approval as pending at that time. This county-level news context does not establish present final approval, payment, causation, completed remediation or responsibility at an individual data-center campus.

Record status: unknown. The present final approval, payment and remedial outcome are unknown in this bounded review. OPB reported approval pending in August; an announced settlement or reported preliminary-approval lead does not establish final court approval, actual disbursement, admitted liability or resolution of all regional groundwater concerns.

Event date: Not established

Source publication date: March 31, 2026

Disposition date: Not established

Concern sources checked: October 18, 2026

The article reports a settlement announcement but the original signed execution, filing or actual approval date was not independently established. The event date stays unknown; publication and a relative Tuesday reference are not substituted for a verified court event. The original Oregon Capital Chronicle report displays March 31, 2026 publication with later same-day company/group updates. The independently read OPB follow-up is published August 12, not its August 13 syndication. Source checks are separate from all execution, court and payment dates.

Raised or recorded by Oregon Capital Chronicle.

Company statement reported by an outlet

Amazon Data Services stated, according to Oregon Capital Chronicle, that it denied contributing to the groundwater problem and chose to settle to avoid extended litigation and focus on community support. The report describes no admission of liability. This is an outlet-reported statement, not a court finding or verified completed remedy.

The original March 31 report explicitly attributes the statement to an Amazon spokesperson in the same reported settlement discussion; its update note records the company reply later that same day. March 31 is outlet publication, not an independently reviewed company-original statement/execution day. Other defendants and separate farm settlements are not attributed to Amazon.

Response publication date: March 31, 2026

Response sources checked: October 18, 2026

Counts describe attributed documentation, not harm or severity. Allegations, procedural outcomes and published replies retain their separate scope.

Public concern on the record: Roundhouse Cascade Locks Data Center

Port of Cascade Locks and Roundhouse said in their joint July 20, 2023 announcement that the community support needed for their proposed computing project was not achieved. They attributed the decision to discontinue the project to community feedback and incompatibility with current community sentiments. This is the joint participants account rather than direct resident testimony, a petition total, measured harm, a general ban or physical closure.

Record status: unknown. The original Port joint statement explicitly identifies the Roundhouse proposal and describes insufficient community support. It does not independently establish current concern disposition, a complete public comment record or the present outcome of every possible project at the Port.

Event date: Not established

Source publication date: July 20, 2023

Disposition date: Not established

Concern sources checked: October 24, 2026

The joint public announcement is dated July 20, 2023. The exact first community comment, underlying discontinuation decision and complete public input chronology are not independently dated in this bounded source. The release date is printed in the original Port announcement. Its date does not become an exact first community objection or physical facility closure day.

Raised or recorded by Port of Cascade Locks.

Company statement published by an agency or court

Roundhouse Inc. stated in the joint Port announcement that the proposed project would be discontinued and that no future computing partnerships were planned between those two organizations at that point. This is a direct joint statement without independently dated earlier deliberations or a verified current concern resolution.

The original Port announcement expressly identifies Roundhouse as a joint participant in this same project discontinuation and community support account.

Response publication date: July 20, 2023

Response sources checked: October 24, 2026

Port of Cascade Locks original joint Roundhouse announcement

Counts describe attributed documentation, not harm or severity. Allegations, procedural outcomes and published replies retain their separate scope.

Dated record: Roundhouse Cascade Locks Data Center

Recorded event date: July 20, 2023

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.

A recorded date retains its original source and phase scope. A scheduled date does not confirm that the event happened or permission was granted. Source-check dates are separate.

www.portofcascadelocks.gov