Indiana research index · last changed 16 September 2026

Indiana data centers: what the public record shows.

This index separates independently source-linked campus records from separately researched physical-facility records. It preserves unknowns and duplicate-building risk so a 2 MW carrier hotel never looks equivalent to a 2 GW campus.

Two inventories · do not add them8 sourced evidence checksProject demand ≠ critical IT loadUnknown ≠ zero

Explore Indiana

Map, listings and checked facts.

Start with 40 licensed source leads, then inspect the separate public-evidence layer below. Licensed rows are not independently verified and are not a statewide census.

Indiana map

Reported locations in Indiana

40 licensed rows · 35 source localities · 5 map targets

Open interactive map
Source-reported points; some are approximate. Not parcel boundaries. Exact Approximate or representative Bounded nearby group
Browse 5 mapped areas as links
Map sources and method

The state outline is adapted from the U.S. Census Bureau 2025 cartographic boundary file. Facility coordinates are adapted from Compute Atlas by Edward Kubiak, edition 1.33.0, under CC BY 4.0. Outline and markers use one geographic projection before any explicitly disclosed readability offset. Exact singleton source anchors are never moved. A one-kilometre boundary tolerance prevents the simplified 1:20,000,000 outline from hiding legitimate border-area source points; farther conflicts are disclosed, not clamped. DataCenterData groups source-reported city coordinates only within a bounded map radius; the outline does not validate a facility record.

40 licensed rows32 reported city labels28 eligible organization labels

Browse all 40 rows below. Licensed rows are not independently verified and remain separate from the checked public-evidence layer.

  1. source-reported cancelledCapacity not statedSource updated 13 September 2026approximate location
    View facility →dcd-dir-000025
  2. source-reported operationalPlanned 2,200 MWOperational 590 MWSource updated 16 August 2026exact location
    View facility →dcd-dir-000068

Indiana evidence at a glance

Some questions answerable

Selected public evidence, not a statewide census. Each row shows whether it is independently source-linked, attributed, or unresolved; licensed leads remain separate.

Published project / campus
9
Published facility / building
1
Attributed or unresolved rows
22
Licensed directory leads
40 not independently verified
Capacity boundary stated
9 of 36 published DataCenterData rows
Review timing
Audit through 12 September 2026 · next 12 October 2026
Known coverage gap

Both announcements were found only by following URLs in the Compute Atlas source list. The IEDC newsroom index carries no data center items and the events.in.gov search returns unrelated results, so state announcements for the other Indiana projects could not be enumerated.

Browse all 40 Indiana licensed leads → · Why these counts differ →

60large project/campus leads in CAC’s separate public statewide map
18marked withdrawn in that source—30% of its listed leads
21facility research records: 1 independently source-linked and 20 attributed or unresolved
Not establishedcomparable electric demand across reviewed records; Meta separately claims a 1 GW design with an undefined capacity boundary
The honest answer to “how many?” depends on the unit.CAC’s separate source has 60 large-campus leads; our public project table contains 9 verified project/campus records. The facility file has 21 research records, of which 16 are address-resolved verified or attributed rows, 4 remain unresolved leads and one government function has no published location. These universes overlap and must not be added.

Where the evidence points

One state. Two very different kinds of marker.

Large-project markers and physical-facility records are mapped separately. Each marker is anchored to the Census place centroid; where a place has both marker types they are separated by a few pixels, within the same county. Markers are not plotted at a parcel, and marker size never substitutes for unknown capacity.

Indiana county boundaries

County boundaries: U.S. Census Bureau TIGERweb. Place centroids: 2026 Census Gazetteer. The map does not plot parcel or street-address coordinates; published addresses remain available in the facility table.

Reviewed large projects

Primary links, field by field.

These are the reviewed project and campus records linked to operator, government, utility or municipal evidence. A reviewed source can support one field without proving every MW, job, tax or operating claim in the row.

2 operating4 under construction3 approved1 expanding
15rows shown
Project / operatorStatusDisclosed demandLocation / landUtility / ISOEvidence
operatingGov. record
Google — Fort WayneGoogle

