Latest updates · Project developments

Project developments

Openings, expansions, construction milestones, financing, contracts and ownership changes, as well as schedule changes, disputes, force majeure, litigation, pauses and cancellations at data-center projects DataCenterData tracks. Each entry names its source and who is making the claim, keeps reported claims separate from official records, and says what it does not establish. DataCenterData does not score or rank projects or companies.

8 reviewed developments8 projects6 public companies with reviewer-bound SEC IDsLast entry added 5 October 2026

Automated discovery checks selected filings and feeds for review leads. Reviewers read the source and confirm its subject before an independent review; discovery never publishes an entry or changes a project’s status.

Reported is not confirmed. A news report is shown as the publisher’s claim. An SEC filing or company release is the company’s own statement. None of them changes a project’s status on DataCenterData; only an official record can, through a separate review. This page shows no market prices, bond or loan pricing, and no score.

Timeline

Project developments, newest source date first.

The source date is when the filing, record or report was dated. A development date is shown only when a filing, official record or company statement supports it; news alone never dates one.

  1. Permit or regulatory changeOfficial recordIndependently reviewedTexas

    Permit or regulatory change: TCEQ index lists a Goodnight Data Center application received January 30, 2026 (Armstrong County, TX)

    The Texas Commission on Environmental Quality's pending New Source Review applications index lists a pending application from applicant Crusoe Energy Systems LLC for Goodnight Data Center, permit numbers 182880, GHGPSDTX268 and PSDTX1698, with a received date of 01/30/2026.

    Source dated
    Development date
    Added to DataCenterData

    Project: Goodnight Data Center

  2. Permit or regulatory changeOfficial recordIndependently reviewedTexas

    Permit or regulatory change: TCEQ index lists a Nexus Data Center Hubbard application received February 17, 2026 (Hill County, TX)

    The Texas Commission on Environmental Quality's pending New Source Review applications index lists a pending application from applicant Nexus Hubbard Power, LLC for Nexus Data Center Hubbard, permit numbers 183046, GHGPSDTX269 and PSDTX1700, with a received date of 02/17/2026.

    Source dated
    Development date
    Added to DataCenterData

    Project: Nexus Data Center Hubbard

  3. LitigationOfficial recordIndependently reviewedNew Mexico

    Litigation: NMED's AQB 26-57 docket lists an Order Lifting Stay from the New Mexico Supreme Court (Doña Ana County, NM)

    The New Mexico Environment Department's docket page for AQB 26-57(P), Yucca Growth Infrastructure, LLC - YGI Microgrid (Project Jupiter), lists an entry titled Order Lifting Stay (from the New Mexico Supreme Court) with the date 09/17/2026.

    Source dated
    Development date
    Added to DataCenterData

    Project: Project Jupiter

  4. Permit or regulatory changeOfficial recordIndependently reviewedNew York

    Permit or regulatory change: GCEDC project page lists an April 16, 2026 public hearing on the STREAM STAMP project (Genesee County, NY)

    The Genesee County Economic Development Center's projects page lists a public hearing dated April 16, 2026, with notice, transcript and archived livestream, in its review documents for STREAM U.S. Data Centers, LLC's proposed data center at STAMP.

    Source dated
    Development date
    Added to DataCenterData

    Project: STREAM U.S. Data Centers at STAMP (Project Double Reed)

  5. Permit or regulatory changeOfficial recordIndependently reviewedCalifornia

    Permit or regulatory change: Gilroy project page records a building permit issued March 19, 2026 (Santa Clara County, CA)

    The City of Gilroy's Gilroy Data Center (by Amazon Web Services) project page states that a building permit was issued on March 19, 2026 for project AS 20-23.

    Source dated
    Development date
    Added to DataCenterData

    Project: Gilroy Data Center

  6. Permit or regulatory changeOfficial recordIndependently reviewedIndiana

    Permit or regulatory change: Indianapolis commission recorded Thunderbird petition approvals (Marion County, IN)

    The Indianapolis Metropolitan Development Commission recorded approval of DCB Indianapolis LLC's amended variance and replat petitions at 305 Fintail Drive, with the variance approval subject to the commitment-filing requirement in footnote 1.

    Source dated
    Development date
    Added to DataCenterData

    Project: DC BLOX Thunderbird

  7. Material contractOfficial recordIndependently reviewedVirginia

    Material contract: Louisa County approved an EdgeCore performance agreement (Louisa County, VA)

    The Louisa County Board of Supervisors voted to approve a local performance agreement with EDI Louisa 1 LLC, identified in the minutes as EdgeCore and the purchaser of Shannon Hill Regional Business Park.

    Source dated
    Development date
    Added to DataCenterData

    Project: EdgeCore Shannon Hill Data Center Project

Relationships

Projects, companies and counterparties.

Only relationships a DataCenterData record already states, matched to a curated company by the record’s exact wording. Lenders and other financing counterparties appear only when a reviewed source names them; none is recorded yet.

Public companies (6)

Private developers and operators (2)

Market data

What this page does not show yet, and why.

Each dataset has a written contract and a rights gate. The page cannot display a dataset whose gate has not passed.

  • Public-company filings and disclosed commitments

    Not shown. Filings appear above only as reviewed developments. DataCenterData does not add up disclosed commitments, leases or capital spending across companies, periods or projects.

  • Corporate bonds and project loans

    Not shown. No licensed bond or loan dataset is connected. FINRA TRACE bond-trade data could be added later, but only after its data agreement and redistribution limits are reviewed.

  • Credit default swaps

    Not shown. Credit-default-swap levels come only from commercial providers, and none has granted display and redistribution rights. A screenshot or a level quoted in the press is not a grant.

  • Share prices and market reactions

    Not shown. Market moves reported alongside a development are not repeated here, and no chart compares prices with project events.

Method

How entries are reviewed.

Sources are ranked. A higher tier never makes a lower-tier claim stronger than its own wording.

  1. Tier 1. SEC filing or official regulatory, court, permit or utility document. An SEC filing is the filer’s own statement; the SEC does not vouch for it.
  2. Tier 2. Company investor-relations or formal corporate disclosure: shown as the company’s statement.
  3. Tier 3. Attributed reputable reporting: shown as the publisher’s report, never as a DataCenterData finding, and never used to date a development or change a status.
  4. Tier 4. Lead that requires further verification: can start a review, never published.
  • Nothing is published automatically. Discovery only opens review tasks.
  • A company is linked to a filing only through a CIK a reviewer recorded with an SEC receipt; names are never matched to find one.
  • A name that could mean more than one project, such as “Jupiter” on its own, is held for review.
  • A source that robots.txt, a login, a paywall or a challenge withholds is never bypassed. It is read only by someone with lawful access, or not used.
  • A later, stronger source replaces an entry; the earlier entry’s link keeps working.

Scheduled discovery checks the high-risk watchlist about every six hours and the full discovery watchlist once a day, using selected SEC filings and registered feeds. Completed checks produce review leads, not verified claims. Publication requires source review and independent acceptance.

Latest updates →State and local policy →Methodology →Change log →

Corrections

Named in an entry? Send a correction or a response.

A company, public body or person named in an entry can ask for a correction or send a sourced response. Use the correction form or write to corrections@datacenterdata.com. A response backed by a document is reviewed like any other source; an accepted correction is published on Change log, and the corrected entry keeps its link.