Evidence ledger · proposed expansion expired

Hammond: the expired expansion is separate from the existing facility.

Hammond approved a proposed 450,000-square-foot, 180 MW CoreWeave expansion in 2025. After two extensions, the city said required milestones were not satisfied and the agreement expired on June 30, 2026. Council minutes dated June 9, 2025 identify CoreWeave as an existing tenant at 100 Digital Crossroads Drive, separate from the proposed 301 project. The expiration notice does not report that existing facility’s closure or freshly confirm its operating status.

Developer: Decennial Group / Digital CrossroadsProposed tenant: CoreWeavePower provider: NIPSCOLast checked: 11 September 2026

Current assessment

The expansion was not delivered before the agreement expired, but the public record does not support calling every contemplated benefit a “broken promise.” Council minutes and the city’s 2025 approval notice say the project was contingent on finalizing a NIPSCO power agreement and then executing the lease. The full development-agreement PDF was not separately obtained; exact unsatisfied milestones remain unnamed in the expiration notice.

QuestionDid the proposed CoreWeave expansion at 301 Digital Crossroads proceed, and what happened to the existing DX-1 facility?
FindingCity outcome record (1 July 2026): after two extensions, milestones and obligations due by 30 June 2026 were not satisfied; the development agreement among the City, Redevelopment Commission, Decennial Group and CoreWeave expired with no further extension. Council minutes dated 9 June 2025, page 4, identify CoreWeave as an existing tenant at 100 Digital Crossroads Drive and distinguish that facility from the proposed 301 project. That historical statement and the expiration notice do not freshly verify current operation or establish closure of the existing facility.
180 MWproposed facility sizeCoreWeave description in council record; not a utility filing
450K ft²proposed new building301 Digital Crossroads; separate from DX-1
35–90projected permanent jobsProposal; not delivered; due status not established
Up to $4Mannual impact payment concept20-year concept in minutes; due status not established
30 Jun 2026agreement expirationCity outcome record

Claims

A verdict applies only to the wording shown.

Company claims are shown as stated; they are not findings.

Construction & status · Digital Crossroad Hammond campus

Contradicted

A question DataCenterData examined; no one is quoted.

Checked 11 September 2026 · Next check: no trigger recorded

The expiration of Hammond's CoreWeave agreement means the existing Digital Crossroad data center closed.

What the evidence supports

Hammond says the separate agreement for the proposed 301 Digital Crossroads expansion expired. June 9, 2025 council minutes identify CoreWeave as an existing tenant at 100 Digital Crossroads Drive. The failed expansion and existing DX-1 site are not the same lifecycle event; the notice does not establish closure of the existing facility.

Biggest limitation

These records do not freshly confirm the existing facility’s current operating status.

Confidence: medium · 2 sources

Open full claim →

Construction & status · CoreWeave / Digital Crossroads expansion

Outdated

Said by the City of Hammond · government record · 10 June 2025 →

Checked 11 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

450,000 square feet; 180 MW; contemplated 20-year CoreWeave lease

What the evidence supports

Development agreement expired; expansion not delivered.

Biggest limitation

Exact unsatisfied milestones.

Confidence: medium — city-approved proposal · 2 sources

Open full claim → History (1) →

Jobs · CoreWeave / Digital Crossroads expansion

Outdated

Said by the City of Hammond · government record · 9 June 2025 →

Checked 11 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

35 to 90 jobs paying more than $75,000

What the evidence supports

Not delivered; due status not established.

Biggest limitation

Evidence basis: city-council projection

Confidence: medium — city-council projection · 1 source

Open full claim → History (1) →

Community impact · CoreWeave / Digital Crossroads expansion

Outdated

Said by the City of Hammond · government record · 9 June 2025 →

Checked 21 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

Up to $4 million per year for 20 years

What the evidence supports

Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. The City announced on 1 July 2026 that the agreement for 301 Digital Crossroads had expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. No community impact payment is shown as due or received in the saved record, and the notice concerns the proposed 301 expansion, not the separate existing DX-1 facility; it does not freshly confirm current operation.

Biggest limitation

The executed agreement and its payment-trigger clauses, the two extension resolutions, which milestones failed…

Still unknown

The executed agreement and its payment-trigger clauses, the two extension resolutions, which milestones failed and any City payment ledger are not in the saved record; whether any payment was ever due or made is not established.

Confidence: medium — city-council description · 3 sources

Open full claim → History (3) →

Community impact · CoreWeave / Digital Crossroads expansion

Unknown

Said by the City of Hammond · government record · 22 December 2025 →