I&M confirms the site was energized in November 2024 and Google began operation; construction continues. Project demand and acreage remain unknown pending independent support.

operatingcampus UnknownNo independently supported figure Fort WayneFort Wayne · Allen County Indiana Michigan PowerPJM
constructionCompany
Meta — LebanonMeta

Meta and IEDC reported a February 2026 groundbreaking; 1 GW is a company design claim, not measured load. IEDC describes 13 buildings, including 10 data-center buildings, across 1,500 acres.

constructioncampus 1 GWcompany design · campus scope LebanonLebanon · Boone County Wabash Valley Power Alliance / Boone REMCMISO Open full evidence ledger →
constructionGov. record
Meta — JeffersonvilleMeta

IEDC reported the approximately 700,000-square-foot campus nearing completion in February 2026. Operation is not marked delivered. The 2024 announcement describes a 619-acre site and a 2026 expected-operation target; neither establishes current operation.

constructioncampus UnknownNo independently supported figure JeffersonvilleJeffersonville · Clark County Duke Energy IndianaMISO
unknownCompany
DartPoints — Columbus expansionDartPoints

DartPoints confirms an operating Columbus facility; its current facility page lists 735 kW critical IT load and 2.5 MW utility power. Expansion demand remains unknown.

unknownAttributed · not independently counted UnknownNo independently supported figure ColumbusColumbus · Bartholomew County Duke Energy IndianaMISO
operatingGov. record
Digital Crossroad — Hammond campusDigital Crossroad

DX-1 operates at the campus. Hammond says the separate CoreWeave/Decennial development agreement expired June 30, 2026 after milestones were not met. Expansion demand remains unknown.

operatingcampus UnknownNo independently supported figure HammondHammond · Lake County NIPSCOMISO Open full evidence ledger →
expiredGov. record
CoreWeave / Digital Crossroads expansionCoreWeave

Expansion agreement expired and expansion not delivered; existing facility operating

expiredRelated project UnknownNo independently supported figure HammondHammond · Lake County Unknown Open full evidence ledger →
constructionCompany
Microsoft — La PorteMicrosoft

Microsoft reported a June 2026 groundbreaking. La Porte Common Council minutes (2 March 2026) show the council introduced and unanimously adopted Resolution R-3-2026, approving the rescission of the 2024 local Microsoft taxpayer agreement and termination of its tax abatement, and IEDC lists the state exemption as a pending offer with no executed agreement posted. Project demand and acreage remain unknown pending independent support.

constructioncampus UnknownNo independently supported figure La PorteLa Porte · LaPorte County NIPSCOMISO
approvedGov. record
Sabey — Decatur Technology ParkSabey Data Center Properties

The commission approved the rezoning-commitment and variance petitions subject to commitments. The petition describes a closed-loop air-cooled system and a commitment to pay all related costs of a proposed substation and energy infrastructure. Project demand remains unknown pending independent support.

approvedproject UnknownNo independently supported figure IndianapolisIndianapolis · Marion County AES IndianaMISO
expandingCompany
AWS — New CarlisleAmazon Web Services; New Carlisle is one site in the multi-site Project Rainier cluster

Amazon says the multi-site Project Rainier cluster is operational and New Carlisle is one site. That does not prove completion of the full campus. Project demand and acreage remain unknown pending independent support.

expandingcampus UnknownNo independently supported figure New CarlisleNew Carlisle Indiana Michigan PowerPJM Open full evidence ledger →
constructionInstitution
DC BLOX ThunderbirdDC BLOX; phase-two use not defined

Conditional local approval recorded; judicial review reported

constructionAttributed · not independently counted UnknownNo independently supported figure IndianapolisIndianapolis · Marion County Unknown
approvedGov. record
Amazon Data Services — Hobart projectAmazon Data Services, Inc.

Hobart approved local agreements for Amazon Data Services, Inc.; IDEM's application describes two proposed sites. The agreements explicitly do not compel construction, investment or jobs, so approval is not described as construction.

approvedproject UnknownNo independently supported figure HobartHobart · Lake County Unknown
approvedGov. record
Amazon / NIPSCO northern Indiana service program

