Shooting Targets Councilman, Raises Data-Center Backlash Fears

Early in April 2026, Indianapolis City-County Councilor Ron Gibson returned home to find 13 bullets had been fired into his front door and a handwritten note that read “NO DATA CENTERS.” Gibson, who had spoken in favor of rezoning to permit a data-center project in his district, described the event as “deeply unsettling,” noting the shots struck just steps from his dining room table where his son had been playing. No injuries were reported. Indianapolis Metropolitan Police Department officers found evidence of gunfire and have characterized the episode as an isolated, targeted incident; local reporting indicates the FBI is also investigating.

Data centers increasingly function as visible proxies for the public’s anxiety about AI — both the economic disruption AI is perceived to bring and the environmental and utility impacts large facilities can impose. A security-focused Soufan Center analysis, cited in reporting, documents a recent spike in opposition activity around data-center projects nationwide. Several incidents in the past year illustrate how local hearings and online campaigns have escalated: in California, developers reported coordinated online threats tied to a data-center proposal, and a December town-hall in Port Washington, Wisconsin, ended in arrests after protesters disrupted a hearing.

Key facts from reporting: The handwritten “NO DATA CENTERS” message links the shooting explicitly to the project Gibson supported; the Metropolitan Development Commission recently voted to allow rezoning for that project. Local outlets (NBC, CBS, PBS, Fox59, Fortune, People, New York Times) confirm the core facts: 13 shots, the note, no injuries, law-enforcement and federal investigation. City leadership has expressed alarm; Council President Maggie Lewis and local officials are monitoring the probe.

This incident reframes data-center siting as not only an economic and environmental consideration but also a security concern that can directly affect elected officials, permitting timelines, and on-the-ground operations. Organizations planning AI infrastructure must treat community opposition as a multi-dimensional risk: reputational, regulatory, and physical. Companies should expect more stringent contractor and staff safety planning, potential delays from contested zoning votes, and increased costs for security and community relations. For ML engineers and ops teams, the risk translates to potential interruptions in buildouts, delays in capacity expansion, and heightened scrutiny from local regulators concerned about public safety.

Developers should coordinate with local law enforcement and federal agencies when threats are credible, accelerate community-engagement programs centered on transparent utility, environmental, and economic data, and prepare contingency plans for phased deployments if permitting becomes contested. Legal and security teams must document online threats and escalate coordinated harassment to relevant investigative bodies. Public-sector practitioners should expect calls for moratoria or stricter local controls on data-center approvals in jurisdictions where opposition is mounting.

the outcome of the FBI and IMPD investigations; any arrests or identified organizers; statements from the data-center developer in Indianapolis; whether city councils or state legislatures introduce new siting rules or mitigation requirements; and whether similar protests move from digital or procedural disruption to targeted harassment elsewhere.