Checked 21 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

$25 million lump sum discussed

What the evidence supports

Discussed, not contracted, then the agreement lapsed. The 22 December 2025 minutes record the $25 million as announced but 'Right now it's not part of it'. The City announced on 1 July 2026 that the development agreement had expired after two extensions. No payment is shown as due or received in the saved record.

Biggest limitation

Whether the $25 million was ever written into an executed instrument;

Still unknown

Whether the $25 million was ever written into an executed instrument; the executed agreement, the extension resolutions and any City payment ledger are not in the saved record.

Confidence: medium — verbal concept in council discussion · 2 sources

Open full claim → History (2) →

Taxes & incentives · CoreWeave / Digital Crossroads expansion

Outdated

Said by the City of Hammond · government record · 9 June 2025 →

Checked 21 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

10-year construction abatement and 20-year 100% technology deduction

What the evidence supports

Authorized terms, then lapsed. The 9 June 2025 minutes describe the contemplated 10-year construction abatement and 20-year 100% technology deduction alongside the development agreement adopted by Resolution 25R-16 (8–0, one member absent); the scope and terms of the CoreWeave equipment deduction and the Decennial construction abatement requested at the same meeting were not part of that resolution's vote and are not reviewed. The City announced on 1 July 2026 that the agreement had expired after two extensions. No abatement or deduction is shown as adopted, claimed or received in the saved record.

Biggest limitation

