Facility or project event · Environmental review notice issued · Official record
Environmental review notice issued on 21 July 2026: Northtown Data Center (NTDC) (San Jose, CA) — state energy commission notice of preparation dated 21 July 2026
California Energy Commission staff issued a Notice of Preparation of a Draft EIR on July 21, 2026 for GIC San Jose LLC's NorthTown Backup Generating Facility (docket 25-SPPE-02), which the notice describes as planned as part of the NorthTown Park Data Center in San José.
- Event date
- NOP header 'Date: July 21, 2026'; docket stamp 'Docketed Date: 7/21/2026'.
- Source dated
- NOP 'Date' field and CEC docketing cover sheet.
- Source accessed
- Retrieved by DataCenterData; not an event date.
- Added to Latest updates
- When this entry entered the updates log; not an event date.
- Event type
- Environmental review notice issued · Filings and reviews
- Evidence basis
- Official record · California Energy Commission staff
- Confidence
- HighLead agency's own dated notice; campus link stated in the notice itself.
- State
- California
- Linked records
- Northtown Data Center (NTDC)
northtown-data-center-san-jose-ca - Linked claims
- None linked
What the source says
the California Energy Commission (CEC) staff has prepared a Notice of Preparation (NOP) to inform the Governor's Office of Land use and Climate Innovation (LCI) and each responsible and trustee agency that an Environmental Impact Report (EIR) will be prepared
Where: Page 1 of the NOP, first body paragraph; header fields Date, Project Applicant, NOP Review Period (July 21 – August 20, 2026)
Internet Archive copy (captured 21 September 2026)
What this does not establish
- Any approval, exemption or permit
- Construction start
- Operation or energization
- That 97.3 MW of backup generation equals IT load
Still unknown
- Draft EIR release date
- CEC decision on the SPPE
- City of San José entitlements for the data-center buildings
- IT capacity, operator/tenant, building owner
Identifiers
Event ID edafb9b607cd1c4e8c78d6bd705749ab357d9525bfafc0a0422c2ed744b76b33. The ID is derived from the event itself and never changes. A later correction would be published as a separate, linked entry.