Facility or project event · Agreement expired · Official record
Agreement expired on 30 June 2026: CoreWeave / Digital Crossroads expansion (Hammond, IN) — city notice dated 1 July 2026
The City of Hammond announced that the four-party development agreement for the proposed data center at 301 Digital Crossroads (City, Redevelopment Commission, Decennial Group and CoreWeave) expired because required milestones were not satisfied by the June 30, 2026 deadline.
- Event date
- Notice: milestones and obligations 'were required to be completed by the June 30, 2026 deadline. Because those conditions were not satisfied, the agreement has expired.' The expiry follows that stated deadline; the notice itself is dated July 1, 2026.
- Source dated
- Post byline date 'July 1, 2026' (article:published_time 2026-07-01T11:28:07-05:00).
- 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
- Agreement expired · Expired, withdrawn or cancelled
- Evidence basis
- Official record · City of Hammond
- Confidence
- HighOfficial notice from a contracting party; the event and deadline are stated directly.
- State
- Indiana
- Linked records
- CoreWeave / Digital Crossroads expansion
coreweave-hammond
What the source says
The City of Hammond announced today that the Development Agreement for the proposed data center project at 301 Digital Crossroads has expired following two previously approved extensions.
Where: News post body, first paragraph (byline July 1, 2026)
Source: Hammond Announces Expiration of Data Center Development Agreement
An archive request failed; no archived copy is linked.
What this does not establish
- Closure of the existing Digital Crossroad DX-1 facility
- Cancellation of any CoreWeave activity elsewhere
Still unknown
- Which milestones were unmet
- Whether a new agreement will be negotiated for the site
- Whether any expansion site work occurred before expiry
This event is also listed in the corrections history as an earlier lifecycle row: open the lifecycle row.
Identifiers
Event ID 136e497724993103569cd20e0d210c56a2fe3f047558a8d171fc3f050b69edf5. The ID is derived from the event itself and never changes. A later correction would be published as a separate, linked entry.