The executed agreement, any separate abatement or deduction instrument (and whether one was ever adopted…

Still unknown

The executed agreement, any separate abatement or deduction instrument (and whether one was ever adopted, claimed or received), the extension resolutions and any payment or abatement ledger are not in the saved record.

Confidence: medium — city-council description · 3 sources

Open full claim → History (3) →

Power · CoreWeave / Digital Crossroads expansion

Unknown

Said by the City of Hammond · government record · 9 June 2025 →

Checked 21 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

Final NIPSCO agreement explicitly described as gating

What the evidence supports

The 9 June 2025 minutes describe a final NIPSCO agreement as gating the expansion. No executed NIPSCO agreement is in the saved record, and the City's 1 July 2026 notice says the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026, without naming which. The NIPSCO agreement remains unknown. The notice concerns the proposed 301 expansion, not the separate existing DX-1 facility; it does not freshly confirm current operation.

Biggest limitation

Whether a NIPSCO agreement was ever executed, and which milestones failed;

Still unknown

Whether a NIPSCO agreement was ever executed, and which milestones failed; the executed development agreement, the extension resolutions and any NIPSCO filing for this expansion are not in the saved record.

Confidence: medium — city-council record · 3 sources

Open full claim → History (3) →

Construction & status · CoreWeave / Digital Crossroads expansion

Company claim

Said by Digital Crossroad · company statement in Digital Crossroad Indiana data center page →

Checked 10 September 2026 · Next check: replacement proposal, new NIPSCO docket or new development agreement

DX-1 operating; operator publishes 105,000 square feet and up to 20 MW

What the evidence supports

Digital Crossroad said this. DataCenterData has not found an independent record that confirms or contradicts it; it is shown as the company’s statement, not as a finding either way.

Biggest limitation

Capacity scope is not classified as critical IT load.

Confidence: medium — operator-reported · 1 source

Open full claim →

History

Correction · 11 September 2026 · DataCenterData review

coreweave-hammond → Community impact payments

Field Community impact payments

From Previous locator

To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10

Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.

Evidence https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 21 September 2026 · DataCenterData review

coreweave-hammond → Community impact payments

Field Community impact payments

From Not shown due or paid.

To Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. The City announced on 1 July 2026 that the agreement for 301 Digital Crossroads had expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. No community impact payment is shown as due or received in the saved record, and the notice does not concern the operating DX-1 facility, which is a separate record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · DataCenterData review

coreweave-hammond → Additional payment

Field Additional payment

From Minutes say it was not yet in the agreement.

To Discussed, not contracted, then the agreement lapsed. The 22 December 2025 minutes record the $25 million as announced but 'Right now it's not part of it'. The City announced on 1 July 2026 that the development agreement had expired after two extensions. No payment is shown as due or received in the saved record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · DataCenterData review

coreweave-hammond → Incentives

Field Incentives

From Claimed or received amounts not established.

To Authorized terms, then lapsed. The 9 June 2025 minutes describe the contemplated 10-year construction abatement and 20-year 100% technology deduction alongside the development agreement adopted by Resolution 25R-16 (8–0, one member absent); the scope and terms of the CoreWeave equipment deduction and the Decennial construction abatement requested at the same meeting were not part of that resolution's vote and are not reviewed. The City announced on 1 July 2026 that the agreement had expired after two extensions. No abatement or deduction is shown as adopted, claimed or received in the saved record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · DataCenterData review

coreweave-hammond → Power agreement

Field Power agreement

From No executed agreement located; exact failed milestones undisclosed.

To The 9 June 2025 minutes describe a final NIPSCO agreement as gating the expansion. No executed NIPSCO agreement is in the saved record, and the City's 1 July 2026 notice says the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026, without naming which. The NIPSCO agreement remains unknown. The notice does not concern the operating DX-1 facility, which is a separate record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Dated events

Real-world events recorded for this record, newest event date first. Each event page shows its source, dates and what it does not establish.

  1. Agreement expiredOfficial recordIndiana

    Agreement expired on 30 June 2026: CoreWeave / Digital Crossroads expansion (Hammond, IN) — city notice dated 1 July 2026

    Event date
    Source dated
    Added to Latest updates
  2. Development agreement approvedOfficial recordIndiana

    Development agreement approved on 9 June 2025: CoreWeave / Digital Crossroads expansion (Hammond, IN) — city council minutes dated 9 June 2025

    Event date
    Source dated
    Added to Latest updates

Timeline

Council approves the development agreement

Minutes: Decennial constructs; CoreWeave locates in a new 450,000 ft² building at 301 Digital Crossroads under a contemplated 20-year lease; CoreWeave already a tenant at 100 Digital Crossroads. Community impact payment described as up to $4 million/year for 20 years if abatements are agreed. Timeline begins once Decennial and NIPSCO sign a power agreement.

First extension discussed and approved

Minutes/resolution: utility negotiations continue; NIPSCO had submitted a proposed power agreement to Decennial. A separate $25 million lump-sum commitment is discussed as being finalized during a short extension—described as not yet fully documented in the agreement at that meeting.

Extended deadline passes

After two extensions, required obligations and milestones remain unsatisfied. The city does not name the exact failed milestones.

City announces expiration

Hammond says it will grant no further extension. The notice concerns the proposed project at 301 Digital Crossroads and does not address DX-1.

Source evidence

Neutral readingThis is a negative expansion outcome and a useful developer/tenant track-record event. It is not evidence that DX-1 closed, that $80 million was withheld after becoming due, or that CoreWeave alone caused the agreement to lapse.

Review date follows the coreweave-hammond record check token; it is not advanced merely because this ledger was clarified against the captured minutes and notices.

Recorded information

What this page records, grouped by topic, with the source's units and qualifications. Company-reported values stay labeled as company-reported. Related listings are shown separately.

Reviewed record coreweave-hammond

Project · CoreWeave. Independently reviewed record. Values are shown with their recorded basis.

The expired agreement concerns the proposed 301 project. June 2025 council minutes describe existing tenancy at 100; these records do not freshly confirm current operation.

Location and precision

  • Hammond, IN · Lake County (Place centre, not the site)

Roles

  • Owner: Decennial Group / Digital Crossroads
  • Developer: Decennial Group / Digital Crossroads
  • Operator: CoreWeave

Lifecycle

  • Recorded status: expired

    Hammond says the separate development agreement expired after required milestones were not satisfied by the June 30, 2026 deadline. June 9, 2025 council minutes identify existing CoreWeave tenancy at 100 Digital Crossroads Drive, separate from the proposed 301 project. These records do not freshly confirm current operation.

Power capacity

  • Power detail: 180 MW city-reported project specification

    Recorded with its stated kind; not a measured load and not comparable across records.

  • Capacity — Not yet recorded here.

Cooling, water, PUE and WUE

  • Cooling and water: Not established in the reviewed city release.

Permits, incentives, jobs and proceedings

  • Projected permanent jobs: 35 to 90 positions paying more than $75,000 Announced jobs · city-council projection for proposed expansion · project scope

    not delivered; due status not established because the expansion agreement expired

    Announced job figures are not observed headcount. Different scopes stay separate.

  • Announced investment: multibillion-dollar city description; no precise amount established · 450,000-square-foot expansion scope

    Announced figure, not spending.

  • Incentives and commitments: The expired agreement referenced Community Impact Payments. No payment is treated as delivered without evidence that it came due and was paid.

Sources, dates, limitations and corrections

  • Sources: 4 cited sources, listed on this page
  • Evidence still needed: independently supported demand figure

Not yet recorded here: Area, acreage and buildings · Connectivity · Services · Certifications and design ratings · Rack density · Availability · Specification links and contact.

Next research question

  • Archive and extract the expired agreement, determine which milestones failed, and monitor any replacement development proposal separately from the operating DX-1 facility.

Update this profile with a public source. The request includes topics needing more information; this does not mean the facility lacks them. Corrections and additions are reviewed before publication.

Data + actions

Suggest a correction → Record ID coreweave-hammond and the page are prefilled. Accepted material corrections appear on Changes.

Facility evidence across sources

Identity

Facility ID
dcd-fac-002465 (public id fac-002465)
Unit
site (campus or building not established)
Name source
CoreWeave / Digital Crossroads expansion · DataCenterData reviewed record coreweave-hammond
Evidence tier
reviewed
Part of
Digital Crossroad — Hammond campus fac-002474

Other names

Operators and presences

2 statement(s) naming an operator or presence at this site unit, one row per source. A building with several tenants is one facility with several presence rows.

Operator of record (reviewed): CoreWeave.

Operator as statedRoleUnitStated byDate
CoreWeave
Family: CoreWeave
owner or operator (reviewed)site unknownDataCenterData reviewed record coreweave-hammond
CoreWeave
Family: CoreWeave
named by this source (role not established)facilityCompute Atlas licensed discovery row dcd-dir-000337

Status by layer

LayerValueDateSource
Reviewed (DCD) · verified recordexpired
Status basis: Hammond says the separate development agreement expired after required milestones were not satisfied by the June 30, 2026 deadline. June 9, 2025 council minutes identify existing CoreWeave tenancy at 100 Digital Crossroads Drive, separate from the proposed 301 project. These records do not freshly confirm current operation.
Latest source retrieval/capture date DataCenterData reviewed record coreweave-hammond
Provider-reported (Compute Atlas)provider-reported: cancelledProvider row updated
Provider-reported announcement date: June 2025
Provider dates do not establish when this status began or whether it remains current.
Compute Atlas licensed discovery row dcd-dir-000337

Layers disagree; not reconciled. Each value is what that layer states; DataCenterData does not pick one.

Capacity by kind

Each row is one kind of figure from one source. Utility, generation, design, critical IT and floor-area figures measure different things; they are never summed or totalled.

KindValue and evidenceScope and timingDateSource
Provider-reported capacityPlanned: 180 MW (source-reported; boundary not independently verified; MW measure not stated by provider)
provider-reported

compute atlas public projection

scope not statedProvider row updated Compute Atlas licensed discovery row dcd-dir-000337
Utility (provider note)NIPSCO
provider-reported

compute atlas public projection · Utility as named by the provider.

scope not statedProvider row updated Compute Atlas licensed discovery row dcd-dir-000337

Location

City
Hammond
County
Lake
State
IN
Metro (CBSA)
Chicago-Naperville-Elgin, IL-IN 16980

Coordinates not published; the best available coordinate's precision is unknown, below street level.

Address as published by DataCenterData reviewed record coreweave-hammond. No member source publishes a street address for this facility.

Facts

Quote-bound facts: each shows the value, the source address, the capture hash (first 12 characters; the full SHA-256 is in the page markup) and the capture date. The source's exact wording stays in the capture record and is not republished here; the capture hash binds it.

No quote-bound fact with a hashed capture is recorded for this facility.

Other values by layer

FieldValueLayer and basisDateSource
ownerDecennial Group / Digital CrossroadsReviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
developerDecennial Group / Digital CrossroadsReviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
announced investmentmultibillion-dollarReviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
permanent jobs35 to 90 positions paying more than $75,000Reviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
power detail180 MWReviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
incentives commitmentsThe expired agreement referenced Community Impact Payments. No payment is treated as delivered without evidence that it came due and was paid.Reviewed (DCD) · reviewed recordLatest source retrieval/capture date date not statedDataCenterData reviewed record coreweave-hammond
reported.energy.sourceGrid
Provider label.
provider-reported · compute atlas public projectionProvider row updated Compute Atlas licensed discovery row dcd-dir-000337
reported.ai classificationconfirmed
Compute Atlas classification, not a DataCenterData finding.
provider-reported · compute atlas public projectionProvider row updated Compute Atlas licensed discovery row dcd-dir-000337
reported.announced dateJune 2025
Provider-reported announcement date.
provider-reported · compute atlas public projectionProvider row updated Compute Atlas licensed discovery row dcd-dir-000337
facility typedata_centerprovider-reported · compute atlas public projectionProvider row updated Compute Atlas licensed discovery row dcd-dir-000337

Sources for the reviewed record

These citations belong to the linked reviewed records. They do not establish every figure or present-day operating status. Publication and retrieval dates are shown separately; an unstated date remains unknown.

Details still needed

28 fields in the shared profile are not established for this record. Each states why; missing information does not mean zero or absence.

  • Street address · not recorded for this field in the register
  • Postal code · not recorded for this field in the register
  • Map location precision · not recorded for this field in the register
  • Operator-stated status · not recorded for this field in the register
  • Status in public records · not recorded for this field in the register
  • Critical IT capacity (MW) · not recorded for this field in the register
  • Requested utility capacity (MW) · not recorded for this field in the register
  • Reported total power (MW) · not recorded for this field in the register
  • Generation capacity (MW) · not recorded for this field in the register
  • Company-announced design capacity (MW) · not recorded for this field in the register
  • Floor area (sq ft) · not recorded for this field in the register
  • Data hall or IT floor area (sq ft) · not recorded for this field in the register
  • Site area · not recorded for this field in the register
  • Cooling redundancy · not recorded for this field in the register
  • UPS redundancy · not recorded for this field in the register
  • Backup generator redundancy · not recorded for this field in the register
  • Tier design rating · not recorded for this field in the register
  • Cooling technology · not recorded for this field in the register
  • Opening year or expected opening year · not recorded for this field in the register
  • Network presence · not recorded for this field in the register
  • Service · not recorded for this field in the register
  • Certification or compliance claims · not recorded for this field in the register
  • Rack density · not recorded for this field in the register
  • Space or power availability · not recorded for this field in the register
  • Specifications and facility pages · not recorded for this field in the register
  • Business contact · not recorded for this field in the register
  • Public registration · not recorded for this field in the register
  • Fact supported by a source quotation · not recorded for this field in the register

Jurisdiction and policy actions

Policy actions are matched to this facility by jurisdiction (state, county, municipality or utility), never by the facility's name. A match means the action covers the place, not that it names or affects this facility.

Updates, corrections and review

Last checked

How often we re-check

We plan to re-check this facility every 180 days because it has a reviewed record. Next check due . The last-checked date is the newest evidence date among this facility's sources. Dates are measured against the newest input date, , not the day this page was built.

Update events

Corrections

  • · City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged. details
  • · City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged. details
  • · City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged. details
  • · City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged. details
  • · 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'. details
  • · 2026-09-11: previously 'pp. 3–4'. details
  • · 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'. details
  • · 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'. details
  • · 2026-09-11: previously 'pp. 3–4'. details
  • · 2026-09-11: previously 'pp. 3–4'. details
  • · 2026-09-11: previously 'pp. 3–4'. details
  • · 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'. details
  • · 2026-09-11: previously 'pp. 3–4'. details

Related claims

Update this profile with a public source. The request includes topics needing more information; this does not mean the facility lacks them. Corrections and additions are reviewed before publication.

How complete the facility register is

Rights for this record

For each populated field, the origin of the value shown on this page and the terms it carries. Values that are not redistributable may be read and cited here but are not relicensed.

Values marked Compute Atlas are adapted from Compute Atlas by Edward Kubiak under CC BY 4.0: Compute-infrastructure data from Compute Atlas by Edward Kubiak. DataCenterData did not independently verify them.

FieldSupplied byOriginLicenseAttributionRedistributable
current_nameDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
aliases[0]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
location.cityDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
location.countyDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
location.city_keyDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
location.stateDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
location.cbsaDataCenterData reviewed record coreweave-hammonddcd originalCC-BY-4.0DataCenterDatayes
location.cbsa_nameDataCenterData reviewed record coreweave-hammonddcd originalCC-BY-4.0DataCenterDatayes
location.latCompute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
location.lonCompute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
location.source_precisionCompute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
presences[0]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
presences[1]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
operator_of_recordDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
status_by_layer[0]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
status_by_layer[1]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
lifecycle_statusDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
status_basisDataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[0]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[1]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[2]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[3]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[4]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[5]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano
layer_values[6]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
layer_values[7]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
layer_values[8]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
layer_values[9]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
layer_values[10]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
layer_values[11]Compute Atlas licensed discovery row dcd-dir-000337compute atlasCC-BY-4.0Compute-infrastructure data from Compute Atlas by Edward Kubiakyes
reviewed_unknown_statements[0]DataCenterData reviewed record coreweave-hammonddcd reference onlyreference onlyDataCenterDatano