This is a contract/program ledger, not an additional physical campus. It exists to prevent 2,400 MW, 3,000 MW generation and water-agreement facts from being misassigned to Hobart, New Carlisle or Wheatfield.

approvedproject 2.4 GWutility service · full buildout scope UnknownLocation not published NIPSCOMISO
proposedGov. record
Project Louie — Woodland Caribou LLC (Google-associated)

The notice reports 627 linear feet of stream impact while the application reports 691 feet; both report 0.05 acre of wetland impact. The discrepancy is preserved.

proposedcampus UnknownNo independently supported figure MooresvilleMooresville · Morgan County AES IndianaMISO
proposedGov. record
Amazon Hobart — SBN520Amazon Data Services, Inc.

Child of the Hobart parent project; excluded from parent-level counts.

proposedRelated project UnknownNo independently supported figure HobartHobart · Lake County UnknownMISO
proposedGov. record
Amazon Hobart — SBN750Amazon Data Services, Inc.

Child of the Hobart parent project; excluded from parent-level counts.

proposedRelated project UnknownNo independently supported figure HobartHobart · Lake County UnknownMISO

Coverage: 9 verified project/campus records; 1 disclosed design figure; 0 eligible for aggregation. The complete CAC-derived row set is withheld pending permission or independent reconstruction. Review CAC’s source map →

Why reconciliation matters

Operating facility, expired expansion agreement.

At Digital Crossroad in Hammond, the existing DX-1 physical facility operates. But the city says the separate CoreWeave/Decennial expansion agreement expired after required milestones were not met.

ObservedDX-1 operating

Digital Crossroad markets a 105,000-square-foot physical facility at the site that it says supports up to 20 MW.

Operator evidence ↗
Promised expansionAgreement expired

Hammond says milestones were not satisfied by June 30, 2026 and no further extension would be offered.

City evidence ↗

Sourced claims and inferences

Indiana’s numbers need a unit, a date and a source.

Each card tests exact wording or explicitly labels a common inference. A verdict applies only to the claim shown. “Unknown,” “not yet due,” and “not delivered” remain different findings.

A verdict applies only to the wording shown.

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

Statewide count · IN

Contradicted

Common reading; no one is quoted

Checked 10 September 2026

Treating CAC's queue of roughly 60 proposed hyperscale projects as 60 operating physical buildings.

What the evidence supports

Citizens Action Coalition says approximately 60 large hyperscale data centers were proposed over two years and that only several are operating. Its public index is a useful proposal-discovery queue, including 18 entries it labels withdrawn—not a verified count of operating physical buildings. DataCenterData cites the queue but does not adopt it as a statewide facility total.

Still unknown

Independently reconstructed statewide operating-facility count.

Confidence: medium — Institution; Institution · 1 sources

Open full claim →

Project status · IN · aws-new-carlisle

Unknown

Common reading; no one is quoted

Checked 12 September 2026

Treating AWS Project Rainier's operation as proof that the full New Carlisle campus is complete.

What the evidence supports

Amazon says its multi-site Project Rainier compute cluster is operational and identifies New Carlisle as one site. That supports an operating milestone, not completion of every planned New Carlisle building or the full announced investment scope.

Still unknown

The remaining New Carlisle building count, buildout schedule and full-campus completion milestone are not established in the reviewed source.

Confidence: medium — Company; Institution · 1 sources

Open full claim → History (2) →

Power / timing · IN · meta-lebanon

Contradicted

Common reading; no one is quoted

Checked 11 September 2026

Reading Meta Lebanon's 1 GW design as current measured grid demand.

What the evidence supports

Meta describes a 1 GW campus and reported a February 2026 groundbreaking. The reviewed sources do not establish current metered load, a completed buildout or a comparable utility-service commitment.

Still unknown

None recorded

Confidence: medium — Company; Institution · 1 sources

Open full claim →

Water / cooling · IN · meta-lebanon

Sources re-read on 14 September 2026 (software-assisted second check, not an outside audit)

Unknown

Common reading; no one is quoted

Checked 14 September 2026

Closed-loop liquid cooling means the Meta Lebanon campus will use no water.

What the evidence supports

Meta says the design will recirculate cooling water and use zero water for a majority of the year. That is narrower than zero annual or total campus water use and remains a future design claim until operating measurements exist.

Still unknown

Actual annual withdrawal and consumption, potable and nonpotable shares, the heat-rejection architecture used in operation, and operating measurements.

Confidence: medium — Meta company design statement; no operating measurements. · 1 sources

Open full claim → History (2) →

Entity / lifecycle · IN · digital-crossroads-hammond

Contradicted

Common reading; no one is quoted

Checked 11 September 2026

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. City records identify CoreWeave as an existing tenant at the operating 100 Digital Crossroads facility. The failed expansion and existing DX-1 site are not the same lifecycle event.

Still unknown

None recorded

Confidence: medium — Gov. record; Gov. record · 2 sources

Open full claim →

Jobs / timing · IN · microsoft-la-porte

Sources re-read on 12 September 2026 (software-assisted second check, not an outside audit)

Contradicted

Common reading; no one is quoted

Checked 12 September 2026

Microsoft La Porte already has more than 600 permanent Microsoft jobs.

What the evidence supports

Microsoft's 2026 groundbreaking update projects more than 600 permanent jobs in the first phase but gives no due date for that forecast. Indiana's 2024 announcement separately projected up to 200 jobs by the end of 2032. Neither announcement establishes current employment, and the two scopes have not been reconciled.

Still unknown

Observed employment; whether the 200-by-2032 and 600+ first-phase figures describe the same scope.

Confidence: medium — Company; Gov. record · 2 sources

Open full claim → History (2) →

Jobs / unit · IN · meta-jeffersonville

Contradicted

Common reading; no one is quoted

Checked 11 September 2026

Meta Jeffersonville's hundreds of construction jobs are hundreds of permanent operating jobs.

What the evidence supports

Indiana's project announcement separates approximately 100 operational jobs from hundreds of construction jobs. Neither category is treated as observed until employment evidence and the relevant due date are established.

Still unknown

None recorded

Confidence: medium — Gov. record; Institution · 1 sources

Open full claim →

Power / cost allocation · IN · sabey-indianapolis

Partially supported

Common reading; no one is quoted

Checked 12 September 2026

One Indianapolis developer cost commitment proves no Indiana data center can affect other customers' electricity costs.

What the evidence supports

The reviewed Indianapolis filing says Sabey will pay costs related to the project's substation, generation, transmission and distribution needs. That is meaningful site-specific evidence; it does not establish every tariff, wholesale-market effect or project in Indiana.

Still unknown

Effects outside the reviewed site-specific commitment, including other tariffs, projects and wholesale-market costs, are not established here.

Confidence: medium — Gov. record; Institution · 1 sources

Open full claim → History (2) →

Open data: Indiana claim checks JSON. A correction describes the evidence boundary; it does not imply that the original speaker acted in bad faith.

Physical-facility research

Sites, leads and unresolved functions—kept separate.

This file attempts to normalize by physical address. US Signal IN01 inside Netrality’s 701 W Henry building, for example, does not create another building. Unresolved address and operator relationships remain visible instead of being promoted to verified sites.

21facility research records
16address-resolved verified or attributed rows
15.5 MWsum of operator-published critical IT load at the 6 sites that publish one—not statewide capacity
21rows shown
Facility recordLocationTypePublished capacityRecord statusSource
operatingCompany
DataBank IND1DataBank

Operating — operator marketed

IndianapolisMarion County · 731 W Henry St operating facilityColocation / carrier hotel 2.1 MWcritical it · building scope operatingaddress-resolved operating site facility source →Company
operatingCompany
DataBank IND2DataBank

Operating — operator marketed

IndianapolisMarion County · 650 W Henry St operating facilityColocation 3.75 MWcritical it · building scope operatingaddress-resolved operating site facility source →Company
operatingInstitution
Indy Telcom — 701 W HenryNetrality

US Signal IN01 and other provider presences at this address do not add another physical facility.

IndianapolisMarion County · 701 W Henry St operating facilityInterconnection / colocation Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingInstitution
Indy Telcom — 733 W HenryNetrality

Former Lifeline Data Centers Henry Street site. Netrality's December 2022 release announcing the acquisition described the 733 West Henry facility as 30,000 SF; the current operator page lists 40k sq ft of colocation. The two figures are not reconciled.

IndianapolisMarion County · 733 W Henry St operating facilityInterconnection / colocation Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingInstitution
OTAVA IndianapolisOTAVA

Operating — operator marketed

IndianapolisMarion County · 505 W Merrill St operating facilityCloud / colocation Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingInstitution
Lifeline EastgateLifeline Data Centers

Operator page also claims a 4 MW on-site solar farm; this has not been independently verified.

IndianapolisMarion County · 401 N Shadeland Ave operating facilityColocation / secure enterprise Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingInstitution
US Signal IN02US Signal

Operating — operator marketed

IndianapolisMarion County · 6325 Morenci Trail operating facilityColocation / cloud 1.6 MWcritical it · building scope operatingaddress-resolved operating site facility source →Institution
operatingCompany
Expedient IND1Expedient

Operating — operator marketed

CarmelHamilton County · 701 Congressional Blvd operating facilityColocation / cloud 4.4 MWcritical it · building scope operatingaddress-resolved operating site facility source →Company
operatingInstitution
Cogent Data Center — IndianapolisCogent Communications

Operating listing

IndianapolisMarion County · 13 S Davidson St provider presenceNetwork / colocation Capacity not public operatingaddress-resolved operating site facility source →Institution
unknownDirectory
Lumen Indianapolis 1Lumen

Listed in a petitioner's case exhibit that cites a commercial directory; current service scope not verified

IndianapolisMarion County · 1902 S East St operating facilityNetwork / data center Capacity not public unknownunresolved lead Petitioner appendix, cases 2025-CAP-856 / 2025-CVR-856 →Directory
unknownDirectory
Lumen Indianapolis 2Lumen

Listed in a petitioner's case exhibit that cites a commercial directory; current service scope not verified

IndianapolisMarion County · 4625 W 86th St operating facilityNetwork / data center Capacity not public unknownunresolved lead Petitioner appendix, cases 2025-CAP-856 / 2025-CVR-856 →Directory
operatingCompany
DartPoints CLU01DartPoints

Operator lists 2.5 MW utility power separately from 735 kW critical IT load.

ColumbusBartholomew County · 2425 Technology Blvd operating facilityColocation / cloud 0.735 MWcritical it · building scope operatingaddress-resolved operating site facility source →Company
operatingInstitution
Lifeline Fort WayneLifeline Data Centers

Operating — operator marketed

Fort WayneAllen County · 7601 S Anthony Blvd operating facilityColocation / secure enterprise Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingCompany
Digital Crossroad DX-1Digital Crossroad

The expired 2026 CoreWeave expansion agreement does not mean this existing facility closed. The up-to-20-MW operator figure is not classified here as critical IT load.

HammondLake County · 100 Digital Crossroads Dr operating facilityWholesale colocation up to 20 MWgross facility · building scope operatingaddress-resolved operating site facility source →Company
operatingInstitution
1547 SBIN1 / Union Station1547 Critical Systems Realty

US Signal IN03 is a provider presence at this address and is not counted as another physical facility.

South Bend506 W South St operating facilityCarrier hotel / colocation 2.9 MWcritical it · building scope operatingaddress-resolved operating site facility source →Institution
operatingInstitution
HostColor South BendHostColor

HostColor and Colostore listings may refer to the same address. Counted once pending entity resolution.

South Bend746 S Arnold St operating facilityHosting / colocation Capacity not public operatingunresolved lead facility source →Institution
operatingGov. record
Aunalytics data infrastructure campusAunalytics

A 2024 development agreement described an expansion of data infrastructure; current capacity is not public.

South Bend1440 Ignition Dr S operating facilityEnterprise cloud / data infrastructure Capacity not public operatingaddress-resolved operating site facility source →Gov. record
operatingInstitution
ORI.NET NoblesvilleOn-Ramp Indiana

Provider-operating; physical facility scope needs confirmation

NoblesvilleHamilton County · 518 Herriman Ct operating facilityISP / colocation Capacity not public operatingunresolved lead facility source →Institution
operatingInstitution
Indiana University Bloomington Data CenterIndiana University

Operating — institution confirmed

BloomingtonMonroe County · 2750 E Discovery Pkwy operating facilityInstitutional / research Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingInstitution
IU Indianapolis ICTC Data CenterIndiana University

Operating — institution confirmed

IndianapolisMarion County · 535 W Michigan St operating facilityInstitutional / research Capacity not public operatingaddress-resolved operating site facility source →Institution
operatingGov. record
Indiana Office of Technology data centerState of Indiana

The state services catalog says this facility houses two mainframes supporting state government, Indianapolis and Ball State University.

UnknownLocation not published operating facilityGovernment Capacity not public operatinglocation-unresolved government function facility source →Gov. record

A public operating-facility census can never prove the absence of undisclosed private server rooms. Telecom central offices are excluded unless a source specifically identifies data-center or colocation service.

What the numbers say now

Indiana’s risk is concentrated in the tail.

The public concern is not the existence of ordinary server facilities. It is the small number of very large projects whose full-buildout power demand can reshape utility planning, land use and incentive exposure.

1

reviewed 1 GW+ record

A company-announced design claim—not measured load and not necessarily full buildout.

17

CAC-listed non-withdrawn leads tied to NIPSCO

An attributed source aggregate, not 17 independently verified projects.

31

counties in CAC’s public source

An attributed orientation statistic; independent county-by-county reconstruction is still underway.

0

fully reconciled permanent-job outcomes

This is not a finding of zero jobs. It means announced jobs have not yet been joined to observed employment records across the reviewed Indiana rows.

Most important missing dataContracted versus merely requested megawatts; building-by-building energization; measured water and source-water mix; incentives actually claimed; annual local tax and impact-payment receipts; permanent employees and contractors; and deadlines for every written commitment.

Where the records were checked

Statewide audit pending

Enough to answer questions

This is still not a list of every data center in the state.

Statewide coverage is not complete. The records below are sourced; a full statewide count has not been published.

State research audit window ended 12 September 2026. Individual records and claims below show their own evidence dates and may be newer.

Next scheduled review: 12 October 2026.

9 independently source-linked project/campus records; 1 independently source-linked facility/building record; 22 attributed or unresolved rows. These counts use different units and must not be added together.

Source families checked, selected records and remaining gaps

These notes name selected records, say which kinds of public evidence were checked and show what remains missing. They do not add anything to the published counts.

  • economic development incentives — Partly checked
    • Both announcements were found only by following URLs in the Compute Atlas source list. The IEDC newsroom index carries no data center items and the events.in.gov search returns unrelated results, so state announcements for the other Indiana projects could not be enumerated.
    • the current review did not include a broad discovery sweep for Indiana work, so no keyword search could be run to locate further state announcements, incentive award records or IEDC board resolutions.
    • No IEDC incentive agreement, board resolution or transparency-portal record was retrieved, so the exemption terms recorded here come from announcements rather than from an agreement.
    • Indiana's data center sales tax exemption certifications are not published in a list that was reachable in the current review.

    Selected records

  • utility commission large load — Partly checked
    • The IURC Electronic Document System is a JavaScript Power Pages application that renders no results without scripting, so Indiana cause numbers could not be enumerated and no other docket was identified.
    • Only one document from Cause 46394 could be addressed, because document URLs embed per-document SharePoint GUIDs that cannot be derived. AES Indiana's own project-specific testimony in that cause, which would name the customer, was not retrieved.
    • No large-load tariff, electric service agreement or interconnection record was read for NIPSCO, Indiana Michigan Power, Duke Energy Indiana, Hoosier Energy, IMPA or any REMC, so the utility side of the AWS New Carlisle, AWS Hobart, AWS Wheatfield, Meta Lebanon, Meta Jeffersonville, Microsoft La Porte and Fluidstack Sullivan County projects is entirely unexamined.
    • No MISO or PJM large-load queue record was consulted.

    Selected records

  • environmental construction permits — Partly checked
    • No Indiana air, water, wetland or stormwater permit number appears anywhere in the current research record, because none of IDEM's permit systems could be queried without using the interactive website.
    • The IDEM wetland-impact letter reported to have halted some work at the AWS New Carlisle site was not retrieved and is not recorded as evidence.
    • No county or municipal building, grading or generator permit record was retrieved for any Indiana research lead.
    • Water withdrawal registrations with the Indiana Department of Natural Resources, which would bear on several of these campuses, were not searched.

    Selected records

  • municipal planning assessor gis — Partly checked
    • Not a single Indiana assessor or parcel record naming a data center owner was obtained. Every Indiana research lead lacks a parcel identifier.
    • Marion County's assessor GIS requires authenticated access, so the Sabey, DC BLOX and Metrobloks Indianapolis sites have no parcel evidence.
    • Morgan County and St. Joseph County could not be retrieved during review, blocking the Monrovia, New Carlisle and Granger records.
    • No plan commission, board of zoning appeals or county council minutes document was retrieved for any Indiana jurisdiction, so every rezoning, approval and denial in the current research record rests on the licensed dataset or on news reports.
    • Beacon/Schneider parcel portals, which many Indiana counties use, are interactive and were not attempted.

    Selected records

  • tax abatement development agreements — Partly checked
    • No executed agreement document was retrieved anywhere in Indiana. No economic revitalization area designation, personal-property or real-property tax abatement resolution, CF-1 compliance form, TIF allocation-area ordinance or development agreement was read.
    • The Hammond common council records behind the canonical CoreWeave/Digital Crossroads expansion approval and expiration were not reached, which is why that lifecycle conflict is unresolved.
    • Indiana's DLGF abatement filings (forms SB-1 and CF-1), which are county-level public records, were not searched.
    • The City of Shelbyville permit item refused the connection and did not respond during review on retry.

    Selected records

  • operator disclosures — Partly checked
    • Without a broad discovery sweep in the current review, operator location pages could not be located by keyword and had to be guessed; the one Sabey URL tried returned unavailable during review.
    • No hyperscaler location page (Amazon, Google, Meta, Microsoft) was read for Indiana, so no operator-stated capacity, square footage or facility designation is recorded for the four largest Indiana operators.
    • Colocation operators in the reviewed Indiana facility records — DataBank, Netrality/Indy Telcom, OTAVA, Lifeline, US Signal, Expedient, Cogent, Lumen, DartPoints, 1547, HostColor, Aunalytics and ORI.NET — were not checked at all, so the current research record adds nothing to the canonical colocation coverage.

    Selected records

  • open datasets directories — Checked
    • No unlicensed directory (Data Center Map, Baxtel, datacenters.com, Cloudscene, PeeringDB) was consulted, so provider presence and colocation coverage is absent.
    • The extract contains no record for most of the colocation facilities in the reviewed Indiana facility records, so the current research record cannot speak to whether those canonical records are current.
    • Compute Atlas source URLs that were not followed include most of the press items; only the government-hosted ones and three news or advocacy items were opened.

    Selected records

  • historical closures withdrawals names — Partly checked
    • No primary record of any Indiana cancellation, denial or withdrawal was obtained. The Clinton County and Hancock County records are news reports, and the county sites behind them were not reached.
    • No rezoning case number, ordinance number or resolution number is recorded for any Indiana lifecycle event, because none appeared in a source that could be read.
    • No corporate filing or Secretary of State record was used, so the entity names Logix Reality LLC, Surge Development LLC, Jumping Bison LLC and QLEVR LLC are recorded only as the dataset and press reported them.
    • Renames and acquisitions in Indiana's colocation market (for example the DataBank and Lifeline histories behind the reviewed Indiana records) were not searched at all.
    • Archived versions of operator and municipal pages were not consulted.

    Selected records

  • news and other discovery — Partly checked
    • the current review did not include a broad discovery sweep for Indiana work, so no news sweep was possible and every news item in the current research record was reached through a URL in the Compute Atlas source list.
    • Local reporting on the Hobart, Wheatfield, Michigan City, Granger, Merom, Pittsboro, Merrillville and Bristol proposals was not read.

    Selected records