Mike Hammett

How things actually work.

Tag: Data Centers

  • How I Checked Erin Brockovich’s Community-Report Map

    How I Checked Erin Brockovich’s Community-Report Map

    I’m CTO of DNA Communications and co-founder of FD-IX, an internet exchange. I have no financial interest in any data center project. This piece documents the map analysis in “What Erin Brockovich Gets Right, and Wrong, About AI Data Centers.”

    TL;DR

    • The analysis uses only Brockovich’s own published files: her community reports, her list of facilities, and her zip-code coordinates, as archived on October 10, 2026 [1][2][3].
    • 482 of her 9,683 reports through October 4, 2026, 5.0%, carry a zip code within 10 miles of at least one operating facility on her list and no listed project that isn’t operating. If cancelled projects don’t count, the figure is 510, 5.3%. A wider count, 1,084 reports or 11.2%, sits within 10 miles of an operating facility regardless of what else is nearby.
    • Across every radius from 1 to 30 miles, that share stays between 1.2% and 5.4%; below about 3 miles, the zip-code points are too coarse to mean much.
    • Averaged by status, operating campuses have 14.2 reports within 10 miles, proposed projects 14.3, and campuses under construction 17.9. Medians are 11, 8, and 13.
    • The code below reruns every figure against the archived files.

    The inputs

    Her map page loads three files from her site: community-reports.json, data-centers-map.json, and zip-geocodes.json. I confirmed that from the page’s own network requests on October 29, 2026.

    The community reports file holds one record per report, with six fields: date, city and state, zip code, type, owner, and notes [1]. The archived copy holds 9,683 records, dated June 23, 2024 through October 4, 2026, and every date is in year-month-day form. The type field names the kind of facility, not the complaint: 9,661 records say data center, 18 say battery storage, and 4 are blank. Her stats page for that date shows the same total, 9,683, with data through October 4, 2026 [5].

    The facility file lists 545 projects, each with a status and coordinates [2]. Its header says it was updated September 27, 2026, gives the counts by status (139 operational, 166 under construction, 39 permitted, 175 proposed, 26 cancelled), and names Compute Atlas and Epoch AI as its sources [2]. Her home page describes the list’s scope: the pins cover “publicly announced, major AI-focused and hyperscale facilities,” and “many smaller or unannounced facilities are not listed” [4].

    The zip-code file gives one latitude and longitude for each zip code it covers, 2,465 of them in the archived copy [3]. The file doesn’t document how its maker chose each point, so I call it the zip code’s coordinate rather than its center.

    The live reports file keeps growing. On October 29, 2026, it held 9,733 records, and requests with the version tag in the address, with a different tag, and with none all returned the same file. Filtering the live file to records dated on or before October 4 still returned 9,683, and rerunning the analysis on the live files that day gave the same 1,084 and 482. That match isn’t guaranteed later: a record can be deleted or edited, and the facility file’s statuses will change as projects open. The archived copies are the versions I analyzed, and the code below reads them.

    FileArchived copyBytes
    community-reports.json[1]1,403,943
    data-centers-map.json[2]760,276
    zip-geocodes.json[3]142,877

    Their SHA-256 hashes, in sha256sum format:

    51859eb219c6fa7c28db5421cd7129dac934650570e154968e793344dea75163  community-reports.json
    c039d8f64fede66d9788ba3b7ccc00db832f7e8cbcecc15d1d3653a8d6047b40  data-centers-map.json
    584fc354c560544e50d9194952b0d8aa1e573d31e52a3e5e4012f03bee5a3f5c  zip-geocodes.json
    

    The method

    The method sorts reports by how close their zip code sits to each facility on her list. For each report, I took its zip code’s coordinate and measured the straight-line distance to every facility, using the haversine formula with an Earth radius of 3,958.8 miles. A report counts as near a facility when that distance is 10 miles or less.

    Each report goes into one bucket, the most advanced project nearby: operating first, then under construction, then permitted, proposed, or cancelled. Reports with nothing within 10 miles go into a “none” bucket. Five reports have no usable zip code: four are blank, and one, 76000, isn’t in the zip-code file.

    The operating-only test then takes the reports near an operating facility and keeps those with no listed project of another status within 10 miles, cancelled projects included. A report near two operating facilities and nothing else stays in. It doesn’t depend on the bucket order: a report near an operating facility lands in the operating bucket whatever else is nearby, and the test then looks at every non-operating project on the list.

    The density check counts, for each facility, every report within 10 miles of it, then gives the mean and median by status. Density counts aren’t exclusive, so one report can count toward several facilities.

    Statuses come from the September 27 file, not from the date of each report. A report filed while a nearby project was still proposed counts as near an operating facility if that project had opened by September 27, so some reports in the operating group were filed before the facility ran.

    The results

    Bucket (10 miles)ReportsShare
    Near an operating facility1,08411.2%
    Near a campus under construction, no operating one2,00020.7%
    Near only proposed, permitted, or cancelled projects2,37424.5%
    Near nothing on her list4,22043.6%
    No usable zip code50.05%

    482 reports, 5.0% of 9,683, sit near an operating facility and no listed project of another status. They come from 128 zip codes. 333 are near exactly one operating facility; 149 are near two or more. The other 602 of the 1,084 reports near an operating facility are also within 10 miles of a project that isn’t operating; 28 of those are near only a cancelled one. If cancelled projects don’t count, the operating-only count is 510, 5.3%. Measured against the 5,458 reports within 10 miles of anything on her list, rather than all 9,683, 482 is 8.8%.

    StatusFacilitiesReports within 10 miles (non-exclusive)MeanMedianFacilities with none
    Operational1391,97414.2117
    Under construction1662,96717.9139
    Proposed1752,49914.3821
    Permitted3978320.1162
    Cancelled2637814.593

    72 of the 139 operating campuses have no listed project of another status within 10 miles of the campus itself; 510 distinct reports sit within 10 miles of at least one of them. That isn’t the same group as the 482. The operating-only test looks at what is within 10 miles of each report; this count looks at what is within 10 miles of each campus. 441 reports are in both. The other 69 of the 510 are near one of those campuses and also near a non-operating project that is more than 10 miles from the campus. The other 41 of the 482 are near only operating campuses that each have a non-operating project within 10 miles of the campus but not of the report. That the 510 equals the operating-only count without cancelled projects is a coincidence. Only 40 operating campuses have no other listed facility of any status within 10 miles, and 330 distinct reports sit near those.

    At 25 miles, the buckets shift to 2,312 near an operating facility, 4,800 near only other listed projects, and 2,566 near nothing on the list.

    What the numbers do and don’t show

    The numbers rest on two things the files don’t document: how each zip code’s point was chosen, and whether a report’s zip code is the reporter’s or the reported site’s. Her form asks for both the reporter’s address and the “AI Data Center Location You Are Reporting” [4]. If the zip is the reported site’s, distance roughly says which project a report is about; if it’s the reporter’s, it says how far the reporter lives from the nearest listed project. The file can’t settle which. Proximity says nothing about which facility a report concerns or what prompted it, and the 5% is a share of submitted reports. A rate of filing would need the population inside each circle, which her files don’t carry and I didn’t compute.

    Counted by bucket, more reports sit near projects that aren’t operating, 4,374 or 45.2%, than near operating facilities, 1,084 or 11.2%. Another 4,220, 43.6%, sit near nothing on her list. Counted per facility, operating campuses average 14.2 reports within 10 miles, the same as proposed projects at 14.3, with a higher median, 11 against 8. The operating-only test removes 602 of the 1,084 reports near operating facilities because a non-operating project is also within 10 miles; 67 of the 139 operating campuses have one.

    The bucket labels can also mislead in the other direction. Ahwatukee, in Phoenix, zip code 85044, has 18 reports in the operating-only group because Digital Realty’s operating PHX15 is within 10 miles. One of them, dated April 6, 2026, names Menlo Equities as the owner and describes “a million square foot AI center” less than half a mile from the writer’s house. Five others carry only the note “pics,” and 12 have no owner or note. Menlo Digital’s 38-acre Ahwatukee data center has been under construction since April 2026 [6], and it isn’t on her list within 10 miles of that zip code. The April 6 report is about that construction site, and the test files it as operating-only. The other 17 say nothing about which facility they concern, so neither the test nor I can place them.

    A zip code’s coordinate can sit miles from a rural reporter’s home, and the size and direction of that error vary from place to place. Her list covers major AI and hyperscale facilities and leaves out many smaller ones [4], so “near nothing” means only that no listed facility is within 10 miles. The omitted facilities skew older, smaller, and already running, so their absence pushes the operating-only share down. A share of submitted reports also can’t count neighbors of a running facility who have never heard of her map. Reports also track approval fights: neighbors organize when a project is proposed, so a map built from voluntary submissions will cluster around proposals, whatever happens after a facility opens. The test measures distance only. It doesn’t measure noise, light, wells, water supply, or electricity costs.

    Across every whole-mile radius from 1 to 30 miles, the operating-only share runs from 1.2% at 1 mile to a peak of 5.3% at 6 miles, or 5.4% if cancelled projects don’t count, then mostly falls as wider circles catch more new projects. Below about 3 miles, the circles get smaller than many zip codes, so a report’s assigned point may say little about where the reporter or the site is; I’d give those radii little weight. At 5 miles, it’s 442 reports, 4.6%. At 10 miles, it’s 482, 5.0%. At 25 miles, it’s 211, 2.2%.

    The code

    The code is here so anyone can check the numbers. One block of JavaScript reproduces every figure above from the three archived files [1][2][3]. Read it before you run it: it only downloads those three files and counts. Open any page on web.archive.org, for example, the archived stats page [5], open the browser’s developer console, and paste it. Your browser may ask you to type a confirmation before it accepts pasted code; that warning is there for good reason, so run only code you’ve read. Change RADIUS to rerun at another distance, and set CANCELLED_COUNTS to false to leave cancelled projects out of the operating-only test.

    // Settings. RADIUS is in miles. CANCELLED_COUNTS: true counts a cancelled project as a non-operating project nearby.
    const RADIUS = 10, CANCELLED_COUNTS = true;
    // Archived inputs (October 10, 2026 captures). To use her live files instead, run on brockovichdatacenter.com
    // and set FILES to ['/community-reports.json', '/data-centers-map.json', '/zip-geocodes.json'].
    const FILES = [
      '/web/20261010001606id_/https://www.brockovichdatacenter.com/community-reports.json?v=20261004',
      '/web/20261010001606id_/https://www.brockovichdatacenter.com/data-centers-map.json?v=20260927',
      '/web/20261010001607id_/https://www.brockovichdatacenter.com/zip-geocodes.json?v=20260927'];
    const [all, fj, g] = await Promise.all(FILES.map(u => fetch(u, {cache: 'no-store'}).then(r => r.json())));
    const reps = (Array.isArray(all) ? all : Object.values(all).find(Array.isArray))
      .filter(r => (r.date || '') <= '2026-10-04');
    const fac = fj.fac;
    const R = 3958.8, rad = x => x * Math.PI / 180;
    const hv = (a, b, c, d) => { const dl = rad(c - a), dn = rad(d - b);
      const h = Math.sin(dl / 2) ** 2 + Math.cos(rad(a)) * Math.cos(rad(c)) * Math.sin(dn / 2) ** 2;
      return 2 * R * Math.asin(Math.sqrt(h)); };
    const near = (p, f) => hv(p.lat, p.lng ?? p.lon, f.lat, f.lon) <= RADIUS;
    const order = ['operational', 'under_construction', 'permitted', 'proposed', 'cancelled'];
    const nonOp = f => f.s !== 'operational' && (CANCELLED_COUNTS || f.s !== 'cancelled');
    const buckets = {}; let noZip = 0, opOnly = 0, opAndNonOp = 0, opOnlyMulti = 0;
    for (const r of reps) {
      const z = g[r.zip]; if (!z) { noZip++; continue; }
      const b = order.find(s => fac.some(f => f.s === s && near(z, f))) || 'none';
      buckets[b] = (buckets[b] || 0) + 1;
      if (b !== 'operational') continue;
      if (fac.some(f => nonOp(f) && near(z, f))) { opAndNonOp++; continue; }
      opOnly++; if (fac.filter(f => f.s === 'operational' && near(z, f)).length > 1) opOnlyMulti++;
    }
    const zc = {}; reps.forEach(r => { if (g[r.zip]) zc[r.zip] = (zc[r.zip] || 0) + 1; });
    const within = f => Object.keys(zc).reduce((n, z) => n + (near(g[z], f) ? zc[z] : 0), 0);
    const distinct = list => Object.keys(zc).reduce((n, z) => n + (list.some(f => near(g[z], f)) ? zc[z] : 0), 0);
    const perStatus = {};
    for (const f of fac) { const p = perStatus[f.s] ??= {facilities: 0, reports: 0, counts: []};
      const n = within(f); p.facilities++; p.reports += n; p.counts.push(n); }
    for (const s in perStatus) { const c = perStatus[s].counts.sort((a, b) => a - b);
      perStatus[s] = {facilities: c.length, reportsNonExclusive: perStatus[s].reports,
        mean: +(perStatus[s].reports / c.length).toFixed(1), median: c[Math.floor(c.length / 2)],
        withNone: c.filter(x => x === 0).length}; }
    const op = fac.filter(f => f.s === 'operational');
    const noNonOpNearby = op.filter(f => !fac.some(o => nonOp(o) && near(f, o)));
    const nothingNearby = op.filter(f => !fac.some(o => o !== f && near(f, o)));
    ({reports: reps.length, noZip, buckets, opAndNonOp, opOnly, opOnlyNearTwoOrMoreOperating: opOnlyMulti,
      share: (100 * opOnly / reps.length).toFixed(2) + '%', perStatus,
      operatingWithNoNonOperatingNearby: noNonOpNearby.length, distinctReportsNearThem: distinct(noNonOpNearby),
      ofThoseAlsoOperatingOnly: Object.keys(zc).reduce((n, z) => n + (noNonOpNearby.some(f => near(g[z], f))
        && !fac.some(f => nonOp(f) && near(g[z], f)) ? zc[z] : 0), 0),
      operatingWithNothingElseNearby: nothingNearby.length, distinctReportsNearThose: distinct(nothingNearby)});
    

    On her own site, with the live file paths swapped in, the same code reads her current files. The date filter keeps the reports to the October 4 set, but the facility statuses will be whatever the file says that day.

    Closing

    Her report form already asks whether the facility is “already up and running” or under construction [4]. The published reports file doesn’t include that answer. Publishing it, or a facility identifier with each report, would let anyone separate reports about operating sites from reports about proposals without estimating from distance.


    Sources

    [1] brockovichdatacenter.com, community reports data file (community-reports.json, version October 4, 2026; analysis by the author; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/community-reports.json?v=20261004 (live: https://www.brockovichdatacenter.com/community-reports.json)

    [2] brockovichdatacenter.com, facility data file (data-centers-map.json, updated September 27, 2026; header lists counts by status and its sources; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/data-centers-map.json?v=20260927 (live: https://www.brockovichdatacenter.com/data-centers-map.json)

    [3] brockovichdatacenter.com, zip-code coordinate file (zip-geocodes.json; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001607id_/https://www.brockovichdatacenter.com/zip-geocodes.json?v=20260927 (live: https://www.brockovichdatacenter.com/zip-geocodes.json)

    [4] brockovichdatacenter.com, home page (map scope note, data sources and report form; advocacy source), archived October 20, 2026: https://web.archive.org/web/20261020235816id_/https://brockovichdatacenter.com/index.html (live: https://www.brockovichdatacenter.com/)

    [5] brockovichdatacenter.com, Community Reports Statistics (“Generated October 4, 2026 · Data through October 4, 2026”, 9,683 total reports; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001648id_/https://www.brockovichdatacenter.com/community-stats.html

    [6] Arizona’s Family (azfamily.com), How neighbors say data center construction has affected Ahwatukee community, October 28, 2026 (Menlo Digital’s 38-acre data center in Ahwatukee, under construction since April): https://www.azfamily.com/2026/10/29/how-neighbors-say-data-center-construction-has-affected-ahwatukee-community/

  • What Erin Brockovich Gets Right, and Wrong, About AI Data Centers

    What Erin Brockovich Gets Right, and Wrong, About AI Data Centers

    I’m CTO of DNA Communications and co-founder of FD-IX, an internet exchange, with roughly 20 years in ISP and network infrastructure in Northern Illinois. I have no financial interest in any data center project.

    TL;DR

    • Brockovich’s map headline number, 9,683 reports as of October 4, is not a count of data centers. Her own vetted list holds 545 projects, only 139 of them operating. 80.5% of the published report records carry no owner or note, only a date, a location, and a facility type, and her largest hotspot, 402 reports, is a project with no building and no committed developer.
    • 1,084 reports, 11.2%, come from zip codes within 10 miles of an operating facility on her list, and 482, 5.0%, from near one with no listed project nearby that isn’t operating. 20.7% sit near a campus under construction. Her list leaves out most conventional data centers, and distance can’t say which facility a report is about. Counted per facility, operating campuses average about as many nearby reports as proposed projects.
    • Of the operating facilities discussed in this piece, four show documented harm, all of it noise, on different kinds of evidence. An Oregon nitrate settlement came with denied liability and a causal share no one has established. The largest open case, xAI’s gas turbines powering its Memphis-area AI campus, is in court: a judge has ruled the turbine plant wasn’t exempt from air permits, and no remedy or penalty has been decided. Much of the rest is construction-phase risk common to any large project, or concern about facilities not yet built.
    • She told Bill Maher an average golf course uses 500 million gallons a year. By my calculation from the Golf Course Superintendents Association of America (GCSAA) national survey, the mean is at most about 38 million per facility, so she was off by at least 13x. Her figure for the largest campuses, up to 1.5 billion gallons a year, is accurate, even conservative: Google’s biggest site withdrew 1.75 billion in 2025. Cooling water use can be zero: Microsoft’s new designs use none.
    • Nondisclosure agreements (NDAs) during site selection are real and documented: researchers found them in 25 of 31 Virginia localities with data center activity, and a Houston economic development official said virtually every company scouting that region seeks confidentiality.
    • Her own site corrects two exaggerations popular with data center opponents, calling the claim that a ChatGPT query uses ten times the energy of a Google search “outdated” and “AI will collapse the power grid” an overstatement. It labels the industry’s 100% renewable claim nuanced. Her farmland and drought claims are accurate.

    How this was checked, and what it doesn’t cover

    This piece checks three sources: Brockovich’s July 31, 2026 appearance on HBO’s Real Time with Bill Maher [1], her site brockovichdatacenter.com, and her other public statements where they surfaced in national coverage. I treat government records, peer-reviewed research, and court rulings as authoritative. A court filing tells you what someone alleges, not what happened. I use secondary sources to locate primaries and label them where they’re all I found. I use her site’s figures as of its October 4, 2026, update and cite archived copies, because the live pages keep changing [2]. Where the July 30 snapshot that prompted this piece differs, I give both.

    I checked the locations that surfaced through national coverage and her own top-reported-cities list. That sample skews toward whatever is most newsworthy. It is not a census of every operating facility in the country. When I say I didn’t find something, I mean I didn’t find it in what I checked.

    What Brockovich gets right

    Brockovich’s “Facts vs. Myths” page corrects two claims popular with data center opponents and treats an industry claim more fairly than opponents usually do [3]. It labels the viral claim that a ChatGPT query uses ten times the energy of a Google search “outdated,” citing a reassessment that puts a typical query in the same range as older search estimates [4]. It calls “AI will collapse the power grid” an overstatement. It marks the claim that data centers run on 100% renewable energy as nuanced rather than false, since renewable energy credit accounting makes it technically true, and explains what that accounting doesn’t guarantee. It gives closed-loop cooling a fair hearing. Asked on the same page whether data centers bring real jobs and tax revenue, she acknowledges the tax revenue and construction jobs and notes that a large facility may employ only 20 to 50 full-time workers [3]. Elsewhere she has said plainly that she isn’t “making a blanket argument against data centers”; her target is projects announced after permits are secured and NDAs signed before residents hear about them [5].

    On air, she gave Maher the same courtesy. When he raised golf and almond irrigation as bigger water users, she said the comparison holds for small and medium-sized facilities, called it “great question, good argument,” and narrowed her case to the largest campuses [1]. Her bipartisan claim checks out: Oklahoma’s Data Center Customer Ratepayer Protection Act carried 36 co-authors from both parties and a Republican governor’s signature [6], and her legislation tracker, which cites a named source for every entry, shows comparable bills in Florida and South Dakota alongside New York, Maryland, and Washington [7]. Her Noise Impact Simulation labels itself an illustrative model, not measured data, and its advice to residents is sound: ask for an independent acoustic study, ask about low-frequency noise below 200 Hz, and insist on measurements at the property line [8]. Her News page’s claim that a West Virginia flood was caused by data center construction is also substantiated: a silt-retention breach during earthwork in Mason County sent water and sediment onto nearby homes [9][10].

    Brockovich’s specific claims, checked

    Each entry leads with a verdict: Accurate, Overstated, Imprecise, or Unverified. Where a claim has two parts, each part gets its own.

    Water: Accurate on the largest campuses, Overstated on the golf baseline. Up to 1.5 billion gallons a year is a real figure for the biggest campuses. Google’s thirstiest site, Council Bluffs, Iowa, withdrew 1.75 billion gallons in 2025 and consumed 1.35 billion of it, according to Google’s own environmental report [11]. Withdrawal is what a site draws from its source. Consumption is the part that doesn’t go back, mostly lost to evaporation. A data center can use no water for cooling. Since August 2024, all new Microsoft data center designs use no water for cooling beyond filling the closed loop, though the buildings still use water for restrooms and kitchens [12]. The 1.5 billion number belongs to the largest sites, not to the industry. These are direct, on-site figures. They exclude water consumed at the power plants supplying the electricity, and a dry-cooled campus shifts some of its water footprint there by using more electricity.

    The golf baseline she used is wrong. She told Maher an average golf course uses 500 million gallons a year. GCSAA’s 2024 national survey reached 13,952 golf facilities and drew 1,766 responses. It projects national irrigation at 1.63 million acre-feet by multiplying each region’s mean use per facility by the number of facilities in that region [13][14]. The projection uses only responses based on water-meter readings [14]. Spread across the 13,952 facilities the survey reached, it works out to about 38 million gallons per facility. GCSAA doesn’t publish the facility count behind the projection, and the true count can’t be smaller than the number of facilities the survey reached, so 38 million is an upper bound on the national average. A facility can be a 9-hole course or a 36-hole club, so individual courses vary around that. Southwest courses use more than double the per-facility water of other regions [14], and even Google, when it converts its data center water into “golf course equivalents,” uses a southwestern course at about 150 million gallons a year [11]. Her 500 million is more than three times that and at least 13 times the national average. The correction helps her argument rather than hurting it. Against that average, Google’s largest campus by water use withdraws at least 46 times what a typical facility does [11]. Her version made them look comparable.

    NDAs: Accurate in substance, Overstated in scope. Confidentiality during site selection is common in corporate relocation. A Houston economic development official said virtually every company scouting the region seeks confidentiality [15]. In DeKalb, the 560-acre campus first came before the public as “Project Vector,” filed by a developer rather than the eventual operator [16]. Brockovich’s “everything, everything” claims more than the record shows. Two researchers who filed public-records requests found NDAs in 25 of 31 Virginia localities with data center activity, about 80%, and say the real figure may be higher because some governments kept no copies [17]. That documents NDAs in at least 80% of the localities they checked. The researchers couldn’t settle the rest either way. Public Citizen, an advocacy group opposed to data center NDAs, cites the same 80% from the same source [18]. The sharper complaint isn’t that NDAs exist. It’s that some keep figures out of public view that the public would normally see. In Botetourt County, Virginia, the regional water authority blacked out how much water a Google data center would use, citing an NDA, and released the figure, 2 to 8 million gallons a day, only after court rulings in a local news outlet’s favor [19]. Records for a Google project in Douglas County, Georgia came back with the water requirements redacted [20]. That’s the version of the complaint that holds up, and it’s a question to ask about any local deal.

    She has a stronger local-control example available and doesn’t use it. West Virginia’s HB 2014 exempts certified high impact data centers and microgrid districts from county and municipal zoning, noise, and lighting ordinances [21][22]. That isn’t a private agreement. It’s a state legislature removing a county’s authority over a facility inside its own borders.

    “It’s taking farmland”: Accurate. In DeKalb County, Illinois, every data center site, built or planned, was in crop production until development started. The loss is permanent. It also needs scale. The three DeKalb projects total roughly 1,200 acres, about 0.34% of the county’s 353,524 acres in farms [23]. The county lost about 5% of its farmland between 2017 and 2022 to all causes combined [23]. The newest site followed the city’s own plan: the 2022 Comprehensive Plan designates it industrial, and when the county’s enterprise zone was expanded, the Illinois Department of Agriculture found that including the property was consistent with the state’s farmland preservation policy [24]. The council then annexed and rezoned it in December 2025 [25]. Her claim is true. Whether farmland is a bigger concern for a data center than for the warehouse or factory that would otherwise sit on that edge of town is a separate question.

    “Building them on drought-restricted land… Iowa, Nebraska, Kansas”: Accurate on conditions. When she said it at the end of July, nearly 84% of Nebraska was in drought on the U.S. Drought Monitor, including areas of extreme and exceptional drought [26]. A large area of southwest Kansas was in moderate to severe drought [27]. About a third of Iowa was in moderate drought in early July, concentrated in the north and west [28]. Those are statewide and regional drought classifications, not water-use restrictions on specific parcels. Whether drought explains why particular sites were chosen is a different claim, taken up in the siting section.

    Acreage: Accurate for the largest projects, Overstated as a description of the category. Meta’s Hyperion campus in Louisiana started at 2,250 acres, and Meta bought another 1,400 at the end of 2025, about 3,650 in all [29]. The three DeKalb projects run 132, more than 500, and 560 acres [30][31][32]. Headline acreage also usually describes a project boundary rather than buildings. The Stratos project in Box Elder County, Utah, was billed at about 40,000 acres, split into three sites, with the non-data center land earmarked for uses that may include manufacturing, retail, restaurants, and hotels [33]. Utah’s governor said the first-phase permit holds the data center building footprint to under 2,000 acres, about 5% of the original total, and that later phases would need their own approval [34]. In June, the developer dropped about 20,000 acres and said the campus will likely be 10,000 acres or less [35]. When a number like 4,000 acres describes “a data center,” ask whether it’s typical, the biggest ever built, or mostly land that won’t be built on.

    “We’ve always had data centers. They’re generally smaller”: Accurate, with a caveat. Most older data centers are smaller, and the gigawatt tier is new. Big older ones exist, though. 350 East Cermak in Chicago, a 1912 R.R. Donnelley printing plant converted to telecom use in 1999, runs about 1.13 million square feet with 109 megawatts (MW) of utility power [36][37]. Edged opened the first 24 MW building of its 96 MW campus in Aurora, Illinois, in February 2025; its second building alone is rated 72 MW [38][39]. Stargate Abilene had 618 MW of computing (IT) capacity delivered across six of its eight buildings as of September 10, 2026, according to Oracle [40]. The campus is planned at 1.2 gigawatts (GW), or 1,200 MW [41], about 11 times Cermak’s utility power, and that tier is the one this debate is actually about. It didn’t appear overnight. An industry analyst firm that tracks hyperscale capacity says the average size of new data centers increased gradually for years before accelerating sharply in late 2024, and the number of hyperscale facilities reached 1,136 at the end of 2024 after doubling over five years [42]. Getting from Cermak to Abilene took steadily larger campuses, not a leap from one kind of building to another. The bigger change is architectural. Cermak is a multi-tenant building in a dense urban core, with dozens of companies running their own equipment in a retrofitted high-rise. A modern AI campus is usually one operator’s purpose-built system on open land, with room for substations and cooling plant.

    “People are losing their wells”: Accurate as a complaint, Unverified on cause. Four families near Meta’s Newton County, Georgia data center sued Meta in Gwinnett County Superior Court at the end of August [43]. Meta moved the case to federal court in Atlanta on October 16, and on October 28 the families filed an amended complaint and asked the judge to send the case back to state court [44]. Their central claim is that blasting and excavation during construction pushed sediment into the aquifer feeding their wells; the suit also alleges noise, light, and air emissions. Meta acknowledges limited blasting about 1.1 miles from one family’s property, but says a study by outside experts found the data center is “not likely to be the cause” of the well problems, that groundwater flows away from the homes, and that every gallon the facility used came from the local utility [45]. That dispute is unresolved, and its core is a construction claim, which belongs with the construction section below. Among the cases checked for this piece, none documents an operating data center drawing down neighbors’ wells.

    “I now have nine other countries reporting”: Unverified. Her FAQ and stats page describe a U.S.-only map, and neither shows any international data [46][2]. That doesn’t rule out reports she has received and not published.

    “New York has banned it”: Imprecise. Executive Order 62, signed July 14, 2026, directs the Department of Environmental Conservation to hold in abeyance discretionary permit applications for building or expanding data centers that use 50 MW or more, excluding manufacturing, research, education, and medical uses. Applications the department had already determined complete before the order are outside the hold, and it doesn’t touch local-government permits. The hold lasts until the state completes a generic environmental impact statement, with no fixed end date [47]. It’s a temporary state permitting hold, not a ban.

    “79 municipalities had moratoriums or bans” when she started: Unverified, plausible. The National League of Cities counted at least 76 local governments that had attempted a moratorium or ban when it released its tracker in August [48]. By its October 28 refresh, the tracker listed 218, counting each locality once, with 183 of them adopted or completed [49]. Her own tracker now puts local moratoriums and bans at more than 300 as of September, up from 116 in June, citing SemiAnalysis and Route Fifty [7]. The trackers use different dates and definitions, and a tracker’s count also grows as it catalogs more entries, so these figures don’t show a growth rate. 79 falling between them makes it plausible, not verified.

    Maher’s claims, checked

    Maher got one of his four checkable claims right, had the direction right on a second, was partly right on a third, and was imprecise on the fourth.

    “I don’t think it’s the land. We have the land”: Accurate. Land is not what constrains data center siting nationally. Power availability is, and CBRE calls it “the foremost site selection criterion for greenfield data center developments” [50]. Maher identified the correct binding constraint in an offhand remark.

    “Seven times the amount of water” goes to golf: Understated today. Golf’s national water use, about 531 billion gallons a year from GCSAA’s survey [13], is about 30 times data centers’ direct consumption of 66 billion liters, about 17.4 billion gallons, in 2023 [51]. LBNL’s 2028 projections, 325 to 580 TWh at a site water intensity of 0.45 to 0.48 liters per kWh, work out to roughly 39 to 74 billion gallons [51]. With golf flat or declining, the ratio falls to 7x to 14x. Maher had the direction right and lowballed today’s gap; his number describes 2028. Both comparisons use direct, on-site water only. One caveat on the accounting: GCSAA measures irrigation applied, and some of that soaks back into the ground or runs off, while LBNL’s figure is water consumed. Golf’s consumed share is smaller than its applied total, so the 30x overstates the consumptive gap by an amount neither source measures. It doesn’t close it. The totals also hide a per-unit trend both industries share. Golf’s total use fell 31% since 2005 while the number of facilities fell 14%, so use per facility fell about 20% [14]. Microsoft’s water-use effectiveness, a measure of water per unit of energy, improved 39% from 2021 to the figure it reported in December 2024, and about 80% since its first-generation facilities [12]. Those are different measures, golf per facility and Microsoft per unit of energy, but both show efficiency improving while total demand can still rise as data center computing grows.

    “Why don’t we build them in our 51st state where it’s cold?”: Partly right. Brockovich answered, “Well, absolutely” [1]. Cold climates do cut cooling load. Dry coolers work best where outside temperatures stay below about 80°F, which favors northern sites [52]. But climate doesn’t outrank power. A cold site without transmission capacity and fiber doesn’t get built [50].

    “A $500 billion data center”: Imprecise. $500 billion is the total, multi-year Stargate program across seven planned sites [41]. The flagship Abilene site sits on just over 1,000 acres [53]. Its developers formed a $15 billion joint venture to finance the eight-building, 1.2 GW campus [54], and Oracle is reportedly set to spend about $40 billion on Nvidia chips for it [55]. No total cost for the site is published, but those two figures together are about a ninth of the headline number.

    Maher also asked the sharpest question of the segment. After she said New York had banned data centers, he asked whether New Yorkers would still use what data centers produce: “Everybody’s a hypocrite. Oh, we can’t have it, but I will use it.” She answered “Well, yes,” pivoted to where data centers should go, and he didn’t press [1].

    The map: what’s checked, and what just has a zip code

    Brockovich’s map layers two kinds of data: a vetted list of projects, labeled by status, and a layer of community reports. Only the second produces the headline number, and no individual report on it is tied to a facility or a status.

    As of its September 27 update, the vetted layer lists 545 projects: 139 operational, 166 under construction, 175 proposed, 39 permitted, and 26 cancelled, drawn from two open datasets, Compute Atlas and Epoch AI [56]. It covers major AI campuses and isn’t complete: of the three DeKalb projects, only Meta’s is on it. The “Community Reported” layer is something else, and it produces the headline figure: 8,837 on July 30 in my screenshot of the map, and 9,683 on October 4 [2].

    “Does every ‘Community Reported’ data point represent an AI data center? No. Reports fall into several categories: AI data centers already operating, facilities under construction, and rumored or proposed projects.” brockovichdatacenter.com, FAQ

    That’s her own documentation [46]. A reader looking at the map can’t tell which category a pin belongs to. By her own description, each report is read; reports without a zip code, city, or enough detail aren’t plotted; and duplicates are removed [46]. Nothing in that description checks whether a report describes a real facility.

    The volume clusters hard. Across 2,447 zip codes, the average is about 4 reports. Her top 20 cities total 1,540 reports, 16% of the national figure [2]. The remaining 8,143 are spread across the other 2,427 zip codes, most in single digits.

    The largest number on the map belongs to a project with no building, no committed developer, and a trial more than a year away. Sulphur Springs, Texas, has 402 reports, more than three times second-place Marshall, Michigan, at 127 [2]. Construction there has been halted amid lawsuits since at least February 2026 [57]. The litigation is a deed-restriction fight between the city and the former landowner, Vistra, plus a resident’s claim that the city violated the Open Meetings Act [58]. None of the litigation concerns water, noise, or health. In June, the mayor announced that MSB Global would no longer lead the project, and, as of July, no replacement had been named [58][59]. In September, the court reissued an injunction barring construction of facilities that generate or store electricity for sale on the property and set trial for November 15, 2027 [60]. CyrusOne held a community meeting that month on a possible campus at the site and says the project is still in due diligence [61][62]. The raw file shows how the count got so high: 158 of the 402 carry the same date, May 1, and 376 carry no note at all [63]. By the file’s own dates, 350 of the 402 arrived in May alone, and 389 were in by May 28 [63]. The count has nearly stopped moving since: comparing the author’s July 30 screenshot of the map with the October 4 stats page, Sulphur Springs added 5 reports while the national total added 846. That fits a one-time burst of filing better than an ongoing stream of new complaints. It also shows how much one town’s filing can move the map: Sulphur Springs alone is 4% of the national total.

    A layer called “Community Reported” measures public sentiment, and sentiment about an unbuilt facility is real. In a town of about 17,000 people [64], 402 reports say something true about that community, though the published file doesn’t show whether one person can file more than once.

    On air, she introduced the map about 30 seconds after telling Maher that data centers are “very destructive.” Then came “every single state in the United States of America was reporting to me,” followed less than a minute later by “it’s the whole country” and “it’s risking and taking all of that” [1]. She never said the reports document damage. She never drew the distinction her own FAQ draws, either. Heard in that sequence, the number reads to me as evidence of widespread damage, not widespread worry. Those call for different policy responses, and the count can’t tell them apart.

    The map also can’t support the case it’s used for. To document harm from operating data centers, it would need reports that can be tied to running facilities. Her site publishes the reports themselves as a data file, so this can be checked. Each record holds a date, a place, a zip code, a type, and optional owner and notes fields. Of the 9,683 records, 7,799, 80.5%, have neither an owner nor a note in the published file: a date, a place name, a zip code, and a facility type, and nothing about what the report concerns [63]. Her FAQ says submissions arrive through a form and each one is read [46], so the submissions may say more than the published file does. The public record doesn’t.

    I compared each report’s location to her own vetted list. The site’s zip-code file gives one coordinate for each zip code, and the vetted file gives coordinates for each project. I counted a report as near a project when that coordinate falls within 10 miles of it, and assigned each report to the most advanced project nearby: operating first, then under construction, then permitted, proposed, or cancelled. By that measure, 1,084 reports, 11.2%, are within 10 miles of an operating facility. Another 2,000, 20.7%, are near a campus under construction but no operating one. Another 2,374, 24.5%, are near only proposed, permitted, or cancelled projects, and 4,220, 43.6%, aren’t within 10 miles of anything on her list. Five had no usable zip code.

    602 of the 1,084 are also within 10 miles of a project on her list that isn’t operating, and the file doesn’t say which project those reports concern. That leaves 482 reports, 5.0%, near an operating facility and no listed project of another status; if cancelled projects don’t count, it’s 510. Counted per facility, with each report counted once for every facility within 10 miles of it, operating campuses average about 14 reports, the same as proposed projects, and campuses under construction about 18. So operating sites do draw reports. The 5% is small mostly because 67 of the 139 operating campuses on her list have a non-operating project within 10 miles, and the test drops every report that shares a circle with one.

    A zip code’s coordinate can sit miles from a rural reporter’s home, and the size and direction of that error vary. Her list leaves out many conventional data centers, so “near nothing” means only that no listed facility is within 10 miles. And proximity says nothing about which facility a report concerns. A resident who has lived next to a running facility for years may never have heard of her map, so a shortage of reports near operating sites isn’t proof of no harm. Reports also track approval fights: neighbors organize when a project is proposed, so a map built from voluntary submissions will cluster around proposals, whatever happens after a facility opens. The distance test only speaks to local effects like noise, light, and wells; electricity costs and water supply reach well past 10 miles. Across every radius from 1 to 30 miles, the operating-only share stays between 1.2% and 5.4%: 442 reports (4.6%) at 5 miles, 482 (5.0%) at 10, and 211 (2.2%) at 25, lower at wide radii because a wider circle catches more new projects. These counts lean low: the test drops every report that shares a circle with another project, and operating facilities missing from her list can’t count at all. More reports sit near projects that aren’t running yet, 4,374 or 45.2%, than near running ones, and the map can’t say which facility any of them concern. The full method, code, and file hashes are in a separate article, “How I Checked Erin Brockovich’s Community-Report Map.”

    Leaving conventional data centers off the list also shapes the story. She acknowledged them on air: “We’ve always had data centers. They’re generally smaller” [1]. They’ve operated for decades, and in my experience they draw few complaints, though most of the ones I know sit in urban cores and business parks, not next to farmhouses. Her FAQ is open about the omission: it says more than 4,000 data centers operate in the U.S., many built before the AI boom, and the map isn’t meant to show them [46]. Both of her source datasets track AI compute, not data centers in general. Leaving them off still sets the old record aside: a reader of the map sees the new facilities with nothing to compare them against, including the decades of conventional facilities that, in my experience, drew few complaints. Scale has grown, steadily rather than overnight, as the Cermak comparison above shows. Old and new facilities share the same core parts, computers, cooling equipment, and backup power, while their scale, layout, cooling design, and power supply can differ a great deal.

    The complaint categories rest on about 1,600 categorized submissions, not the full total. Her stats page builds them from a keyword analysis: the raw counts behind the percentages (663 water reports at 41.2%) imply that base, and one submission can match more than one category. The same percentages appeared in Fast Company’s coverage on May 28, when the map held 2,716 reports [65], and they were unchanged on October 22 at 9,733 [2]. Identical percentages after the total grew more than threefold mean the categories haven’t been rerun since late May; the site doesn’t say so. With that understood: water leads at 41.2%, then electricity and grid at 22.2%, health at 18.1%, wildlife and land at 14.6%, and noise at 13.7% [2]. Health is the largest category this piece doesn’t otherwise address. Her site’s health claims run through noise: her noise simulation, which she labels an illustrative model of a hypothetical facility, pairs modeled noise levels with “sleep disruption, stress response, cardiovascular risk with chronic exposure” and cites the World Health Organization’s night-noise guideline of 40 dB [8]. This piece doesn’t test those health effects; it checks the noise cases. Her Facts vs. Myths page discusses health through sleep disruption from noise and light at night [3]. The health pathways documented in this piece’s operating cases are noise and emissions from on-site generation, covered below. Claims linking the power lines and substations that serve data centers to childhood leukemia and other disease come from other advocacy groups, which concede that the health effects of electromagnetic fields from data centers specifically haven’t been extensively studied [66]. Property values come in last at 1.2% [2]. That doesn’t settle whether this is NIMBY opposition, since NIMBY concerns include noise, traffic, and neighborhood character, all of which rank higher. It does show that the most directly financial complaint a homeowner could make is the one that shows up least in her own categories.

    I checked one zip code by hand, my own, and the map can’t say what its reports describe. DeKalb, Illinois, 60115, carries 8 community reports [63]. On the ground, there are three projects. Meta declared its campus, on more than 500 acres, operational in November 2023 [67][31]. The city council approved Edged’s 560-acre campus on December 8, 2025, in Ordinances 2025-050, 2025-051, and 2025-052, covering the development agreement, annexation, and rezoning [25][32]. On July 22, 2024, the council amended Ordinance 2023-038 to allow a seven-building data center on a 132-acre Karis site, after a planning and zoning recommendation a week earlier [68][69]. One of the three is operating. By Meta’s own figures, it withdrew 105 megaliters of water in 2024, about 28 million gallons [70].

    In August 2026, DeKalb’s city manager told WGLT that the city hasn’t had to deal with complaints about the operating Meta facility over noise or any other pollution issue, and the reporter who visited called it “completely silent” [71]. That’s a complaint record and one visit, not a measurement, and complaints to a city undercount for the same reasons reports to a map do. The documented objection in DeKalb is to Edged, which hasn’t been built: a resident raised habitat, light, and sound concerns at the December hearing [71].

    In her data file, one of the 8 reports in 60115 names Meta as the owner, and the only notes on the other seven say “pics” twice [63]. They could be about Edged, Karis, or the operating Meta campus. The difference matters to anyone trying to use that number. Checking took an afternoon with city council records and one local news story. I haven’t seen anyone do it for the other 2,446 zip codes.

    A verification process built on location and duplicates also can’t sort out cause. A report can be accurate about a problem, such as flooding, and say nothing reliable about what caused it.

    Construction is not operation

    Some of the clearest documented harm in the cases I checked comes from construction, not from a running facility. Her map doesn’t separate the two: about 21% of its reports sit near a campus under construction, and distance can’t say whether they describe the construction or the facility to come. Construction-phase risk is common to any large land-disturbing project.

    The West Virginia flooding on Brockovich’s News page is the clearest example. During earthwork at the Monarch Cloud Campus in Mason County, a silt-retention breach sent water and sediment onto neighboring homes in May [9][10]. After heavy rain on July 11 pushed stormwater past the site’s erosion controls again, the state Department of Environmental Protection issued an enforcement order [72]. The developer has pledged to cover cleanup and repair costs [9]. In July, he put his home purchases at 30, about six closed and around 20 under commitment, and the project’s communications team said 38 homes had been bought out [73]. That’s an erosion and sediment control failure. A federal jury in Georgia returned a $135.5 million verdict in 2023 against a solar developer and its contractors for the same failure mode after runoff turned a neighbor’s 21-acre lake into a mud hole [74]. The judge later found the award excessive and ordered a second trial on damages, and in January 2025 the case settled, on terms neither side disclosed, weeks before that trial [75]. Warehouses, subdivisions, highways, and solar farms all produce it. One erosion-control vendor’s analysis put 29% of the solar projects it reviewed at risk of increased erosion [76]. The Georgia well lawsuit above alleges the same kind of construction-phase harm, though there, causation is disputed. Scale matters, and it cuts both ways. The solar developer graded nearly 1,000 acres, according to the lawsuit [75], the size of a large data center campus, and the bigger the disturbed area, the bigger the erosion-control obligation. A data center under construction behaving like any other large construction site is not evidence that data centers are uniquely hazardous.

    That doesn’t make construction harm irrelevant to an approval. Developers build big campuses in phases: Edged opened its first Aurora building in February 2025 and topped out its second in 2026 [38][39]. Damaged drainage can outlast the construction. The point is where the fix lives: erosion and sediment control permits, bonding, inspection, and enforcement, the same tools that govern any large site.

    Noise works the same way. One resident near a data center under construction in Ahwatukee, in Phoenix, has sent the city about 10 noise complaints since April, describing construction noise early in the morning [77]. The complaint is real, and limits on work hours are enforceable. It’s a different claim from what the facility will sound like once it runs, and both get filed under the same heading.

    Siting: what drives it

    I found no evidence that developers target vulnerable water supplies. New campuses are going up in states with drought, including the three she named, but drought maps show regional conditions, not why a site was chosen.

    Site selection screens on power availability first; CBRE calls it the foremost criterion for greenfield developments [50]. Land, water, and permitting get evaluated within markets that pass that screen. Rural farmland is attractive because it’s cheap, has room to expand, and sometimes comes with water rights and infrastructure from decades of irrigation. None of that requires a drought in the year a site gets picked. Drought status changes from year to year; the power, land, and water rights that drew a developer don’t change with it.

    The stronger version of the concern is externality, not malice. Where local water is priced below its scarcity value, ordinary cost minimization pushes demand toward the cheapest input. Whether that depletes a supply depends on withdrawals, recharge, and permit limits. That’s a pricing and permitting problem, and it would produce the same pattern with any water-intensive industry.

    Midwest milkweed fell 58% from 1999 to 2010, with the loss of milkweed in corn and soybean fields a major contributor, and Midwest monarch production fell 81% over the same period [78]. Herbicide-treated corn and soybean fields have lost most of the milkweed that monarch butterflies depend on, so the claim that a campus is worse for wildlife than the farmland it replaces can get the baseline backwards. Whether a specific campus improves on that baseline depends on whether its stormwater and buffer areas get native plantings or mowed turf.

    The cooling trade-off: water, power, and noise

    Cutting a data center’s water use usually costs something on two other fronts.

    Evaporative cooling can cut a campus’s electricity demand 25% to 35% at peak summer load compared with dry cooling, according to an operator figure cited in a 2026 preprint [79]. The annual gap is smaller: the same preprint cites one company’s dry-cooled Nevada site running a 6.4% to 10.2% higher annual power usage effectiveness (PUE), the ratio of total facility energy to computing energy, than its evaporative-cooled sister site [79]. Air also holds far less heat than water, so rejecting the same heat with dry coolers takes more fans moving more air, and those fans are where most of dry cooling’s added noise comes from. EPA’s review of dry cooling at power plants names the fans as dry cooling’s largest operating energy load and lists increased noise among its disadvantages [80]. That review covers power-plant cooling, not data centers, so it supports the mechanism, not a noise estimate for any data center. A separate article will cover the engineering.

    Microsoft’s Fairwater campus in Mount Pleasant, Wisconsin shows the trade-off in practice. More than 90% of its capacity is cooled by a closed loop that Microsoft says has no evaporation losses, rejecting heat through 172 twenty-foot fans; the remaining servers use outdoor air and switch to water only on the hottest days [81]. Microsoft acknowledged the result on its own site:

    Residents to the north of the facility “have noticed a tonal humming sound.” Microsoft website update, April 15, 2026, which tied the sound to the facility’s cooling fans [82]

    That’s an admission against interest from the operator, which makes it one of the best-evidenced complaints in this debate. It backs up the humming Maher described on air and Brockovich endorsed, “it’s very disturbing to them and I get it,” more cleanly than anything on her map [1]. The order of events matters. Microsoft adjusted the fans in mid-April and said the facility met the local noise ordinance. In June, it said the mitigations had “fully resolved the issue,” and it has kept working on additional sound reduction since [82]. The village reported no formal complaints after the adjustments [83]. Three residents filed a federal class action on July 1, alleging noise from generators and heating, ventilation, and air-conditioning (HVAC) equipment, including low-frequency sound they say A-weighted (dBA) readings understate [83]. A problem the operator says it fixed, a facility it says meets the ordinance, and a lawsuit can all exist at once. Microsoft made zero-water cooling its standard for new data center designs [12], and Fairwater, in the Great Lakes basin, is mostly built that way. Fairwater doesn’t prove an evaporative design would have been quieter; fan selection, speed, and layout matter too. It does show a mostly zero-water design and a noise problem arriving together in a region where water is comparatively plentiful.

    A board weighing a cooling design should ask for its water use, electricity demand, and property-line noise estimates together, because cutting one can raise the others.

    What the noise record shows

    Noise complaints come in two kinds the map doesn’t distinguish, and the difference isn’t about legitimacy. Anticipating harm is what environmental review, zoning hearings, and permit conditions exist for. Worrying about a facility before it’s built is rational. The problem is counting anticipated harm as experienced harm, which is what happens when both land in the same total.

    For a site that isn’t built, a noise complaint describes an expectation, not an observation. In Pittsburg, California, where the city approved an AVAIO Digital data center in November 2024, and opponents were still trying to keep shovels out of the ground in August 2026 [84][85][86], one resident at an opposition meeting described how neighbors form their views: “They read what’s on the outside, you know, different towns, different cities” [87]. That’s a reasonable thing for a resident to do. A dataset shouldn’t count it as a measurement.

    Forecasts and observations need different kinds of evidence. For an unbuilt facility, a resident’s concern and a developer’s promise are both forecasts, and both deserve the same scrutiny. What settles either one is a modeled noise study, a stated water source and volume, and conditions written into the permit.

    For running facilities, the record is thinner than the volume suggests. As of July, WilmerHale found no data center noise nuisance suit that appears to have reached summary judgment or trial [88]. Cases settle, operators mitigate, and many neighbors never sue. The newest class of campus, gigawatt-scale, dry-cooled, sometimes with on-site gas, is only now coming online: Stargate Abilene had six of eight buildings delivered as of September 2026 [40].

    I count a case as documented harm from an operating facility when the operator admits the problem, the operator spends to fix it, or measurements show it. Four of the operating facilities discussed here meet that bar, all on noise. Fairwater rests on the operator’s own admission. An older case in Chandler, Arizona, rests on the operator’s response: in 2018, after neighbors near CyrusOne’s campus petitioned the city over a high-pitched hum from its chillers, CyrusOne spent about $2 million on noise-attenuation blankets. The city said the facility complied with its noise ordinance before, during, and after the work. The retrofit helped, and residents still said the hum bothered them two years later [89][90][91].

    Amazon’s facility near the Great Oak subdivision in Prince William County, Virginia, outside Manassas, rests on reported measurements and county records: a real complaint about an operating facility that produced a 10-decibel reduction after 18 months of pressure [92][93]. A March 2025 presentation by a Great Oak resident to the county’s data center ordinance advisory group, posted on the county’s website and made after both fixes were complete, still described the facility as generating continuous low-frequency noise [94]. That’s what a substantiated complaint followed by a partial fix looks like.

    The most recent is in Aurora, Illinois, and rests on the operator’s response. In April 2025, a failed transformer at CyrusOne’s campus on Diehl Road put one data hall on nine backup generators for several days, and the company apologized to neighbors for the noise. It then started a campus-wide chiller noise project: temporary walls around the chiller plants in June 2025, then permanent rooftop sound walls and chiller attenuators, described as reducing “noise impacts for nearby residents,” with community meetings along the way. CyrusOne reported finishing that work at two buildings by September 30, 2026, and was still adding measures in late October [95].

    A settlement involving a fifth doesn’t meet it. Amazon settled a $20.5 million class action over nitrate contamination in eastern Oregon [96][97]. The case involves operating facilities, not construction. The nitrate problem also predates the data centers. Oregon’s Department of Environmental Quality declared the Lower Umatilla Basin a groundwater management area for nitrate in 1990, decades before the data centers arrived [98]. The other defendants include the Port of Morrow, which oversees the county’s wastewater system; Lamb Weston; large farm and dairy operators; and Portland General Electric. Amazon settled while denying the allegations [96]. With a preexisting nitrate problem and a long list of co-defendants, no one has established Amazon’s share. I don’t count it as documented data center harm, and I don’t leave it out either.

    The biggest open operational case isn’t about cooling at all. xAI powers its Colossus 2 AI campus near Memphis with gas turbines at a plant across the state line in Southaven, Mississippi: 69 of them, according to the NAACP’s lawsuit as reported in October [99]. The count has grown as units were added; emails obtained through a public records request put it at 46 in May [100]. Mississippi regulators let the early turbines run without air permits under an exemption of up to a year for temporary, mobile engines, and in March the state permit board approved 41 permanent turbines to replace 27 that had been running unpermitted [101][102]. The NAACP sued under the Clean Air Act. On October 19, a federal judge refused the Justice Department’s request to dismiss the case [99][103], and on October 30 she denied xAI’s own motion to dismiss, ruling that the plant is not a “mobile source” and “was not (and is not) exempted from permitting requirements” [104]. That ruling came on the pleadings. It sets no penalty and orders nothing yet, and the NAACP’s request for a preliminary injunction is still pending. Three residents have also filed a nuisance class action over noise and vibration [105][106]. Backup generators draw complaints too. During a July 2026 power failure, Vantage’s campus in Sterling, in Loudoun County, Virginia, ran on diesel generators. Nearby residents complained to county supervisors about noise and fumes. Vantage says state regulators reviewed its data and found emissions well below permitted levels [107]. On-site generation is an operational issue that belongs in any honest accounting, and it isn’t hypothetical where I live: DeKalb’s Edged campus plans to run on natural gas generators until regional grid upgrades are finished [24].

    The litigation, and who benefits from it

    A filing is not a finding. Crowell & Moring, a defense firm tracking data center cases, describes plaintiffs’ firms building a replicable complaint, advertising for clients, and filing in multiple jurisdictions at once. It compares the pattern to the growth of litigation over PFAS, the “forever chemicals” [108]. That’s a defense firm’s characterization, but the mechanics aren’t unique to data centers, and they produce volume whether or not a given claim is true.

    Readers should know Brockovich’s own ties, as they should know the author’s. Her speakers bureau describes her as a consultant to Weitz & Luxenberg and to Shine Lawyers in Australia [109]. The Weitz relationship dates to 2008 [110]; I found nothing from either firm confirming it’s current, and the firm’s data center page doesn’t mention her. That page solicits clients for data center pollution and noise claims [111]. Her Substack, The Brockovich Report, lists more than 42,000 subscribers, hundreds of them paid [112].

    Incentives run the other way too. Developers, site-selection consultants, utilities chasing load growth, and economic development agencies all have money riding on approvals. Their claims about an unbuilt facility are forecasts as well, and they need the same checking.

    Electricity and e-waste

    Electricity: Accurate. Her site’s figures, about 4.4% of U.S. electricity in 2023 and 7% to 12% by 2028, match the Department of Energy’s 2024 Lawrence Berkeley National Laboratory report, which put them at 4.4% and 6.7% to 12% [3][51]. Her site credits the International Energy Agency for them rather than the LBNL report, but the numbers aren’t inflated. LBNL published an update in June 2026 [113]; the figures she uses match the 2024 edition.

    E-waste: no number to check, and that’s to her credit. Her site lists e-waste as a concern without a figure. A newer peer-reviewed estimate puts AI hardware waste at 131,000 to 225,000 metric tons a year by 2030 [114], about 90% below an earlier projection of up to 2.5 million tons a year by 2030 [115]. (That earlier study’s figure of 5 million tons is a total for 2023 to 2030, not a yearly one [115].) For scale, U.S. construction and demolition debris came to about 600 million tons in 2018 [116], more than 90% of it from demolition rather than new building [117]. That doesn’t make AI hardware disposal a non-issue. It does mean her map, which tracks new buildings, isn’t tracking the larger waste stream.

    Quick Compare: claims vs. the record

    ClaimWhat was saidThe record shows
    Average golf course water use500 million gal/yearAt most ~38 million gal/year national average (2024); ~150 million for a southwestern course
    Largest campus water useUp to 1.5 billion gal/yearAccurate; Google Council Bluffs withdrew 1.75 billion and consumed 1.35 billion gal (2025); range starts at zero
    Golf vs. data center water“Seven times” (Maher)About 30x today; 7x to 14x by 2028
    New York policy“Has banned it”State permit hold on new 50 MW+ applications pending an environmental study; no fixed end date
    Map reports vs. vetted sites9,683 reports545 vetted projects, 139 operating; 80% of records carry no owner or note
    Map reports near running facilities9,683 reports, shown alongside operating, planned, and proposed sites1,084 (11%) within 10 miles of an operating facility on her list; 482 (5%) near one with no non-operating project nearby; the file can’t say which facility a report concerns
    DeKalb data center acreage“Taking farmland”True; roughly 1,200 acres, 0.34% of county farmland

    Quick Compare: national water use, golf vs. data centers

    Latest2028 (projected)Trend
    Golf (national)~531 billion gal/yr (2024)Flat or decliningDown 31% since 2005
    Data centers (direct, national)~17.4 billion gal/yr (2023)39 to 74 billion gal/yrRising sharply

    Closing

    The map Brockovich leads with on national television can show where people are reporting concern. It can’t separate a rumor from an operating facility, a construction complaint from an operational one, or a correct grievance from a misattributed one. In the on-air sequence above, it reads as evidence of nationwide harm, and its own data can’t show that.

    The rest of her case mostly holds up. Farmland is being lost, the Plains states she named were in drought, and her one clean numerical miss, the golf baseline, makes her argument stronger once it’s fixed.

    A blanket moratorium blocks a well-designed, well-conditioned project as readily as a badly designed one, because it can’t tell them apart. A short, time-limited pause to write standards is defensible where a community has none. Where state law leaves zoning to local boards, as Illinois does and West Virginia no longer does for certified projects, a city council or county board can write them into a special-use permit or development agreement, within what state law allows and alongside the permits state agencies issue: property-line noise limits that cover low-frequency sound, a stated water source and volume, proof of state air permits for any on-site generation, erosion and sediment control bonding, and monitoring after opening with remedies that can be enforced.

    Rates and cost allocation sit with the state. Oklahoma’s HB 2992 shows what that looks like, and it bans nothing. It defines a large load as 75 MW or more, requires that costs be allocated under cost-causation principles, with separate tariffs and 10-year terms for large loads, and requires a developer buying land outside a city or industrial park to notify adjacent owners, county commissioners, and the Corporation Commission within 60 days [118]. That goes after cost allocation and secrecy without blocking anything. This piece doesn’t measure how much cost shifting has happened; a future piece will sort which complaints hold everywhere, which hold only at specific sites, and which don’t hold at all.

    Her form already asks whether a facility is running or coming soon. A version of the map that published that answer, showed how many reports name a specific facility, and showed the count of distinct facilities alongside the report total would be a useful public tool. She has the audience and the submissions to build it.

    Until then, anyone evaluating a project in their own community will get further with city council minutes, state environmental filings, and utility rate cases than with a number from either side. Ask which facility a claim describes, whether it’s built, and whether the complaint is about construction or operation.

    Cover photo: Theodore Christopher / Wikimedia Commons, CC0


    Sources

    [1] Real Time with Bill Maher, HBO, episode 736, July 31, 2026, Erin Brockovich interview (author’s recording and transcript on file; quoted passages at about 9:22 to 10:57, 13:45 to 14:36, and 16:06 to 16:33 of the recording); guest lineup per BroadwayWorld, July 30, 2026: https://www.broadwayworld.com/bwwtv/article/REAL-TIME-WITH-BILL-MAHER-Sets-Guest-Lineup-20260730

    [2] brockovichdatacenter.com, Community Reports Statistics, data through October 4, 2026 (advocacy source; live page has since updated): https://www.brockovichdatacenter.com/community-stats.html (archived October 10, 2026: https://web.archive.org/web/20261010001648id_/https://www.brockovichdatacenter.com/community-stats.html)

    [3] brockovichdatacenter.com, AI Data Centers: Facts vs. Myths: https://www.brockovichdatacenter.com/facts-myths.html (archived October 10, 2026: https://web.archive.org/web/20261010001652id_/https://www.brockovichdatacenter.com/facts-myths.html)

    [4] Epoch AI, How much energy does ChatGPT use?: https://epoch.ai/gradient-updates/how-much-energy-does-chatgpt-use

    [5] TechCrunch, Anthony Ha, Erin Brockovich takes aim at data center secrecy, May 31, 2026: https://techcrunch.com/2026/05/31/erin-brockovich-takes-aim-at-data-center-secrecy/

    [6] Oklahoma House of Representatives, Boles and Green applaud governor for signing HB 2992, May 13, 2026: https://www.okhouse.gov/posts/News-20260513_1

    [7] brockovichdatacenter.com, Communities & Legislation (advocacy source; each entry cites a named source): https://web.archive.org/web/20261026191653id_/https://www.brockovichdatacenter.com/community-and-legislation.html (archived October 26, 2026: “300+ Local Moratoriums & Bans in effect nationwide as of Sept 2026, up from 116 in June”; live page: https://www.brockovichdatacenter.com/community-and-legislation.html)

    [8] brockovichdatacenter.com, Noise Impact Simulation: https://www.brockovichdatacenter.com/noise-impact.html (archived October 11, 2026: https://web.archive.org/web/20261011053702id_/https://www.brockovichdatacenter.com/noise-impact.html)

    [9] WSAZ, Severe flooding in Mason County relating to data center construction, May 24, 2026: https://www.wsaz.com/2026/05/24/data-center-construction-causes-severe-flooding-mason-county-residents-be-reimbursed/

    [10] WV MetroNews, Mason County community impacted by flooding from data center construction site, May 24, 2026: https://wvmetronews.com/2026/05/24/mason-county-community-impacted-by-flooding-from-data-center-construction-site/

    [11] Google, 2026 Environmental Report, water use by data center location, 2025, p. 97 (Council Bluffs, IA: 1,746.4 million gallons withdrawn, 1,346.0 million consumed), and endnote 78, p. 113 (average annual irrigation for a Southwest U.S. golf course is 459 acre-feet, around 150 million gallons, citing USGA 2012): https://sustainability.google/reports/google-2026-environmental-report/ (PDF: https://sustainability.google/files/1699a2e19277e478b38a659f00cb38398a836e8c/download-1699a2e1.pdf)

    [12] Microsoft, Sustainable by design: Next-generation datacenters consume zero water for cooling, December 9, 2024: https://www.microsoft.com/en-us/microsoft-cloud/blog/2024/12/09/sustainable-by-design-next-generation-datacenters-consume-zero-water-for-cooling/

    [13] GCSAA, Golf courses reduce water usage by 31 percent according to national survey, December 30, 2025 (1.63 million acre-feet; the 531 billion gallon conversion is the author’s): https://www.gcsaa.org/who-we-are/media/news-release/2025/12/30/golf-courses-reduce-water-usage-by-31-percent-according-to-national-survey

    [14] Golf Course Management (GCSAA), J. Bryan Unruh and Travis Shaddox, From acre-feet to outcomes: Interpreting the 2024 GCEP Water Survey, December 2025 (survey reached 13,952 facilities; 1,766 responses): https://www.gcmonline.com/research/news/from-acre-feet-to-outcomes-interpreting-the-2024-gcep-water-survey

    [15] Bisnow, Jarred Schenke, Amazon HQ2 search likely won’t upend economic development secrecy, January 30, 2018: https://www.bisnow.com/news/national/economic-development/amazon-hq2-search-likely-wont-upend-economic-development-secrecy-84260

    [16] WNIJ, Bear Savage and Jenna Dooley, Public can weigh in on proposal for 500-acre data center in DeKalb, November 24, 2025: https://www.northernpublicradio.org/wnij-news/2025-11-24/public-can-weigh-in-on-proposal-for-500-acre-data-center-in-dekalb

    [17] Virginia Mercury, Eric Bonds and Viktor Newby (guest commentary), Data centers, non-disclosure agreements and democracy, April 30, 2025: https://virginiamercury.com/2025/04/30/data-centers-non-disclosure-agreements-and-democracy/

    [18] Public Citizen, The Secret Data Center Buildout (advocacy organization): https://www.citizen.org/news/the-secret-data-center-buildout-how-states-can-stop-big-techs-abuse-of-ndas/

    [19] WVTF / Radio IQ, Data center water fight spotlights non-disclosure agreements, February 26, 2026: https://www.wvtf.org/news/2026-02-26/data-center-water-fight-spotlights-non-disclosure-agreements

    [20] WHIO-TV I-Team, Data centers, water, and secrets: Companies using NDAs to hide their names, water usage, November 24, 2025: https://www.whio.com/news/local/i-team-data-centers-water-secrets-companies-using-ndas-hide-their-names-water-usage/SWT7F3PMZZGI7KOHKDQZSKZFSU/

    [21] West Virginia Legislature, Enrolled Committee Substitute for H.B. 2014 (2025), §5B-2-21b(c) and (d): https://www.wvlegislature.gov/Bill_Text_HTML/2025_SESSIONS/RS/bills/hb2014%20sub1%20enr.pdf

    [22] Broadband Breakfast, Jericho Casper, New West Va. Law Grants Sweeping Exemptions to Attract Data Centers, May 2, 2025 (final bill exempts qualifying data centers from local land-use rules “including municipal zoning, permitting, and noise and lighting regulations”): https://broadbandbreakfast.com/new-west-va-law-grants-sweeping-exemptions-to-attract-data-centers/

    [23] USDA NASS, 2022 Census of Agriculture County Profile, DeKalb County, Illinois (archived September 26, 2026; the original address now returns 404): https://web.archive.org/web/20260926110822/https://www.nass.usda.gov/Publications/AgCensus/2022/Online_Resources/County_Profiles/Illinois/cp17037.pdf

    [24] City of DeKalb, Edged Development Approved, December 2025: https://www.cityofdekalb.com/CivicAlerts.aspx?AID=964

    [25] City of DeKalb, Regular City Council Meeting Minutes, December 8, 2025 (Ordinances 2025-050, 2025-051, and 2025-052, Project Vector, approximately 560 acres): https://www.cityofdekalb.com/DocumentCenter/View/20217/2-120825-Regular-Minutes

    [26] Nebraska State Climate Office, July 2026 Monthly Climate Summary: https://nsco.unl.edu/news/july-2026-monthly-climate-summary/

    [27] National Weather Service Dodge City, Drought Information Statement, August 3, 2026 (U.S. Drought Monitor data released July 28, 2026): https://www.weather.gov/media/ddc/DGT/DGT_DDC_08032026.pdf

    [28] Iowa Department of Natural Resources, Water Summary Update: Drought expands in areas of northern and western Iowa, July 9, 2026: https://www.iowadnr.gov/news-release/2026-07-09/water-summary-update-drought-expands-areas-northern-and-western-iowa-east-returns-normal-conditions

    [29] DataCenterDynamics, Meta purchases additional 1,400 acres for Hyperion mega data center expansion, February 9, 2026: https://www.datacenterdynamics.com/en/news/meta-purchases-additional-1400-acres-for-hyperion-mega-data-center-expansion/

    [30] DataCenterDynamics, Seven-building data center campus gets preliminary OK from Illinois planning commission: https://www.datacenterdynamics.com/en/news/seven-building-data-center-campus-gets-preliminary-ok-from-illinois-planning-commission/

    [31] Shaw Local, Meta expands DeKalb data center, totaling $1B investment, April 27, 2022: https://shawlocal.com/daily-chronicle/news/2022/04/27/meta-expands-dekalb-data-center-totaling-1b-investment

    [32] Shaw Local, Unanimous yes to 560-acre DeKalb data center, December 9, 2025: https://www.shawlocal.com/daily-chronicle/2025/12/09/unanimous-yes-to-560-acre-dekalb-data-center

    [33] Utah News Dispatch, Renderings show vision for massive data center proposed in Utah, May 19, 2026: https://utahnewsdispatch.com/2026/05/19/renderings-show-massive-data-center-box-elder-utah-permits-could-take-years/

    [34] KUTV, Utah governor posts answers to questions, concerns about Box Elder County data center, May 8, 2026 (“the initial permit in phase one of the project will be fewer than 2,000 acres in the data center building footprint”): https://kutv.com/news/local/utah-governor-posts-answers-to-questions-concerns-about-box-elder-county-data-center

    [35] KPCW, Kevin O’Leary to scale back Utah project, says it won’t be the largest data center in the world, June 5, 2026: https://www.kpcw.org/state-regional/2026-06-05/kevin-oleary-to-scale-back-utah-project-says-it-wont-be-the-largest-data-center-in-the-world

    [36] DataCenterDynamics, Digital Realty files to build 565,000 sq ft data center in Chicago (350 E Cermak history and capacity): https://www.datacenterdynamics.com/en/news/digital-realty-files-to-build-565000-sq-ft-data-center-in-chicago/

    [37] Digital Realty, 350 East Cermak Road property factsheet (8 levels; 1,133,000 sq ft), on Digital Realty’s site: https://go2.digitalrealty.com/rs/087-YZJ-646/images/DS_Digital_Realty_2308_ORD10_Property_Factsheet_EN.pdf (an earlier version of the same factsheet, hosted by Data Center Map, also lists 109,000 kW utility power and 70,000 kW UPS: https://static.datacentermap.com/company/digital-realty-trust/datacenter980/DS_Digital_Realty_2308_ORD10_Property_Factsheet_EN.pdf)

    [38] DataCenterDynamics, Edged launches first phase of 96MW Chicago data center campus, February 27, 2025: https://www.datacenterdynamics.com/en/news/edged-launches-first-phase-of-96mw-chicago-data-center-campus

    [39] DataCenterDynamics, Edged tops out second building at Chicago data center campus, June 5, 2026: https://www.datacenterdynamics.com/en/news/edged-tops-out-second-building-at-chicago-data-center-campus-illinois/

    [40] Epoch AI, OpenAI Stargate Abilene, AI Data Centers directory (timeline entry for September 10, 2026, quoting Oracle’s Q1 FY27 earnings call: “618 megawatts and 75% of total capacity have now been delivered to the customer”; six of eight buildings): https://epoch.ai/data/ai-data-centers/directory/openai-stargate-abilene

    [41] Epoch AI, OpenAI Stargate: where the US sites stand, April 2026: https://epoch.ai/publications/openai-stargate-where-the-us-sites-stand

    [42] Synergy Research Group (TechInsights), Hyperscale Data Center Count Hits 1,136; Average Size Increases; US Accounts for 54% of Total Capacity, March 19, 2025 (industry analyst): https://srgresearch.com/articles/hyperscale-data-center-count-hits-1136-average-size-increases-us-accounts-for-54-of-total-capacity

    [43] Atlanta Journal-Constitution, Georgia families sue Meta, accuse its data center of tainting their water, September 1, 2026: https://www.ajc.com/news/2026/09/georgia-families-sue-meta-accuse-its-data-center-of-tainting-their-water/

    [44] U.S. District Court for the Northern District of Georgia, Morris v. Meta Platforms, Inc., No. 1:26-cv-06273-SDG, docket (removed from Gwinnett County Superior Court, No. 26-A-07974-11; notice of removal filed October 16, 2026, ECF 1; first amended complaint and motion to remand, October 28, 2026, ECF 26 and 27), retrieved from PACER October 29, 2026; public copy: https://www.courtlistener.com/docket/74996593/morris-v-meta-platforms-inc/

    [45] WSB-TV, 4 Georgia families sue Meta, claim data center construction contaminated well water, October 21, 2026: https://www.wsbtv.com/news/local/4-georgia-families-sue-meta-claim-data-center-construction-contaminated-well-water/FVX726UR7FGJTLEAOYTQ4MDZ2Y/

    [46] brockovichdatacenter.com, FAQ: https://www.brockovichdatacenter.com/faq.html (archived October 20, 2026: https://web.archive.org/web/20261020235820id_/https://www.brockovichdatacenter.com/faq.html)

    [47] New York State, Executive Order No. 62, Establishing a Temporary Moratorium on Data Centers in New York While the State Develops Standards, July 14, 2026: https://www.governor.ny.gov/executive-order/no-62-establishing-temporary-moratorium-data-centers-new-york-while-state-develops

    [48] Route Fifty, Many localities have tried data center moratoriums, tracker finds (National League of Cities tracker), August 28, 2026: https://www.route-fifty.com/artificial-intelligence/2026/08/many-localities-have-tried-data-center-moratoriums-tracker-finds/415696/

    [49] National League of Cities, Data Center Local Action Tracker (dashboard last refreshed October 28, 2026; counts of localities with a moratorium or ban entry by the author): https://www.nlc.org/resource/data-center-local-action-tracker/

    [50] CBRE, North America Data Center Trends H1 2025, September 8, 2025: https://www.cbre.com/insights/reports/north-america-data-center-trends-h1-2025

    [51] Shehabi et al., 2024 United States Data Center Energy Usage Report, Lawrence Berkeley National Laboratory, December 2024, doi:10.71468/P1WC7Q (water figures pp. 55-56): https://web.archive.org/web/20261022090909/https://escholarship.org/content/qt32d6m0d1/qt32d6m0d1.pdf

    [52] Data Center Knowledge, Christopher Tozzi, The pros and cons of dry coolers for data centers, July 9, 2025: https://datacenterknowledge.com/cooling/the-pros-and-cons-of-dry-coolers-for-data-centers

    [53] Texas Standard, Stargate data center poised to complete construction this year in Abilene: https://texasstandard.org/stories/stargate-data-center-abilene-texas-construction-ai-artificial-intelligence/

    [54] Crusoe, Crusoe, Blue Owl Capital and Primary Digital Infrastructure enter second phase of $15 billion joint venture for the 1.2 GW Abilene, Texas data center, May 21, 2025: https://www.crusoe.ai/resources/newsroom/crusoe-blue-owl-capital-and-primary-digital-infrastructure-enter-joint-venture

    [55] DataCenterDynamics, Oracle to spend $40bn on Nvidia chips for OpenAI Texas data center (Abilene; JPMorgan loans of $9.6 billion and about $5 billion from Crusoe and Blue Owl): https://www.datacenterdynamics.com/en/news/oracle-to-spend-40bn-on-nvidia-chips-for-openai-texas-data-center/

    [56] brockovichdatacenter.com, vetted facility data file (data-centers-map.json, updated September 27, 2026; sources Compute Atlas and Epoch AI): https://www.brockovichdatacenter.com/data-centers-map.json (archived version analyzed: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/data-centers-map.json?v=20260927)

    [57] KLTV, Judge denies major motion from City of Sulphur Springs in data center lawsuits, February 10, 2026: https://kltv.com/2026/02/10/judge-denies-major-motion-city-sulphur-springs-data-center-lawsuits/

    [58] KLTV, New developer to take over data center project in Sulphur Springs amid legal battles, June 2, 2026: https://www.kltv.com/2026/06/03/new-developer-take-over-data-center-project-sulphur-springs-amid-legal-battles/

    [59] KLTV, Vistra seeks dismissal of key claims in Sulphur Springs legal fight over data center site, July 7, 2026: https://www.kltv.com/2026/07/07/vistra-seeks-dismissal-key-claims-sulphur-springs-legal-fight-over-data-center-site/

    [60] District Court of Hopkins County, Texas, 62nd Judicial District, City of Sulphur Springs v. Luminant Mining Company, LLC, et al., Cause No. CV45943, Order Granting Temporary Injunction, signed September 14, 2026 (copy from re:SearchTX, posted by East Texas Radio): https://drive.google.com/file/d/165w-r6rg7bwOUtSLBx53Jf70q2LM5Q7y/view (East Texas Radio report, September 15, 2026: https://easttexasradio.com/judge-rules-in-favor-of-vistra-and-luminent-over-restrictive-covenant-on-thurmo-property/)

    [61] KLTV, Data center developer holds community meeting on potential Sulphur Springs project, September 25, 2026: https://www.kltv.com/2026/09/25/data-center-developer-holds-community-meeting-potential-sulphur-springs-project/

    [62] CyrusOne, Sulphur Springs Data Center project page (“still in the due diligence and planning phase”): https://www.cyrusone.com/data-centers/north-america/sulphur-springs-texas

    [63] brockovichdatacenter.com, community reports data file (community-reports.json, version October 4, 2026, 9,683 records; the live file has since grown; zip-code coordinates from zip-geocodes.json; analysis by the author; full method in the companion article “How I Checked Erin Brockovich’s Community-Report Map”): archived version analyzed: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/community-reports.json?v=20261004; zip-code coordinates: https://web.archive.org/web/20261010001607id_/https://www.brockovichdatacenter.com/zip-geocodes.json?v=20260927

    [64] U.S. Census Bureau QuickFacts, Sulphur Springs city, Texas (15,941 in the 2020 Census; 17,054 estimated July 1, 2025): https://www.census.gov/quickfacts/fact/table/sulphurspringscitytexas/PST045224

    [65] Fast Company, Jennifer Mattson, This map tracks 4,000 AI data centers being built, May 28, 2026 (2,716 reports; water 41.2%, grid 22.2%, health 18.1%): https://www.fastcompany.com/91549212/ai-data-center-map-reveals-where-biggest-boom-is-erin-brockovich

    [66] Environmental Health Sciences, Is it safe to live near a data center? (advocacy organization), March 14, 2026: https://ehsciences.org/data-centers-increase-electromagnetic-fields-emf-exposure/

    [67] FOX 32 Chicago, Meta’s new Illinois data center operational, November 29, 2023: https://www.fox32chicago.com/news/meta-new-illinois-data-center-operational

    [68] City of DeKalb, Planning and Zoning Commission Minutes, July 15, 2024 (recommendation to amend Ordinance 2023-038 for Karis Acquisitions, 132 acres at Peace and Gurler roads, adding data center as a permitted use): https://www.cityofdekalb.com/AgendaCenter/ViewFile/Minutes/_07152024-2555

    [69] City of DeKalb, Development Projects List as of July 15, 2026 (Karis: recommended 7/15/24, approved 7/22/24; Edged/Project Vector: recommended 12/1/25, approved 12/8/25): https://www.cityofdekalb.com/DocumentCenter/View/21222/Development-Projects-List-7-15-26-

    [70] Meta, 2025 Environmental Data Index, Water Withdrawal by Facility, p. 9 (DeKalb, IL: 105 megaliters in 2024; the megaliter-to-gallon conversion is the author’s): https://sustainability.atmeta.com/wp-content/uploads/2025/10/Meta_2025-Environmental-Data-Index.pdf

    [71] WGLT / Illinois Public Radio, Ben Howell, How Aurora and DeKalb are dealing with data centers, August 2026: https://www.wglt.org/local-news/2026-08-03/how-aurora-and-dekalb-residents-are-dealing-with-data-centers (republished: https://ipmnewsroom.org/how-aurora-and-dekalb-are-dealing-with-data-centers/)

    [72] West Virginia Department of Environmental Protection, WVDEP issues enforcement order following stormwater violations at Monarch Cloud Campus construction site, July 14, 2026: https://dep.wv.gov/news/Pages/WVDEP-Issues-Enforcement-Order-Following-Stormwater-Violations-at-Monarch-Cloud-Campus-Construction-Site.aspx

    [73] WSAZ, Flooding continues near construction of Mason County data center, July 13, 2026: https://www.wsaz.com/2026/07/13/flooding-continues-near-construction-mason-county-data-center/

    [74] FOX 5 Atlanta, Georgia couple awarded $135.5M over damages by solar company, contractor, May 4, 2023: https://www.fox5atlanta.com/news/georgia-couple-awarded-damages-solar-company-contractor

    [75] Atlanta Journal-Constitution, Silicon Ranch settles with Georgia couple in muddy runoff case, January 14, 2025: https://www.ajc.com/news/business/silicon-ranch-settles-with-georgia-couple-in-muddy-runoff-case/VFW4S4KO3ZF6VB6PGROV2YCERU/ (archived July 14, 2026: https://web.archive.org/web/20260714163128/https://www.ajc.com/news/business/silicon-ranch-settles-with-georgia-couple-in-muddy-runoff-case/VFW4S4KO3ZF6VB6PGROV2YCERU/)

    [76] Informed Infrastructure, Ross Bruno (Profile Products), From the ground up (erosion-control vendor analysis): https://read.informedinfrastructure.com/articles/from-the-ground-up

    [77] Cronkite News, Attorney General Kris Mayes holds town hall to hear about data center concerns, October 15, 2026: https://cronkitenews.azpbs.org/2026/10/15/kris-mayes-data-centers-town-hall/ (archived October 23, 2026: https://web.archive.org/web/20261023001923/https://cronkitenews.azpbs.org/2026/10/15/kris-mayes-data-centers-town-hall/)

    [78] Pleasants and Oberhauser, Milkweed loss in agricultural fields because of herbicide use: effect on the monarch butterfly population, Insect Conservation and Diversity 6:135-144 (2013) (peer-reviewed), doi:10.1111/j.1752-4598.2012.00196.x; abstract, archived February 25, 2024: https://web.archive.org/web/20240225040930/https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1752-4598.2012.00196.x

    [79] Small Bottle, Big Pipe: Quantifying and Addressing the Impact of Data Centers on Public Water Systems (preprint): https://arxiv.org/pdf/2603.02705

    [80] U.S. EPA, Technical Development Document for the Final Regulations Addressing Cooling Water Intake Structures for New Facilities, EPA-821-R-01-036, November 2001, Chapter 4, pp. 4-5 to 4-6: https://www.epa.gov/sites/production/files/2015-04/documents/cooling-water_phase-1_tdd_2001.pdf

    [81] Microsoft, Inside the world’s most powerful AI datacenter, September 18, 2025: https://blogs.microsoft.com/blog/2025/09/18/inside-the-worlds-most-powerful-ai-datacenter/

    [82] Microsoft, Update on our investigation of humming sound at our Mount Pleasant datacenter (updates April 10, April 15, June 18, and July 20, 2026): https://local.microsoft.com/blog/testing-underway-to-understand-noise-at-our-mount-pleasant-datacenter/

    [83] Wisconsin Public Radio, Microsoft sued over noise complaints at new Mount Pleasant data center, July 2, 2026: https://www.wpr.org/news/microsoft-sued-noise-complaints-at-new-mount-pleasant-data-center

    [84] City of Pittsburg, Perseus Data Center project page: https://www.pittsburgca.gov/services/perseus-data-center

    [85] Contra Costa News, Pittsburg launches webpage on AVAIO data center, June 30, 2026 (“the AVAIO Perseus Data Center”; council approval in November 2024): https://contracosta.news/2026/06/30/pittsburg-launches-webpage-on-avaio-data-center/

    [86] NBC Bay Area, Pittsburg residents protest approved data center, August 3, 2026: https://www.nbcbayarea.com/news/local/pittsburg-residents-protest-approved-data-center/4123100/

    [87] CBS San Francisco, Planned data center in Pittsburg brings residents out in force in opposition, 2026: https://www.cbsnews.com/sanfrancisco/news/planned-data-center-in-pittsburg-brings-residents-out-in-force-in-opposition/

    [88] WilmerHale, Data centers in court: the emerging wave of nuisance, environmental, and land-use litigation, July 13, 2026: https://www.wilmerhale.com/en/insights/client-alerts/20260713-data-centers-in-court-the-emerging-wave-of-nuisance-environmental-and-land-use-litigation

    [89] ABC15 Arizona, Chandler residents annoyed with humming noise, April 20, 2018: https://www.abc15.com/news/region-southeast-valley/chandler/chandler-residents-frustrated-over-humming-noise

    [90] DataCenterDynamics, CyrusOne forced to take action following noise complaints in Chandler, Arizona, April 16, 2018: https://www.datacenterdynamics.com/en/news/cyrusone-forced-to-take-action-following-noise-complaints-in-chandler-arizona/

    [91] Phoenix Magazine, Douglas Towne, Land Zo: Chandler’s Bad Buzz, April 25, 2020: https://www.phoenixmag.com/?p=95601

    [92] Engadget, How to fight a data center (Amazon Manassas noise reduction), 2026: https://www.engadget.com/2227325/how-to-fight-a-data-center/

    [93] Potomac Local, Amazon tones down its data center noise after residents sound the alarm, October 25, 2023: https://www.potomaclocal.com/2023/10/25/amazon-tones-down-its-data-center-noise-after-residents-sound-the-alarm

    [94] Prince William County, Data Center Ordinance Advisory Group, Great Oak status and proposed ordinance levels, March 19, 2025: https://pwcva.gov/assets/2025-03/DCOAG%20Great%20Oak%20Status%20Proposed%20Ordinance%20Levels%20PowerPoint%2020250319.pdf

    [95] CyrusOne, Aurora, IL: CHI1-CHI3 noise mitigation communication and back-up generator schedule (operator page; updates April 24, 2025 to October 26, 2026): https://www.cyrusone.com/data-centers/north-america/aurora-il-back-up-generator-schedule

    [96] FERN, Sean Patrick Cooper, Amazon to pay $20.5 million to settle class action suit over pollution in eastern Oregon, March 31, 2026: https://thefern.org/2026/03/breaking-amazon-to-pay-20-5-million-to-settle-class-action-suit-over-pollution-ineastern-oregon/

    [97] Oregon Capital Chronicle, Amazon to pay $20.5 million settlement over northeast Oregon nitrate pollution, March 31, 2026: https://oregoncapitalchronicle.com/2026/03/31/amazon-to-pay-20-5-million-settlement-over-northeast-oregon-nitrate-pollution/

    [98] Oregon Department of Environmental Quality, Groundwater Management Areas: https://www.oregon.gov/deq/wq/programs/Pages/GWP-Management-Areas.aspx

    [99] Mississippi Today, Judge rejects Trump DOJ request to dismiss NAACP xAI lawsuit, October 21, 2026: https://mississippitoday.org/2026/10/21/judge-trump-administration-xai-naacp-lawsuit-southaven/

    [100] DataCenterDynamics, xAI deploys 19 natural gas turbines at Colossus 2 data center in Southaven, Mississippi (citing Wired and MDEQ emails obtained by the Southern Environmental Law Center), May 14, 2026: https://datacenterdynamics.com/en/news/xai-deploys-19-natural-gas-turbines-at-colossus-2-data-center-in-southaven-mississippi-report/

    [101] Mississippi Free Press, report on the NAACP’s motion to shut down xAI’s Southaven turbines, May 8, 2026 (updated June 25, 2026): https://mississippifreepress.org/xai-gas-turbines-causing-harm-in-southaven-naacp-argues-in-motion-to-shut-them-down

    [102] Mississippi Free Press, Mississippi permit board grants xAI’s request for 41 Southaven gas turbines, March 10, 2026: https://www.mississippifreepress.org/mississippi-permit-board-grants-xais-request-for-41-southaven-gas-turbines-to-power-memphis-data-center/

    [103] DeSoto County News, Judge lets NAACP lawsuit over Southaven xAI turbines proceed, October 20, 2026: https://desotocountynews.com/mississippi-news/southaven-xai-turbines-lawsuit-proceeds/

    [104] U.S. District Court for the Northern District of Mississippi, NAACP v. X.AI Corp., No. 3:26-cv-00074, Opinion and Order denying motion to dismiss, ECF 139, October 30, 2026: https://storage.courtlistener.com/recap/gov.uscourts.msnd.52261/gov.uscourts.msnd.52261.139.0_1.pdf (Earthjustice release on the ruling, plaintiffs’ counsel: https://earthjustice.org/press/2026/court-denies-xais-motion-to-dismiss-air-pollution-lawsuit-against-elon-musks-company)

    [105] Mississippi Free Press, report on residents’ class-action nuisance suit over xAI’s Southaven turbines, June 10, 2026 (updated June 25, 2026): https://www.mississippifreepress.org/?p=359745

    [106] PCMag, Mississippi residents sue xAI over near-constant noise from data centers, 2026: https://www.pcmag.com/news/mississippi-residents-sue-xai-over-near-constant-noise-from-data-centers

    [107] WJLA, Data center noise, fumes create flood of complaints in Loudoun County, July 23, 2026: https://wjla.com/news/local/story/data-center-noise-fumes-create-flood-of-complaints-in-loudoun-county-virginia-board-of-supervisors-sterling

    [108] Crowell & Moring, Data centers in the crosshairs: the plaintiffs’ bar has begun filing new claims using old tricks (defense counsel), 2026: https://www.crowell.com/en/insights/client-alerts/data-centers-in-the-crosshairs-the-plaintiffs-bar-has-begun-filing-new-claims-using-old-tricks

    [109] Aurum Speakers Bureau, Erin Brockovich speaker profile: https://aurumbureau.com/speaker/erin-brockovich/

    [110] ABA Journal, Erin Brockovich signs on with NYC law firm, September 26, 2008: https://www.abajournal.com/news/article/erin_brockovich_signs_on_with_nyc_law_firm

    [111] Weitz & Luxenberg, Data center pollution litigation (plaintiffs’ firm): https://www.weitzlux.com/environmental/pollution/data-center-pollution-litigation/

    [112] The Brockovich Report (Substack), home page (“Over 42,000 subscribers”) and Substack’s ranking label in the page data (“Hundreds of paid subscribers”): https://www.thebrockovichreport.com/ (archived October 26, 2026: https://web.archive.org/web/20261026191126id_/https://www.thebrockovichreport.com/)

    [113] Lawrence Berkeley National Laboratory, United States Data Center Energy Usage Report: 2025 Update, June 2026: https://eta-publications.lbl.gov/publications/united-states-data-center-energy-2025

    [114] Vrije Universiteit Amsterdam, New estimate of AI e-waste (university release on Alex de Vries-Gao, Resources, Conservation and Recycling), February 27, 2026: https://vu.nl/en/news/2026/new-estimate-of-ai-e-waste

    [115] Physics World, Generative AI has an electronic waste problem, researchers warn (Wang, Tzachor et al., Nature Computational Science, 2024): https://physicsworld.com/a/generative-ai-has-an-electronic-waste-problem-researchers-warn

    [116] U.S. EPA, Construction and Demolition Debris: Material-Specific Data: https://www.epa.gov/facts-and-figures-about-materials-waste-and-recycling/construction-and-demolition-debris-material

    [117] U.S. EPA, Sustainable Management of Construction and Demolition Materials: https://www.epa.gov/smm/sustainable-management-construction-and-demolition-materials

    [118] Oklahoma Legislature, Enrolled House Bill 2992 (Data Center Customer Ratepayer Protection Act of 2026): https://www.oklegislature.gov/cf_pdf/2025-26%20ENR/hB/HB2992%20ENR.PDF

  • EMF From a Data Center Comes From the Substation, Not the Servers

    EMF From a Data Center Comes From the Substation, Not the Servers

    Part 13 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    The last of the thirteen records is the one with the least to do with the building. Fiber carries no power-frequency current. Network copper carries signal at low power. The 60 Hz fields neighbors ask about come from the substation, transformers, switchgear, and conductors that serve any large load, and the same substation would serve a plant, a hospital, or a subdivision.

    That makes EMF a Selective concern as applied to data centers and a Contested one as applied to power lines, and this post rates it both ways. The science is not settled in either direction: IARC’s “possibly carcinogenic” classification from 2002 rests on a childhood leukemia association, the exposure guidelines were built to prevent acute nerve stimulation and not to address that association, and Illinois has no statewide numeric limit. Calling the concern fabricated overstates the case against it as much as calling it proven overstates the case for it.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Electromagnetic Fields

    Claim: The data center will expose neighbors to dangerous EMF. Tier: Selective. The source is power infrastructure, not the data center.

    Fiber carries no power-frequency current, and network copper carries signal current at low power. The 60 Hz fields come from the substations, transformers, switchgear, and high-current conductors that serve any large load: a plant, a hospital, a distribution center, or the substation serving a subdivision. [34]

    Claim: Power-line EMF causes cancer. The reverse claim: EMF concerns are made up. Tier for both: Contested.

    IARC classified extremely low frequency magnetic fields as possibly carcinogenic (Group 2B) in 2002, based on associations between long-term residential exposure and childhood leukemia. [35] ICNIRP’s 2010 guidelines set public reference levels at 2,000 milligauss to prevent acute nerve stimulation, not from a risk assessment of long-term low-level exposure. ICNIRP calls the leukemia evidence “too weak to form the basis for exposure guidelines” while acknowledging pooled analyses that “indicate that an excess risk may exist for average exposures exceeding 0.3 to 0.4 µT,” 3 to 4 milligauss, about three orders of magnitude below the reference level; WHO says the evidence is not strong enough to be considered causal. [34][35a] The United States has no federal limit. Six states set numeric limits for power-line fields and five apply “prudent avoidance”; Illinois was in neither group in the 2018 international comparison, which covers statewide standards, not conditions the Illinois Commerce Commission may attach to a siting order. [36] The signal exists, the standards were not built to address it, and none of it is specific to data centers. Calling it fabricated overstates the case against it as much as calling it proven overstates the case for it.


    What to ask for. Ask where the power comes from and what it requires. In my experience, a campus at this scale rarely connects to existing distribution. It typically needs a new substation, switchyard, transmission upgrades, and easements, and those are sited and permitted separately, often by the utility and the Illinois Commerce Commission rather than the municipality. In the applications I reviewed, the EMF question and the visual and environmental footprint of that infrastructure did not appear. Require the applicant to identify the interconnection plan and the off-site work at the time of approval, so the council is evaluating the whole project and not just the building. Where a substation or new line will sit near homes, ask whoever designs it, the applicant or the utility, for the calculated magnetic field at the nearest homes, with the load and averaging assumptions stated. Residents will have read the 3 to 4 milligauss figure from the pooled leukemia analyses. [34][35a] That figure describes average long-term exposure in a home, in studies that show an association and not a cause. It is not a safety limit, and a property-line calculation is not the same measurement, so the useful answer says how the expected household exposure compares with it and on what assumptions.

    Where the series ends. Thirteen records, one building type, and no uniform verdict. Four of the thirteen hold at compliant facilities everywhere: construction disruption, lighting’s effect on wildlife, farmland conversion, and the wastewater stream from evaporative cooling. One, infrasound, has no evidentiary basis. The rest turn on grid, climate, hydrology, design, or distance, and on whether the person making the claim carried those conditions with it. What the imported cases from Virginia, Arizona, Oregon, Tennessee, and Georgia carry to Illinois is less their harm than their gaps: no cumulative generator review, no required pre-construction well test, no state or county rule requiring an acoustic baseline, where only cities such as Yorkville and Aurora have written one, and a vesting clause that can freeze out whatever the city learns next. Before the next approval vote, put three things in the record: the baselines, measured before ground is broken; the corridor-wide estimates of generator emissions and water demand; and enforceable limits on water, noise, and generator operation that the vesting clause does not freeze. The next dispute then gets settled with a measurement.

    This is part 13 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: chemical hazards. The full article also covers where the industry, the opposition, regulators, and local government each get it wrong, and collects every condition above in one checklist.

    Cover photo: Ron Clausen / Wikimedia Commons, CC0


    Citations

    [34] International Commission on Non-Ionizing Radiation Protection, “Guidelines for Limiting Exposure to Time-Varying Electric and Magnetic Fields (1 Hz to 100 kHz),” Health Physics, Vol. 99, No. 6, pp. 818-836, 2010. This is the current ICNIRP primary guideline for extremely low frequency fields, superseding the 1998 up-to-300-GHz guideline for this frequency range. Reference levels at 50/60 Hz: 200 microtesla (2,000 milligauss) general public, 1 millitesla (10,000 milligauss) occupational. Read directly: Table 4 general public reference level 2 x 10^-4 T and Table 3 occupational 1 x 10^-3 T at 50 to 400 Hz; “It is the view of ICNIRP that the currently existing scientific evidence that prolonged exposure to low frequency magnetic fields is causally related with an increased risk of childhood leukemia is too weak to form the basis for exposure guidelines”; pooled analyses “indicate that an excess risk may exist for average exposures exceeding 0.3-0.4 µT”; the only well-established effects in volunteers are nerve stimulation and retinal phosphenes. https://www.icnirp.org/cms/upload/publications/ICNIRPLFgdl.pdf (archived: https://web.archive.org/web/20261012204141/https://www.icnirp.org/cms/upload/publications/ICNIRPLFgdl.pdf). Milligauss figures are direct conversions of ICNIRP’s 200 µT and 1 mT (1 µT = 10 mG).

    [35] International Agency for Research on Cancer, IARC Monographs on the Evaluation of Carcinogenic Risks to Humans, Volume 80, “Non-Ionizing Radiation, Part 1: Static and Extremely Low-Frequency (ELF) Electric and Magnetic Fields,” 2002: ELF magnetic fields classified Group 2B, possibly carcinogenic to humans, on the basis of childhood leukaemia epidemiology, as described in ICNIRP 2010 [34] and WHO Fact Sheet 322 [35a]. https://publications.iarc.who.int/Book-And-Report-Series/Iarc-Monographs-On-The-Identification-Of-Carcinogenic-Hazards-To-Humans/Non-ionizing-Radiation-Part-1-Static-And-Extremely-Low-frequency-ELF-Electric-And-Magnetic-Fields-2002 (archived: https://web.archive.org/web/20260924134857/https://publications.iarc.who.int/Book-And-Report-Series/Iarc-Monographs-On-The-Identification-Of-Carcinogenic-Hazards-To-Humans/Non-ionizing-Radiation-Part-1-Static-And-Extremely-Low-frequency-ELF-Electric-And-Magnetic-Fields-2002)

    [35a] World Health Organization, “Electromagnetic fields and public health: Exposure to extremely low frequency fields,” Fact Sheet No. 322, June 2007. IARC classification based on “pooled analyses of epidemiological studies demonstrating a consistent pattern of a two-fold increase in childhood leukaemia associated with average exposure to residential power-frequency magnetic field above 0.3 to 0.4 µT” (3 to 4 milligauss); “the evidence related to childhood leukaemia is not strong enough to be considered causal.” Copy hosted by the Bonneville Power Administration: https://www.bpa.gov/-/media/Aep/lands/EMF_WHO_EMF-Fact-Sheet-2007a1.pdf (archived: https://web.archive.org/web/20261025155101/https://www.bpa.gov/-/media/Aep/lands/EMF_WHO_EMF-Fact-Sheet-2007a1.pdf)

    [36] Netherlands National Institute for Public Health and the Environment (RIVM), “Comparison of international policies on electromagnetic fields (power frequency and radiofrequency fields),” 2018, p. 8: “United States: No federal legislation is in force. In some states (Colorado, Connecticut, Hawaii, Maryland, Ohio), variations on the ‘prudent avoidance’ principle have been adopted. … In other states, fixed limits for the electric or magnetic field of power lines are set, varying from 20% to 240% of the reference level in the EU recommendation (Florida, Minnesota, Montana, New Jersey, New York, Oregon).” Illinois appears in neither list. https://www.rivm.nl/sites/default/files/2018-11/Comparison%20of%20international%20policies%20on%20electromagnetic%20fields%202018.pdf (archived: https://web.archive.org/web/20261025155410/https://www.rivm.nl/sites/default/files/2018-11/Comparison%20of%20international%20policies%20on%20electromagnetic%20fields%202018.pdf)

  • PFAS Foam, Dielectric Fluid, and Batteries: The Chemical Hazards at a Data Center

    PFAS Foam, Dielectric Fluid, and Batteries: The Chemical Hazards at a Data Center

    Part 12 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    A data center holds three things that can go wrong chemically: the foam in the generator yard’s fire suppression, the fluid in an immersion-cooled hall, and the batteries that carry the load until the generators start. Only the first has a documented groundwater record, and that record belongs to sites where aqueous film-forming foam was tested or discharged, which is why “PFAS” arrives at hearings with more certainty than the evidence carries.

    This post rates three chemical claims: the PFAS foam concern, which is Regional and has an accountability failure attached to it; immersion cooling fluids, which are plausible and undocumented; and fire risk, where the data that would settle it does not exist in public. It ends with the one line that belongs in every application and almost never appears: the fire suppression agent, named, for the generator yard and the data halls separately.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Chemical Hazards

    Claim: Data centers will contaminate groundwater with PFAS from firefighting foam. Tier: Regional. Sites where foam was tested or discharged.

    Aqueous film-forming foam (AFFF) is the documented concern. Its per- and polyfluoroalkyl substances (PFAS) are associated with groundwater contamination where suppression systems were tested or discharged, and PFOA and PFOS are CERCLA hazardous substances. [15a] Their federal drinking water limits of 4 parts per trillion remain in place; EPA’s May 2026 proposals would keep them, let systems that request it take until 2031 to comply, and rescind the limits for four other PFAS; neither is final. [15d] Two distinctions keep the concern from being misapplied. AFFF is a foam for flammable-liquid fires, which at a data center means the fuel and generator yard, not the data hall. The clean-agent gases common in data halls, FK-5-1-12 and HFC-227ea, are not foams and do not reach groundwater the way foam does, but they are PFAS under some definitions, though not under CERCLA, so “PFAS-free” is a claim to check against the agent named in the fire protection plan. As of May 2025, fifteen states, Illinois among them, had banned the sale of PFAS-containing firefighting foam. [15b] Operators describe a transition to fluorine-free agents, and there is no public, independently verified timeline for completing it. The industry has not published one. That is an accountability failure.

    Claim: Immersion cooling fluids are a new toxic risk. Tier: Contested.

    Immersion cooling submerges servers in non-conductive dielectric fluid and is growing in high-density AI facilities. I found no peer-reviewed lifecycle environmental data for these fluids at commercial scale. The concern is plausible and undocumented, which is why an application for an immersion-cooled facility should name the fluid, the volume on site, the containment, and the disposal route.

    Claim: Data centers are a fire hazard to the neighborhood. Tier: Contested.

    Battery systems at data center campuses are typically installed to NFPA 855, which binds where a jurisdiction has adopted it, and tested against UL 9540A, a method for evaluating thermal-runaway propagation. [16a] Fire is a real event class wherever dense electrical equipment runs. Uptime Institute’s annual outage analyses find power supply, not fire, the leading cause of significant outages, but outage data does not count fires that did not interrupt service. [16] Settling the question would take insurer, fire department, or NFPA incident data, and I found no industry-wide fire dataset. Cardinal’s agreement puts battery storage other than in-rack backup in standalone buildings at least 50 feet from other structures, with a fire safety plan approved by the fire district. [11x]


    What to ask for. Fire suppression agents identified by name in the application, for the generator yard and the data halls separately, since “PFAS-free” means different things for a foam and a clean-agent gas and no public tracking exists of which facilities have completed the AFFF transition. [15b] Illinois banned the sale of PFAS-containing foam, so a new campus should have no reason to resist the question. The diesel tank schedule and the SPCC plan belong in the same submission. [15c] For an immersion-cooled hall, require the fluid’s name, the volume on site, the containment, and the disposal route. For battery storage, require the standard the installation is built to, the UL 9540A test results, the setback, and a fire safety plan approved by the fire district, which Cardinal’s agreement does with a 50-foot standalone-building requirement. [16a][11x] Put the end-of-life disposal of batteries, dielectric fluids, and suppression agents in the decommissioning plan described in the land post.

    The accountability failure. Operators describe a transition to fluorine-free agents, and there is no public, independently verified timeline for completing it. The industry has not published one. A council cannot fix that, but it can refuse to accept “transitioning” as an answer for its own site.

    This is part 12 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: light at night and human health. Last: electromagnetic fields, where the source is the substation and the standards were not built for the question.

    Cover photo: Kecko / Flickr via Wikimedia Commons, CC BY 2.0


    Citations

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [15a] U.S. EPA, “Designation of Perfluorooctanoic Acid (PFOA) and Perfluorooctanesulfonic Acid (PFOS) as CERCLA Hazardous Substances,” Final Rule, effective July 8, 2024. MCLs for PFOA and PFOS set at 4.0 parts per trillion under the concurrent PFAS National Primary Drinking Water Regulation (April 10, 2024). https://www.epa.gov/superfund/designation-perfluorooctanoic-acid-pfoa-and-perfluorooctanesulfonic-acid-pfos-cercla (archived: https://web.archive.org/web/20261002070559/https://www.epa.gov/superfund/designation-perfluorooctanoic-acid-pfoa-and-perfluorooctanesulfonic-acid-pfos-cercla)

    [15b] Pillsbury Winthrop Shaw Pittman LLP, PFAS Observer, “PFAS, HFCs and Related Chemicals in the Data Center Industry,” May 2, 2025 (cross-posted on Gravel2Gavel). “Historically, dry pipe fire suppression systems have used Class B aqueous film-forming foams (AFFF)”; activation “may result in the sudden discharge of large quantities of PFAS-containing AFFF.” https://pfas.pillsburylaw.com/pfas-hfcs-chemicals-data-center-industry/ (archived: https://web.archive.org/web/20261025155111/https://pfas.pillsburylaw.com/pfas-hfcs-chemicals-data-center-industry/)

    [15c] U.S. EPA, Office of Emergency Management, “The SPCC Rule and Recent Amendments,” November 2010 (SPCC basics). Applicability to facilities storing more than 1,320 gallons of oil aboveground with a reasonable expectation of a discharge to navigable waters; secondary containment under 40 CFR 112.7(c) sized to “the typical failure mode, and the most likely quantity of oil that would be discharged”; qualified-facility self-certification available at “10,000 U.S. gallons or less in aggregate aboveground oil storage capacity,” with Professional Engineer certification otherwise. https://www.epa.gov/sites/default/files/2014-05/documents/spcc_basics.pdf (archived: https://web.archive.org/web/20260219022141/https://www.epa.gov/sites/default/files/2014-05/documents/spcc_basics.pdf). Rule text: 40 CFR Part 112.

    [15d] U.S. EPA, “Rescission of Regulatory Determinations and Removal of Related Provisions for Four PFAS Substances,” proposed rule, 91 FR 29413, May 20, 2026, FR Doc. 2026-10085, docket EPA-HQ-OW-2025-0654: would rescind the determinations for PFHxS, PFNA, HFPO-DA, and “mixtures of these three PFAS plus perfluorobutane sulfonic acid (PFBS)”; “This action does not impact the MCLGs, MCLs or the regulatory provisions” for PFOA and PFOS. https://www.federalregister.gov/documents/2026/05/20/2026-10085/rescission-of-regulatory-determinations-and-removal-of-related-provisions-for-four-pfas-substances (archived: https://web.archive.org/web/20261016032522/https://www.federalregister.gov/documents/2026/05/20/2026-10085/rescission-of-regulatory-determinations-and-removal-of-related-provisions-for-four-pfas-substances). U.S. EPA, “Extending the Compliance Deadline for the PFOA and PFOS Maximum Contaminant Levels,” proposed rule, 91 FR 29425, May 20, 2026, FR Doc. 2026-10086, docket EPA-HQ-OW-2025-1742: compliance moved “from April 26, 2029, to April 26, 2031” for systems that submit a request, through a federal exemption under SDWA section 1416(f). https://www.federalregister.gov/documents/2026/05/20/2026-10086/extending-the-compliance-deadline-for-the-pfoa-and-pfos-maximum-contaminant-levels (archived: https://web.archive.org/web/20261007222507/https://www.federalregister.gov/documents/2026/05/20/2026-10086/extending-the-compliance-deadline-for-the-pfoa-and-pfos-maximum-contaminant-levels). EPA proposal page, MCLs “remain 4.0 parts per trillion (ppt) each”: https://www.epa.gov/sdwa/proposed-pfoa-and-pfos-compliance-extension-rule (archived: https://web.archive.org/web/20261016195758/https://www.epa.gov/sdwa/proposed-pfoa-and-pfos-compliance-extension-rule). Comment periods closed July 20, 2026; no final action found as of October 24, 2026.

    [16] Uptime Institute, “Annual Outage Analysis 2025,” May 6, 2025. https://uptimeinstitute.com/about-ui/press-releases/uptime-announces-annual-outage-analysis-report-2025 (archived: https://web.archive.org/web/20260701002954/https://uptimeinstitute.com/about-ui/press-releases/uptime-announces-annual-outage-analysis-report-2025)

    [16a] NFPA, “NFPA 855, Standard for the Installation of Stationary Energy Storage Systems.” Becomes legally enforceable when adopted by the applicable state or local authority having jurisdiction, as with other NFPA standards. UL, “UL 9540A Test Method for Evaluating Thermal Runaway Fire Propagation in Battery Energy Storage Systems,” a test method used to characterize fire propagation risk rather than a standalone regulatory requirement; UL 9540 is the separate product safety standard for energy storage systems. https://www.nfpa.org/codes-and-standards/nfpa-855-standard-development/855 (archived: https://web.archive.org/web/20261017191038/https://www.nfpa.org/codes-and-standards/nfpa-855-standard-development/855) and https://www.ul.com/services/ul-9540a-test-method (archived: https://web.archive.org/web/20261025155719/https://www.ul.com/services/ul-9540a-test-method)

  • Lights On All Night: What Data Center Lighting Does to Wildlife

    Lights On All Night: What Data Center Lighting Does to Wildlife

    Part 10 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    A hyperscale campus is lit to commercial standards 24 hours a day, and artificial light at night does documented things to birds, insects, and the animals that eat them. This is one of the four records in this series that hold at compliant facilities everywhere, alongside construction disruption, farmland conversion, and evaporative wastewater. It is also one of the easiest to address in an approval, and one the opposition material I reviewed never applies to the warehouse across the road.

    This post is short because the evidence is settled and the fix is specific. It rates two claims, one Systemic and one Selective, and names the three specification terms that belong in the photometric plan.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Light Pollution: Wildlife and Habitat

    Claim: Data center lighting harms wildlife. Tier: Systemic. True of any large facility lit through the night.

    Artificial light at night disrupts migratory bird navigation, suppresses insect abundance, alters predator-prey timing, and interferes with pollination, and the peer-reviewed literature on it is substantial. [25] Any large 24-hour campus lit to commercial standards produces the effect, and it matters most near flyways and sensitive habitat. It is addressable with Dark Sky-compliant specifications, full-cutoff fixtures, and motion-activated lighting on non-security perimeters. Cardinal’s developer testified that its lighting would “exceed dark sky standards”; the agreement requires a photometric plan with each building permit. [11y][11x]

    Claim: Data center lighting is uniquely harmful. Tier: Selective.

    The same mechanism applies to warehouse campuses, 24-hour plants, highway interchanges, and big-box retail. In the opposition material I have reviewed, the objection is not applied to them.


    What to ask for. Specify the lighting in the approval instrument: full-cutoff fixtures, Dark Sky-compliant specifications, and motion activation on non-security perimeter lighting, with a photometric plan filed with each building permit, which Cardinal’s agreement already requires. [11x] A developer who testifies that lighting will “exceed dark sky standards” has made a checkable promise, and the photometric plan is where it gets checked. [11y] Where the parcel sits near a flyway, a wetland, or a wooded buffer, ask for the lighting plan to be reviewed against it rather than against the parking lot.

    The honest comparison. The same mechanism applies to warehouse campuses, 24-hour plants, highway interchanges, and big-box retail, and a council that requires full-cutoff fixtures of a data center has a good argument for requiring them of the next distribution center too.

    This is part 10 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: land and habitat. Next: light at night and human health, where the physiology is established and the studies measure something other than a neighbor at a setback.

    Cover photo: NASA, International Space Station / Wikimedia Commons, public domain


    Citations

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [11y] United City of Yorkville, Planning and Zoning Commission, transcript of the public hearing on PZC 2025-08 (Pioneer Development, LLC, Project Cardinal), July 9, 2025, Vitosh Reporting Service (ArchiveCenter Item 6395, “PZC 7-9-25 Minutes & Transcript”). Sworn testimony of Matt McCarron for Pioneer Development: Ashburn homes “within 500 feet of data center campuses in Ashburn have been appreciated by approximately 70 percent over the last decade” (transcript p. 26); “legacy Ashburn data center campuses are built as close as a hundred, 130 feet from residential property lines. We’re committing to a minimum 500-foot setback” (pp. 26 to 27); generator testing “is only going to occur once or twice a year” and generators “are really never used outside of testing” (p. 25); “all backup generators meet Tier 4 final EPA standards” (p. 29); “if it’s curtailed in an emergency, we would be curtailed first and we would have backup generators. We are not going to cause a brownout” (p. 84). https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6395 (archived: https://web.archive.org/web/20261025162533/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6395)

    [25] Gaston, K.J., Visser, M.E., and Hölker, F., “The biological impacts of artificial light at night: the research challenge,” Philosophical Transactions of the Royal Society B: Biological Sciences, Vol. 370, No. 1667, 20140133, May 2015. https://doi.org/10.1098/rstb.2014.0133 (archived: https://web.archive.org/web/20250906061251/https://royalsocietypublishing.org/doi/10.1098/rstb.2014.0133)

  • Light at Night and Human Health: What the Studies Measure and What They Don’t

    Light at Night and Human Health: What the Studies Measure and What They Don’t

    Part 11 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    The physiology is not in dispute. Light at night suppresses melatonin, disrupts circadian rhythm, and the International Agency for Research on Cancer has classified shift work with circadian disruption as probably carcinogenic since 2007. [26] A resident who cites that at a hearing is citing real science. The question this post asks is what population that science describes, and the answer is night-shift workers under overhead lighting and whole metropolitan areas measured by satellite, not a household 500 feet from a full-cutoff fixture.

    Every side of the professional dispute over LED lighting, the American Medical Association and the Illuminating Engineering Society included, treats dose as decisive. [27][27a] This post rates three light-and-health claims against that standard and ends with the gap that is real: there is no federal standard for residential light exposure from adjacent industry and no established safe threshold, which is a reason to specify the fixtures, not a finding of harm.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Light Pollution: Human Health

    The mechanism is established physiology. Artificial light at night suppresses melatonin and disrupts circadian rhythm. The International Agency for Research on Cancer classified shift work involving circadian disruption as probably carcinogenic to humans (Group 2A) in 2007, confirmed in 2010 and 2020. [26] The American Medical Association’s 2016 policy on high-intensity LED street lighting found brighter residential nighttime lighting associated with reduced sleep, impaired daytime functioning, and obesity. [27] Epidemiological reviews find associations between outdoor light at night and breast cancer, type 2 diabetes, cardiovascular disease, and depression in large cohorts. [28] The claims built on that mechanism are what get tiered.

    Claim: The health studies show what living near a lit data center does to you. Tier: Exaggerated. Occupational and regional exposure applied to a single facility.

    The literature draws on two populations: night-shift workers under high-intensity light for long hours, and whole metropolitan populations correlated with satellite-measured light across regions. Neither describes a resident at a setback from one facility. Direct light falls off roughly with the square of distance, though skyglow and reflected light do not. The AMA grounds its concern in intensity, spectrum, duration, and timing, and the Illuminating Engineering Society, which disputes the AMA’s use of color temperature as a proxy, argues that the quantity of light reaching the eye and the duration matter at least as much. [27][27a] Every side of that professional dispute treats dose as decisive. A full-cutoff fixture at a 500-foot setback is not a night shift under overhead lighting.

    Claim: Data center lighting is a health risk other lit buildings aren’t. Tier: Selective.

    A three-shift warehouse lights comparable or greater exterior acreage, and the mechanism applies identically. In the opposition material I have reviewed, the objection does not.

    Claim: This facility’s lights will cause cancer in its neighbors. Tier: Contested.

    The population studies measure aggregate light across neighborhoods, not one facility’s contribution to one bedroom, and an NCI epidemiologist writing in the British Journal of Cancer has noted that mixed findings are hard to interpret because individual exposure assessment is unresolved. [28a] I found no peer-reviewed study that measured health outcomes attributable to light from a single industrial facility. There is also no federal standard for residential light exposure from adjacent industry and no established safe threshold. Those are real gaps. Neither establishes harm at any specific facility.


    What to ask for. The same specification as the wildlife post, because the fix is the same: full-cutoff fixtures, Dark Sky-compliant specifications, motion activation on non-security perimeters, and a photometric plan with each building permit that shows the light level at the nearest residential property line and bedroom-window height. [11x] That last number is the one the health literature cannot supply for a single facility and the one a neighbor is actually asking about. If a council wants to go further, a measured light-at-night baseline at the nearest homes, taken with the acoustic baseline, costs little and gives any later complaint a comparison.

    What the record does not show. I found no peer-reviewed study that measured health outcomes attributable to light from a single industrial facility, and an NCI epidemiologist has written that individual exposure assessment in this literature is unresolved. [28a] Those are gaps, not clearances. Neither establishes harm at any specific facility, and neither should be cited as if it did.

    This is part 11 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: light pollution and wildlife. Next: chemical hazards, from PFAS foam to dielectric fluid to the battery building.

    Cover photo: Almanta / Wikimedia Commons, CC BY-SA 4.0


    Citations

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [26] International Agency for Research on Cancer, IARC Monographs on the Evaluation of Carcinogenic Risks to Humans, Volume 98: Painting, Firefighting, and Shiftwork. Lyon: IARC, 2010. Classification of shift work involving circadian disruption as Group 2A (probably carcinogenic to humans). Reaffirmed in Volume 124 (Night Shift Work), 2020. https://publications.iarc.who.int/Book-And-Report-Series/Iarc-Monographs-On-The-Identification-Of-Carcinogenic-Hazards-To-Humans/Night-Shift-Work-2020 (archived: https://web.archive.org/web/20261017154102/https://publications.iarc.who.int/Book-And-Report-Series/Iarc-Monographs-On-The-Identification-Of-Carcinogenic-Hazards-To-Humans/Night-Shift-Work-2020)

    [27] American Medical Association Council on Science and Public Health, “Human and Environmental Effects of Light Emitting Diode (LED) Community Lighting,” CSAPH Report 2-A-16, adopted June 2016 (AMA Policy H-135.927). https://www.ama-assn.org/sites/ama-assn.org/files/corp/media-browser/public/about-ama/councils/Council%20Reports/council-on-science-public-health/a16-csaph2.pdf (archived: https://web.archive.org/web/20260909024644/https://www.ama-assn.org/sites/ama-assn.org/files/corp/media-browser/public/about-ama/councils/Council%20Reports/council-on-science-public-health/a16-csaph2.pdf)

    [27a] Illuminating Engineering Society, “PS-09-17: IES Board Position on AMA CSAPH Report 2-A-16, Human and Environmental Effects of Light Emitting Diode (LED) Community Lighting.” IES formally disagreed with the AMA’s use of correlated color temperature (CCT) as a proxy for circadian health impact, arguing that quantity of light at the retina and duration of exposure are established, at least equally important inputs. https://ies.org/advocacy/ps-09-17/ (archived: https://web.archive.org/web/20261010004135/https://ies.org/advocacy/ps-09-17/) Readable report of the position: John Wallace, Laser Focus World, “The Illuminating Engineering Society disagrees with AMA policy statement on spectral content of LED outdoor lighting,” August 2, 2017 (IES: CCT “is inadequate for the purpose of evaluating possible health outcomes”; key factors are “the quantity of light at the retina of the eye and the duration of exposure”). https://www.laserfocusworld.com/articles/2017/08/the-illuminating-engineering-society-disagrees-with-ama-policy-statement-on-spectral-content-of-led-outdoor-lighting.html (archived: https://web.archive.org/web/20261025162433/https://www.laserfocusworld.com/articles/2017/08/the-illuminating-engineering-society-disagrees-with-ama-policy-statement-on-spectral-content-of-led-outdoor-lighting.html)

    [28] Bozejko, M., Tarski, I., and Malodobra-Mazur, M., “Outdoor artificial light at night and human health: A review of epidemiological studies,” Environmental Research, Vol. 218, Article 115049, 2023. https://doi.org/10.1016/j.envres.2022.115049 (archived: https://web.archive.org/web/20240415131632/https://www.sciencedirect.com/science/article/abs/pii/S0013935122023763)

    [28a] Jones, R.R., “Exposure to artificial light at night and risk of cancer: where do we go from here?” British Journal of Cancer, Vol. 124, pp. 1-2, January 2021 (National Cancer Institute, NIH). https://doi.org/10.1038/s41416-020-01231-7 (archived: https://web.archive.org/web/20231009234814/https://www.nature.com/articles/s41416-020-01231-7)

  • Farmland to Server Hall: The Land Question Is a Values Question

    Farmland to Server Hall: The Land Question Is a Values Question

    Part 9 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    Data centers in Northern Illinois go on farmland. Corn and soybeans are the prior use on nearly every parcel in the Eldamain corridor, and the conversion is permanent. That is the one environmental claim in this series that is true everywhere, and it is also the one that is least about data centers. The decision in front of a council is whether to rezone farmland for industry at all, and that is a judgment about land, not a finding about the building.

    This post rates two land claims. The first, that data centers are taking farmland, holds. The second, that a data center is the worst thing you could put on the parcel, does not survive comparison with the warehouse campus that is usually the alternative, though no controlled study has measured the two side by side. It ends with what Project Cardinal’s approval actually requires on the land, and with the end-of-life condition that no data center approval I reviewed contains and that Illinois already requires of solar and wind.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Land and Habitat

    Claim: Data centers are taking our farmland. Tier: Systemic.

    True, and permanent. Data centers in Northern Illinois are typically sited on agricultural land, with corn and soybeans the dominant prior use. The decision in front of most councils is therefore whether to rezone farmland for industry at all, and that is a values question about land, not a finding about data centers. Where the alternative is continued agriculture, the questions that matter are prime farmland loss, drainage district and field tile disruption, impervious cover, detention basin maintenance, and post-construction stormwater performance. Those deserve their own treatment and do not get it here.

    Claim: A data center is the worst thing you could put on this land. Tier: Selective.

    Where a parcel is already industrial or certain to be, the comparison is another industrial use, and the record does not support ranking data centers worst. A warehouse distribution campus generates its own footprint: heavy truck traffic, disproportionately at night, diesel particulate at loading docks, and refrigeration noise. [33a] No controlled study has measured the two uses against each other on matched parcels. On known characteristics, they differ in kind: a data center’s operating impacts are continuous and mechanical, a warehouse’s vehicular and peak-driven, and which a neighbor would rather live beside depends on what that neighbor is sensitive to. A council weighing a parcel can fairly ask what use or site would be acceptable. If the answer is none, the objection is to the building or to a constraint every local site shares, such as transmission, water, or residential proximity, and each is legitimate argued as what it is.

    The Cardinal approval shows what conditions on the land can look like. The PUD agreement approved November 10, 2025 carries a 100-foot landscape buffer on all four road frontages with a 12-foot berm facing homes and 8 feet elsewhere, a 500-foot separation from any home or business occupied on the approval date, and a 78-foot height limit including rooftop equipment. [11x] Shaw Local’s account adds 4,900 new trees and setbacks of 625 and 1,200 feet from the two nearest subdivisions, from the plan exhibits. [11m] The record I located has no stormwater performance data and no measure of net habitat outcome.


    What to ask for. Treat the farmland question as the values question it is and argue it as one: prime farmland loss, drainage district and field tile disruption, impervious cover, detention basin maintenance, and post-construction stormwater performance are the questions that matter where the alternative is continued agriculture, and they deserve their own study. Where the parcel is going industrial regardless, compare the uses honestly. A warehouse campus brings night truck traffic, dock diesel, and refrigeration noise; a data center brings continuous mechanical load. [33a]

    Require an end-of-life plan and the money to execute it. Illinois already requires a decommissioning plan and financial assurance as a condition of county siting approval for commercial solar and wind, with the plan filed at application and the security posted before the building permit. [42] Data centers are permitted with no equivalent in the approvals I reviewed. The buildings are refit on multi-year hardware cycles, and whether a campus built for one generation of hardware suits the next is a question no approval asked. Require a decommissioning plan covering demolition, foundation and slab removal, restoration of pervious surface, and disposal of batteries, dielectric fluids, and fire suppression agents, with financial assurance sized to that plan and adjusted periodically. This is the condition with the longest tail and the one least likely to be raised at the hearing where it matters.

    What nobody knows. I found no controlled comparison of data center thermal, noise, or air quality impacts against comparably sized warehouses or plants on matched parcels, and none against continued agriculture where the decision is whether to rezone at all.

    This is part 9 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: thermal effects. Next: light pollution and wildlife, a real effect of any campus lit through the night.

    Cover photo: U.S. Forest Service / Wikimedia Commons, public domain


    Citations

    [11m] Joey Weslo, Shaw Local News Network (Kendall County Now), “Yorkville OKs ‘larger than Central Park in New York’ data center campus,” November 14, 2025. Unanimous approval of the Project Cardinal PUD on November 10, 2025: 4,900 new trees; a landscaped 12-foot berm near residential properties narrowing to eight feet elsewhere; 625-foot setback from Bristol Bay and 1,200 feet from Equestrian Estates; 78-foot height limit including rooftop equipment; generator testing only during daytime; city monitoring of light pollution; phased construction under a 20-year PUD. https://www.shawlocal.com/kendall-county-now/2025/11/11/yorkville-oks-1037-acre-project-cardinal-data-center/ (archived: https://web.archive.org/web/20260415165443/https://www.shawlocal.com/kendall-county-now/2025/11/11/yorkville-oks-1037-acre-project-cardinal-data-center/)

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [33a] LOCUS (locusdata.io), “Impacts of warehouses and ports on truck traffic,” analysis of Arizona truck traffic data documenting disproportionate nighttime truck activity around logistics facilities. [Data-vendor blog, not peer reviewed.] https://locusdata.io/blog/impacts-of-warehouses-and-ports-on-truck-traffic (archived: https://web.archive.org/web/20260416171405/https://locusdata.io/blog/impacts-of-warehouses-and-ports-on-truck-traffic)

    [42] 55 ILCS 5/5-12020, Counties Code, commercial wind energy facilities and commercial solar energy facilities: county siting standards including a deconstruction (decommissioning) plan and financial assurance, implemented through the Agricultural Impact Mitigation Agreement with the Illinois Department of Agriculture. Accessible county implementation: Macon County Code, Chapter 156, Commercial Solar Energy Facility Siting: applicant “must submit a decommissioning plan with cost estimation to the county as part of the siting application” and “post the required financial assurances for the benefit of the county” before a building permit; “The decommissioning agreement and financial assurances shall comply with 55 ILCS 5/5-12020.” https://codelibrary.amlegal.com/codes/maconcounty/latest/maconcounty_il/0-0-0-8916 (archived: https://archive.org/details/macon-county-code-chapter-156-2026-10-25, the page text as displayed October 25, 2026, uploaded because the Wayback Machine cannot capture the code library’s JavaScript page)

  • Ten Years of Trucks: Construction Is the Impact Neighbors Meet First

    Ten Years of Trucks: Construction Is the Impact Neighbors Meet First

    Part 7 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    Before any generator runs or any fan spins, the trucks come. Construction is the environmental impact residents encounter first, raise most often at hearings, and, on a phased hyperscale campus, live beside longest. Project Cardinal’s agreement describes about ten years of build-out and calls the phasing plan “advisory only and non-binding.” [11x]

    Most of this record is not a data center record. Dust, haul traffic, and construction noise come with any large project, and a loaded gravel truck weighs the same on Eldamain Road as it does in Saline Township, Michigan. What is specific is duration, and the two site-specific hazards, blasting and the loss of a tree buffer, that do not happen everywhere. This post rates three construction claims and ends with the conditions that belong in the approval instrument, in the right order, which is before the trucks start running.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Construction

    Claim: Building a data center disrupts the neighborhood for years. Tier: Systemic.

    Construction is the impact residents encounter first, experience longest, and raise most often at hearings, and the pattern repeats across states. In Saline Township, Michigan, gravel haulers serving the Oracle and OpenAI campus drew complaints about speeding, noise, dust, and damage to newly repaved streets. [37] Near Microsoft’s Mount Pleasant, Wisconsin campus, neighbors reported construction noise, dust, light, and truck traffic through successive build phases. [38] In Middlesex Township, Pennsylvania, residents reported a blast that shook a house across the road, despite pre-blast surveys and seismographs. [39] A Louisa County, Virginia homeowner sued Amazon in July 2026 over dump truck traffic, dust, and water discoloration. [40] In Spartanburg County, South Carolina, residents said tree clearing removed a sound buffer that had shielded them from existing noise. [41] Dust behaves the same in Illinois as in Michigan, and a loaded gravel truck weighs the same on Eldamain Road.

    Duration is what changes the experience, and it attaches to large phased campuses of any kind, of which hyperscale data centers are one. Project Cardinal’s agreement describes a build-out of about ten years and calls the phasing plan “advisory only and non-binding.” [11x] Mount Pleasant residents are living beside phase three. The “temporary disruption” framing assumes an end date phased campuses do not offer. Yorkville’s settlement with a resident in the first Cardinal lawsuit, approved 5-1 on June 23, 2026, requires each construction phase to be substantially complete before the next begins, with exceptions for circumstances beyond the developer’s control. [11o][11k]

    Claim: Haul trucks and dust are a data center problem. Tier: Selective.

    Haul traffic, dust, and construction noise come with any large project, and warehouses, hospitals, subdivisions, and highway rebuilds are rarely treated as environmental questions for it. Blasting, well damage, and clearing an established tree buffer are site-specific and do not happen everywhere. Apart from those and the duration, most of the construction complaint is a large-project complaint.

    Claim: Living next to a data center means dust and trucks. Tier: Misattributed.

    Dust, haul traffic, and blasting end when construction ends. Describing them as what an operating data center is like conflates a build phase with a facility. On a ten-year campus, the distinction is thin for the neighbor, which is why phasing conditions matter more here than anywhere else in this series.


    What to ask for. Write the construction conditions into the approval. Designated haul routes that avoid residential streets and school zones. Delivery hour limits. A pre-construction road survey with developer-funded repair obligations. Dust suppression with a named enforcement contact. Pre-blast structural surveys with seismograph monitoring where blasting is planned, and a private-well baseline within a defined radius where excavation or blasting is near homes on wells, which is the subject of the water quality post. Phase-completion requirements, so a decade of building is not a decade of simultaneous activity; Yorkville’s June 2026 settlement with a resident requires each Cardinal phase to be substantially complete before the next begins, with exceptions for circumstances beyond the developer’s control. [11o][11k] Saline Township negotiated traffic enforcement after the trucks started running, which is the wrong order. [37]

    The honest comparison. A warehouse campus, a hospital, or a highway rebuild produces the same dust and the same trucks, and they are rarely treated as environmental questions for it. What makes a hyperscale campus different is that its build phase can outlast a mortgage. Conditions that assume a construction end date are written for a different kind of project.

    This is part 7 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: noise. Next: thermal effects, where Phoenix has a peer-reviewed measurement and Illinois has none.

    Cover photo: Joseph Gage / Flickr via Wikimedia Commons, CC BY-SA 2.0


    Citations

    [11o] United City of Yorkville, City Council Packet, June 23, 2026, agenda item EDC 2026-31 (Project Cardinal, Pioneer Development LLC). Community Development Director’s memo dated June 3, 2026, packet pp. 369 to 371: Utility and Infrastructure Agreement and Development Agreement approved March 10, 2026 by Ordinance No. 2026-23 (executed copy, Section 4.1: the City “will provide water” at 42,000 gpd average day and 71,400 gpd maximum day, overuse billed at twice the volumetric rate; Section 3.6: HVO or biodiesel for generator testing; no well provision; https://www.yorkville.il.us/DocumentCenter/View/13590/Ordinance-2026-23—need-signed-agreements?bidId= (archived: https://web.archive.org/web/20261025151443/https://www.yorkville.il.us/DocumentCenter/View/13590/Ordinance-2026-23—need-signed-agreements?bidId=)); closing-notice deadline extension from July 1, 2026 to December 31, 2027. Draft Memorandum of Understanding (Pioneer Development redline dated May 21, 2026), packet pp. 378 to 381, Section 4.1 Water Allocation: “The City acknowledges that the provisions of adequate amounts of potable water is essential for the development of the Project”; “(Average Day) 42,000 gallons per day (Maximum Day) 71,400 gallons per day”; penalty “equal to two times the then-existing volumetric water rate on the difference between the actual average day and the estimated average day of 42,000 gallons for the entire billing cycle”; for any day over 71,400 gallons, the same double rate “until compliance with the water allocation standards are met or further improvements to the water service system are completed at the sole cost of the Developer.” Same packet, City Administrator memo dated June 18, 2026, p. 233, and Conditional Settlement Agreement and Releases, Bryan v. Yorkville, Kendall County Case No. 2025 CH 000028, from p. 239. https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6803 (archived: https://web.archive.org/web/20261025162608/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6803). Adoption: Minutes of the Regular Meeting of the City Council, June 23, 2026 (as reproduced in the July 14, 2026 council packet): Ordinance 2026-43 approving the conditional settlement, roll call 5-1 (Corneils nay); Ordinance 2026-44 approving the first amendment to the annexation agreement, 6-1; Ordinance 2026-45 approving the memorandum of understanding, 5-1 (Corneils nay). https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6824 (archived: https://web.archive.org/web/20261025162615/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6824)

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [11k] Shaw Local (Kendall County Now), “Yorkville close to reaching settlement on resident’s lawsuit over 1,037 acre data center,” March 21, 2026, and Yorkville Herald, “Yorkville Council to Consider Settlement in Project Cardinal Lawsuit,” June 19, 2026. Resident John Bryan filed suit October 28, 2025 alleging noise and property value harm; Pioneer Development LLC intervened as a defendant December 19, 2025; the June 23, 2026 council agenda included a conditional settlement requiring that “each phase of the project is substantially complete before construction of the next phase begins,” “with limited exceptions for circumstances beyond the developer’s control.” https://www.shawlocal.com/kendall-county-now/2026/03/21/yorkville-close-to-reaching-settlement-on-residents-lawsuit-over-1037-acre-data-center/ (archived: https://web.archive.org/web/20260804170512/https://www.shawlocal.com/kendall-county-now/2026/03/21/yorkville-close-to-reaching-settlement-on-residents-lawsuit-over-1037-acre-data-center/) and https://www.yorkvilleherald.com/articles/yorkville-council-to-consider-settlement-in-project-cardinal-lawsuit (archived: https://web.archive.org/web/20260908214340/https://www.yorkvilleherald.com/articles/yorkville-council-to-consider-settlement-in-project-cardinal-lawsuit)

    [37] Planet Detroit, “Saline residents blast Oracle data center construction,” March 17, 2026, and FOX 2 Detroit, “Saline Twp. data center construction causing noise complaints, Oracle responds.” Resident complaints of speeding gravel haulers, noise, dust, and road damage; Saline Mayor Brian Marl met with contractor Walbridge and pledged additional traffic enforcement. https://planetdetroit.org/2026/03/saline-data-center-traffic/ (archived: https://web.archive.org/web/20261024150438/https://planetdetroit.org/2026/03/saline-data-center-traffic/)

    [38] Wisconsin Public Radio, “Microsoft sued over noise complaints at new Mount Pleasant data center facility,” July 2, 2026. Residents near the operating facility and the phase-three construction site reported construction noise, dust, light pollution, and truck traffic. https://www.wpr.org/news/microsoft-sued-noise-complaints-at-new-mount-pleasant-data-center (archived: https://web.archive.org/web/20261016202631/https://www.wpr.org/news/microsoft-sued-noise-complaints-at-new-mount-pleasant-data-center)

    [39] CBS 21 / local21news, “What’s it like living next to a data center construction site? Residents weigh in,” Middlesex Township, Cumberland County, Pennsylvania, April 28, 2026. Township-reported construction hours of 6 a.m. to 6 p.m.; contractors conducted pre-blast inspections documenting existing conditions in nearby homes and installed seismographs to measure ground movement. https://local21news.com/news/local/whats-it-like-living-next-to-a-data-center-construction-site-middlesex-township-acres-township-officials-country-club-road (archived: https://web.archive.org/web/20260820125637/https://local21news.com/news/local/whats-it-like-living-next-to-a-data-center-construction-site-middlesex-township-acres-township-officials-country-club-road)

    [40] Virginia Mercury, “Brown water, dust and loud noises: Louisa homeowner sues Amazon over data center construction,” July 28, 2026. Allegations are unadjudicated. https://virginiamercury.com/2026/07/28/brown-water-dust-and-loud-noises-louisa-homeowner-sues-amazon-over-data-center-construction/ (archived: https://web.archive.org/web/20260730185048/https://virginiamercury.com/2026/07/28/brown-water-dust-and-loud-noises-louisa-homeowner-sues-amazon-over-data-center-construction/)

    [41] Fox Carolina, “Spartanburg residents say data center construction is already disrupting their lives,” July 23, 2026. Residents reported dust and said clearing of several acres of trees removed a sound buffer. https://www.foxcarolina.com/2026/07/23/spartanburg-residents-say-data-center-construction-is-already-disrupting-their-lives/ (archived: https://web.archive.org/web/20260902163554/https://www.foxcarolina.com/2026/07/23/spartanburg-residents-say-data-center-construction-is-already-disrupting-their-lives/)

  • Does a Data Center Warm the Neighborhood? Phoenix Says Yes. Illinois Is Unstudied.

    Does a Data Center Warm the Neighborhood? Phoenix Says Yes. Illinois Is Unstudied.

    Part 8 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    Every watt a data center draws leaves as heat, and an air-cooled campus puts that heat into the air at the fence line. Whether neighbors feel it is a newer question than the others in this series, and it has two very different answers in circulation: a peer-reviewed Arizona State University study that drove sensors upwind and downwind of four Phoenix facilities and measured up to 4°F in summer, and a satellite preprint claiming 2°C for miles around AI data centers worldwide. [14a][14b]

    The two are not the same kind of evidence, and the second has a problem its method cannot resolve. This post rates three thermal claims: the Phoenix measurement, the satellite preprint, and the claim that a heat island is coming to a corridor that switched to air cooling to save water. The Yorkville projects use the design the ASU study measured. What differs is the climate, and nobody has measured an Illinois July.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Thermal Effects

    Claim: Data centers heat the air around them. Tier: Regional. Documented at air-cooled facilities in Phoenix.

    Air-cooled data centers in Phoenix measurably warm the air downwind, by up to 4°F (2.2°C) in summer. A peer-reviewed Arizona State University study measured ambient air temperature at four Phoenix-area facilities from June through October 2025 with vehicle-mounted sensors driven simultaneously upwind and downwind. Average downwind increases ran 1.3 to 1.6°F, detectable up to about a third of a mile from the perimeter. It is the first study to measure air temperature directly rather than satellite-derived land surface temperature. [14a]

    Claim: AI data centers raise temperatures 2°C for miles around. Tier: Contested. A satellite preprint, not peer-reviewed.

    A preprint first posted to arXiv in March 2026 (Marinoni et al.) reports that satellite-measured land surface temperature rises about 2°C on average after an AI data center starts operating, with effects detectable up to 10 km away and an average 1°C increase out to 4.5 km, and estimates that more than 340 million people could be affected. [14b] It measures ground surface temperature, not the air people experience. The authors say they filtered out seasonality and “other types of anthropogenic activities,” but the paper does not describe a control for the facility’s own conversion of fields to roofs and pavement, which by itself raises satellite-measured surface temperature and is already in place when operations start. [14b][21] The result may be real, overstated, or largely an artifact of construction, and the method as described cannot tell which.

    Claim: A data center will create a heat island here. Tier: Contested. Unstudied in a cold climate, not shown absent.

    The Yorkville projects moved to air cooling to cut water use, so the corridor uses the design the ASU study measured. What differs is the climate. Whether a 4°F downwind effect measured in a Phoenix summer appears at all in an Illinois July has not been studied, and no published evidence supports predicting a neighborhood heat island here.


    What to ask for. This is the record with the least to require and the most to measure. Ask the applicant to state the cooling design and the heat rejection capacity at full build-out, which is already needed for the noise and power questions. If a council wants a thermal baseline, it is the cheapest of the baselines in this series: ambient air temperature at the property line and at the nearest homes across a summer before construction, taken the way the ASU team took theirs, so that a later claim in either direction can be checked against a number rather than a satellite image. [14a] No approval I reviewed asks for one, and no rule requires it.

    What nobody knows. Whether a 4°F downwind effect measured in a Phoenix summer appears at all in an Illinois July has not been studied. Northern Illinois has far more cool-weather hours, which changes the fan load for much of the year, and no published evidence supports predicting a neighborhood heat island here. It also does not support ruling one out on design-day afternoons.

    This is part 8 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: construction. Next: land and habitat, where the real question is whether to rezone farmland at all.


    Citations

    [14a] Sailor, D.J., Abolhassani, S.S., and Martin, E., “Data Center Waste Heat as an Emerging Urban Thermal Hazard: First Field Measurements of Neighborhood-Scale Air Temperature Impacts,” ASME Journal of Engineering for Sustainable Buildings and Cities, Vol. 7, No. 2, May 2026. https://asmedigitalcollection.asme.org/sustainablebuildings/article/7/2/024501/1233035/Data-Center-Waste-Heat-as-an-Emerging-Urban (archived: https://web.archive.org/web/20261005124524/https://asmedigitalcollection.asme.org/sustainablebuildings/article/7/2/024501/1233035/Data-Center-Waste-Heat-as-an-Emerging-Urban) The journal page sits behind a bot check and was not read directly; study details are confirmed through Interesting Engineering, May 18, 2026: four facilities from a 36 MW Mesa building to a 169 MW Chandler campus; June 18 to October 25, 2025; vehicle-mounted sensors with simultaneous upwind and downwind readings; up to 4°F, average 1.3 to 1.6°F; primarily air-cooled, condenser discharge 14 to 25°F above ambient; detectable up to a third of a mile; “the first to directly measure air temperatures both upwind and downwind of data centers in real time.” https://interestingengineering.com/science/data-center-phoenix-temperature (archived: https://web.archive.org/web/20260519113752/https://interestingengineering.com/science/data-center-phoenix-temperature)

    [14b] Marinoni, A., Cambria, E., Lin, W., et al., “The data heat island effect: quantifying the impact of AI data centers in a warming world,” arXiv:2603.20897, submitted March 21, 2026, revised April 21, 2026 (v3). Not peer-reviewed. Abstract: land surface temperature “increases by 2°C on average after the start of operations”; “more than 340 million people could be affected.” Full text: impact “reaches up to 10 km distance”; “an average monthly LST increase of 1 °C can be measured up to 4.5 km”; filtering for “seasonality effects” and “other types of anthropogenic activities in the surrounding of AI hyperscalers”; “over 6733 data points.” https://arxiv.org/abs/2603.20897 (archived: https://web.archive.org/web/20261013004906/https://arxiv.org/abs/2603.20897)

    [21] Andy Masley, “Data centers’ heat exhaust is not raising the land temperature around where they’re built,” The Weird Turn Pro (Substack), March 31, 2026. [Commentary, not peer-reviewed.] https://blog.andymasley.com/p/data-centers-heat-exhaust-is-not (archived: https://web.archive.org/web/20261013004907/https://blog.andymasley.com/p/data-centers-heat-exhaust-is-not)

  • Chandler’s Hum, Yorkville’s Monitors, and the Infrasound Claim

    Chandler’s Hum, Yorkville’s Monitors, and the Infrasound Claim

    Part 6 of 13 in Thirteen Records. The long article, Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them., rates thirteen kinds of environmental complaint against data centers. This series takes them one at a time.

    I work at a local ISP in Northern Illinois and co-founded FD-IX, an internet exchange. I have no customer, vendor, or interconnection relationship with any facility or developer named here and no financial position in any of them beyond broad-market index funds. My industry grows with infrastructure investment in a general way, which is an indirect interest; the full disclosure is at the top of the complete article.


    Noise is the complaint Virginia’s own auditors found behind most data center disputes, and it is the one Yorkville’s staff heard first when they called Loudoun County for advice. [4][11w] It is also the category that holds the widest spread of claims in this series: a documented siting failure in Chandler, Arizona, a developer’s promise made under oath, a resident’s health warning built from general material, and a mechanism, inaudible infrasound, that has no evidentiary basis at all.

    What makes noise different from the other twelve records is that Yorkville wrote the test into its approvals. Continuous monitors, a final study on measured data for the actual equipment, mitigation on any exceedance. Whether neighbors hear these campuses will be a measured fact. This post rates five noise claims, reads Project Steel’s own acoustic study, which found the base design over both the city code and the state limits, and explains why a water concession usually arrives with a noise cost attached.

    How the ratings work. Each complaint below is stated the way it usually arrives at a hearing and rated on the scale the full article uses. Systemic: documented at compliant facilities across multiple geographies. Regional: real, but only under specific geographic or operational conditions. Isolated: documented at one or few facilities due to misconduct or atypical design. Exaggerated: the concern is real, but the figures are permit ceilings or worst cases, not operating norms. Selective: a legitimate concern applied only to data centers, not to comparable land uses. Misattributed: the harm is real, but the source, geography, or cause is wrong. Contested: a plausible mechanism exists, but causal documentation at compliant facilities does not. Fabricated: no credible evidentiary basis exists. Where I say I found no record of something, that means a search of public sources through October 2026, not paid databases or records requests.


    Noise

    Claim: Data centers are loud. Tier: Regional. Depends on cooling design, climate, and distance.

    Virginia’s JLARC study, the only state-level examination of the question I located, found that “a large majority of data centers do not generate noise complaints because of their location or design,” that whether noise carries past the property line depends on design and cooling type, and that the noise behind resident complaints measured roughly 40 to 59 decibels, “rarely loud enough to violate noise ordinances.” The complaint is the constancy, not the volume. [4] Complaint counts are not measurements, so the finding supports something narrower than “data centers are quiet”: complaint-level noise is not inevitable. DeKalb’s city manager said in August 2026 the city has had no complaints about noise or any other pollution from Meta’s campus, roughly a mile from the nearest homes. [10d] Air-cooled facilities run fans continuously, and in hot climates they run at or near full speed for long stretches. Variable-speed fans, barriers, berms, and setbacks in the hundreds of feet are available mitigations, and I found no survey of how widely they are deployed. One vendor reports a 97.5% reduction in tonal fan noise from impeller redesign, a result it published itself rather than one independently verified. [14]

    Claim: Chandler shows data centers make neighborhoods unlivable, and Chandler is coming to Yorkville. Tier: Misattributed.

    Chandler’s noise problem was real. In early 2019, residents near Dobson and Queen Creek roads described the hum from a CyrusOne campus’s 24 chillers as “a blender on steroids,” and one said she had not slept a full night in about two and a half years. CyrusOne said it complied with the city’s ordinances. [36b] The cause was a zoning framework with no data center provisions applied to a facility of this scale near homes: city staff later wrote that the lack of rules “has caused confusion for both the data center industry and Chandler residents,” and the council adopted a data center zoning amendment, Ordinance No. 5033, in December 2022. It sets no decibel limit. It requires a third-party sound study at the nearest residential property line before the first neighborhood meeting, mitigation so operation does not exceed the ambient level that study found, post-construction studies at peak operation annually for five years, an on-site liaison for noise complaints, and generator testing on weekdays between 9 a.m. and 5 p.m. with 24 hours’ public notice. [36a] That is a siting failure answered with a measurement, not a property of the building type.

    Carrying it to Yorkville also skips the climate. Northern Illinois has far more cool-weather hours than Phoenix, which changes the cooling load and the fan speed for much of the year, though the economizer inputs that would quantify it are not public for any proposal here. It does not settle Yorkville the other way: Project Steel is air-cooled, and an air-cooled campus here still runs at full output on hot, humid days. Chandler’s record cannot stand in for design-day sound levels at a Yorkville property line. Only the applicant’s acoustic data can.

    Claim: Neighbors “are not going to hear this campus.” Tier: Contested. A promise the conditions will test.

    This is the developer’s claim, made under oath by Project Cardinal’s representative at the July 2025 hearing: “They are not going to hear it during operation, they are not going to hear it during generator testing.” [11y] The neighboring project’s own consultant shows why that needs measuring. Prologis’s study for Project Steel measured average baseline (L90) levels of 39 to 42 dBA and found the base design would put 49 to 65 dBA on nearby homes, over both the city code and the state limits that govern the unincorporated residences around the site. [11d] Quieter chillers and sound walls bring it within the city’s 60 dBA day and 50 dBA night limits; for the state’s roughly 44 dBA nighttime limit, the study claims only “substantial compliance,” and only with the lowest-noise equipment. [11d][11s] Those state limits are the Illinois Pollution Control Board’s octave-band ceilings for sound crossing onto residential land, such as 61 dB at 63 Hz and 35 dB at 1,000 Hz by night from a commercial source; they apply everywhere in Illinois, including where no city ordinance reaches, and they are enforced by complaint after the fact. [41a] CyrusOne’s study for its 228-acre Yorkville campus projected 30 to 45 dBA at nearby homes at night against background levels of 38 to 41 dBA: within code, and at the top of that range, above the existing background. [11q] And CyrusOne’s older Aurora campus, approved around 2017, drew enough complaints, mainly about rooftop fans, that Aurora wrote new rules. [11q][11t][11u]

    Yorkville wrote the test into the approvals. Steel’s agreement puts city-chosen continuous monitors in at the start of each construction phase for the life of the project, sets the city code with a 10 dBA penalty for tonal noise as the limit, requires mitigation on any exceedance, and requires the final study to use measured sound data for the actual equipment. [11s] CyrusOne’s amended agreement requires continuous monitoring and a reviewed noise study with each building permit, and records that the city’s ordinance exempts emergency generator operation. [11q] Cardinal’s carries continuous monitoring and a report within 60 days of each building going live. [11x] Whether neighbors hear these campuses will be a measured fact, which is the point.

    Claim: A data center this size “could cause significant noise pollution in this area to residents, causing neurological and mental health stressors in addition to medical issues and complications.” Tier: Contested.

    That is the Yorkville resident’s March 2025 claim, supported with general material on noise and diesel exhaust rather than anything about this site. [11w] The measurable question is the level and duration of sound at the home, which the Yorkville conditions now require someone to measure. Whether a given level at a given home harms health is not something the sources reviewed for this series settle, and it is not something a general article about noise can settle for a specific campus either.

    Claim: Data centers harm health through infrasound you can’t hear. Tier: Fabricated.

    The claim is that facilities emit sound below 20 Hz, below the threshold of hearing, that causes headaches, insomnia, nausea, and anxiety through an inaudible mechanism. The mechanism is where it fails. Infrasound becomes audible at high levels, about 97 dB at 10 Hz and 107 dB at 4 Hz for a typical young adult [32a], and a review of the literature found “no reliable evidence that infrasounds below the hearing threshold produce physiological or psychological effects.” [32a] I found no facility-specific measurement showing sub-20 Hz levels anywhere near the hearing threshold at a residential setback. A 2019 NIOSH health hazard evaluation, citing a 1982 review, reported no evidence of hearing threshold shifts from continuous exposure at 118 dB or less for 24 hours. [32]

    The closest population evidence comes from wind turbines, and it is comparison evidence only: turbines are a different source, and the study related health outcomes to calculated turbine noise levels, not to infrasound measured on its own. Health Canada’s study of 1,238 households near 399 turbines, published in peer-reviewed form in 2016, found self-reported illness, including migraines, tinnitus, dizziness, and poor sleep, unrelated to calculated turbine noise, and found the objectively measured outcomes, hair cortisol, blood pressure, resting heart rate, and actigraph-measured sleep, unrelated to it as well. Annoyance did rise with exposure: each 5 dB increase raised the odds of being highly annoyed by a factor of 2.6. [31][31a] Residents raising infrasound are usually responding to something real, audible low-frequency noise or the fair worry that a decibel reading misses something. That is answered with octave-band measurements before and after construction, not with the infrasound claim.


    What to ask for. Measure first. Require a pre-construction acoustic baseline at the property line and at the nearest residences, a final study on measured sound data for the actual equipment, and continuous monitoring from the start of construction, which is what Yorkville’s Ordinance 2025-53 and its three approvals now require. [11b][11s][11q][11x] Ask for the applicant’s cooling design and the resulting sound power levels, and for disclosure of changes to either after approval, because air cooling rejects the same heat with fans and runs them hardest on the hot, humid days when windows are open. Aurora’s ordinance shows a stricter form: 57 dBA by day and 47 at night at the facility’s own property line, rooftop chillers at least 1,500 feet from homes, and annual property-line noise reports the city publishes. [11t][11u] Ask also whether the state’s octave-band limits, enforced by complaint after the fact, are the only protection for unincorporated homes around the site, since Project Steel’s study claims only “substantial compliance” with the nighttime limit. [11d][41a]

    On infrasound. Residents raising it are usually responding to something real: audible low-frequency noise, or a fair worry that a single decibel reading misses it. The answer is octave-band measurements before and after construction, not a mechanism no study supports. A claim that fails on evidence costs the room the real concern should have won.

    This is part 6 of 13 in Thirteen Records, a series that takes the long article Data Centers Don’t Have an Environmental Record. They Have Thirteen of Them. one topic at a time. Previous: cooling wastewater. Next: construction, the impact neighbors meet first and, on a ten-year campus, live beside longest.

    Cover photo: Rsparks3 / Wikimedia Commons, CC0


    Citations

    [4] Joint Legislative Audit and Review Commission, “Data Centers in Virginia,” Report 598 (House/Senate Document RD206), December 9, 2024. Summary findings: generators “make up less than 4 percent of regional emissions of nitrogen oxides” in Northern Virginia (p. vi); “One-third of data centers are currently located near residential areas” (p. vii); “a large majority of data centers do not generate noise complaints because of their location or design” (p. viii). Chapter 5: 2023 actual emissions “only 7 percent of what permits allowed, with most emissions coming from maintenance testing”; emissions “unlikely to adversely affect regional air quality”; generators’ “intermittent use makes their impacts difficult to model”; regional monitoring “does not effectively capture localized effects”; DEQ three-year monitoring study (p. 59). “General Assembly could incentivize use of generators with lower emission rates”; Tier 4 engines or SCR reduce nitrogen oxides and particulate matter “reportedly by up to 90 percent”; “only one uses Tier 4 generators” (p. 60). Permits “issued per data center site, rather than per building or generator”; worst case “where all data centers in Northern Virginia reach their maximum allowed emissions” would emit “over 9,000 tons of nitrogen oxides in the region,” “about half of what has typically been emitted annually in Northern Virginia by all sources” (p. 60). Chapter 6: noise “is not loud enough to damage nearby residents’ hearing and rarely loud enough to violate noise ordinances”; audibility past the property line “depends on its design and its type of cooling system”; complaint noise “ranges from an estimated 40 to 59 decibels” (p. 75). “Almost one-third (29 percent) of operational data center properties in Virginia are within 200 feet of residentially zoned properties” (p. 77; Table B-1, p. 103). https://jlarc.virginia.gov/pdfs/reports/Rpt598.pdf (archived: https://web.archive.org/web/20261025155822/https://jlarc.virginia.gov/pdfs/reports/Rpt598.pdf). Legislative repository copy: https://rga.lis.virginia.gov/Published/2025/RD206 (archived: https://web.archive.org/web/20260908164522/https://rga.lis.virginia.gov/Published/2025/RD206)

    [10d] Ben Howell, WGLT/NPR Illinois, “How Aurora and DeKalb residents are dealing with data centers,” August 3, 2026: City Manager Bill Nicklas said “the city has not had to deal with complaints about the center due to noise … or any other pollution issue”; the campus sits “roughly a mile from the nearest homes.” https://www.nprillinois.org/illinois/2026-08-03/how-aurora-and-dekalb-residents-are-dealing-with-data-centers (archived: https://web.archive.org/web/20261025160423/https://www.nprillinois.org/illinois/2026-08-03/how-aurora-and-dekalb-residents-are-dealing-with-data-centers)

    [11q] United City of Yorkville, City Council Packet, July 14, 2026, item PZC 2026-03 & EDC 2026-30, First Amendment to the Planned Unit Development Agreement with C1 Yorkville, LLC (CyrusOne CHI-11, approximately 228 acres): water allocation reduced from 500,000 to 40,000 gallons per day with closed-loop cooling; Section on mechanical screening and noise: noise study by Trinity Consultants “reviewed and accepted by the City’s 3rd party review engineer (Soundscape Engineering)”; “The Developer agrees to be responsible for the continuous noise monitoring”; project “subject to the requirements of the City’s Noise Ordinance, Title 4, Chapter 4”; “the City’s ordinance exempts the emergency operation of generators from regulation”; final noise study with each building permit “consistent with the standards set forth on Exhibit H,” presented to the City Council. Exhibit G, Trinity Consultants, CyrusOne Yorkville AHJ Noise Study, May 21, 2026: long-term background measurements September 3 to 4, 2024 (nighttime L90 38 to 41 dBA); projected nighttime data center levels of 30 to 45 dBA at receivers against a 60/50 dBA day/night code limit. Exhibit H, Soundscape Engineering, “Recommended Guidelines for Data Center Noise Impact Studies Submitted with Permit Applications, Rev. 1,” July 14, 2026: octave-band sound power data, measured data preferred; tonality assessment; reasonable worst-case conditions; routine generator testing; updated ambient survey optional but recommended. https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6824 (archived: https://web.archive.org/web/20261025162615/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6824) and https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6827 (archived: https://web.archive.org/web/20261025162621/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6827). Adoption: Minutes of the Regular Meeting of the City Council, July 14, 2026 (as reproduced in the July 28, 2026 council packet): Ordinance 2026-50, Exhibit H amendment 7-0, main motion 7-0; Alderman Marek on noise issues at CyrusOne’s Aurora campus; CyrusOne attorney Russ Whitaker that the Aurora campus “was approved around 2017, prior to the predictive modeling and noise standards they follow now.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6839 (archived: https://web.archive.org/web/20261025162729/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6839)

    [11d] Shiner Acoustics, LLC, “Project Steel Environmental Noise Assessment,” SA project 1250506, Revision C, September 19, 2025, prepared for Prologis, in the United City of Yorkville City Council Packet, March 24, 2026, PDF pp. 807 onward (Summary, p. 809): average baseline L90 sound levels of 39 to 42 dBA; Yorkville limits 60 dBA day and 50 dBA night; Illinois limits for unincorporated residences about 55 dBA day and 44 dBA night; base design predicted at “49 to 65 dBA at residential receivers” with standard-noise chillers and generators, “which exceeds both noise codes.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6695 (archived: https://web.archive.org/web/20260409172641/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6695)

    [11s] United City of Yorkville, Ordinance No. 2026-32, approving a Planned Unit Development Agreement with Prologis, L.P. (Project Steel), passed March 24, 2026, executed copy (scanned; read by text recognition of the page images, October 25, 2026): Section 2.1, entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date,” provided the project commences within three years; Section 2.2, “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. The Developer has requested and the City hereby agrees that, for a period of fifteen (15) years from the Effective Date, any standards adopted to further regulate Energy Industrial Uses shall be waived and not applicable to the Subject Property”; Section 2.3, construction over a twenty-year period in three phases; Section 3.3 noise terms as below; Section 3.4, water usage “governed by the terms of the Utility Agreement”; Exhibit H, the Shiner Acoustics initial noise study. https://www.yorkville.il.us/DocumentCenter/View/13598 (archived: https://web.archive.org/web/20261025160732/https://www.yorkville.il.us/DocumentCenter/View/13598). Packet version: City Council Packet, March 24, 2026 (Project Steel approval). Planned Unit Development Agreement between the United City of Yorkville and Prologis, L.P. (Project Steel), Section 3.3, Noise Studies and Noise Monitoring: “At the onset of each phase of construction, Developer shall install continuous noise monitoring devices recommended by a sound engineer chosen by the City”; devices “maintained throughout the life of the Project,” with City access to data on request; on notice of an exceedance, Developer “shall investigate the source of the noise and identify and implement one or more means to mitigate”; final noise study based on “actual sound level measurements of that specific equipment … and not on interpolated, extrapolated, or otherwise calculated sound levels,” with a mitigation plan meeting local limits “which includes the penalty for tonal equipment.” City presentation in the same packet: daytime limit 60 dBA and nighttime 50 dBA, “10 dbA penalties to those limits for tonal noise (i.e. limit of 50 dbA daytime / 40 dbA nighttime).” Shiner Acoustics, Project Steel noise evaluation, September 19, 2025: baseline L90 39 to 42 dBA (measured June 23 to 27, 2025); Illinois limits for commercial to residential about 55 dBA day and 44 dBA night; base design predicted at 49 to 65 dBA at residential receivers, “which exceeds both noise codes”; with lower-noise chillers and sound walls “predicted to achieve compliance with the Yorkville limits”; for the Illinois limits, “substantial compliance” with “the lowest-noise chillers and low-noise generators.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6695 (archived: https://web.archive.org/web/20260409172641/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6695)

    [11t] City of Aurora, Illinois. Ordinance O26-022, Legistar 26-0112 Exhibit A-FINAL, Zoning Ordinance Section 49-104.3(c)(25), data center facility conditional use: “A baseline pre-development sound study with minimum and maximum dB (A) levels measured for a continuous weeklong period”; Noise Modeling Study by a third-party acoustical engineer; “Evaporative chillers utilizing potable water are prohibited”; roof-mounted chillers not within 1,500 feet, ground-mounted chillers and generators not within 1,000 feet of any residential, hospital or educational use; “Roof-mounted generators are prohibited”; generators to comply with Public Act 104-0458 “including but not limited to Tier 4 emission standards in 415 ILCS 5/39(a)”; noise “must not exceed the following constant-minimum noise thresholds as measured at the facility property line: Daytime hours 57 dB (A) weighted 7am-7pm; and Nightime hours 47 dB (A) weighted 7pm-7am”; continuous vibration monitoring; PUE no more than 1.2; “Water Usage Effectiveness of no more than two tenths (0.2),” potable building water (liters) per IT equipment kilowatt-hour. https://www.aurora.il.us/files/sharedassets/mainsite/v/1/environment/documents/o26-022.pdf (archived: https://web.archive.org/web/20261025155804/https://www.aurora.il.us/files/sharedassets/mainsite/v/1/environment/documents/o26-022.pdf). Ordinance O26-021, Legistar 26-0092, Chapter 50, Aurora Responsible Data Center Ordinance, applicable to all data centers in city limits: generator testing “regardless of whether installed before or after March 25, 2026, may only occur between the hours of 9:00 am and 5:00 pm Monday through Friday, and not on holidays. No more than two (2) generators may be tested simultaneously”; annual ENERGY STAR Portfolio Manager energy and water report and “Third party tested noise level reports … during both daytime hours and nighttime hours at the property line,” made publicly available by June. https://www.aurora.il.us/files/sharedassets/mainsite/v/1/environment/documents/o26-021.pdf (archived: https://web.archive.org/web/20261025155729/https://www.aurora.il.us/files/sharedassets/mainsite/v/1/environment/documents/o26-021.pdf). City pages: “New Data Center and Warehouse Regulations,” https://www.aurora.il.us/Property-Business/Zoning-and-Planning/New-Data-Center-and-Warehouse-Regulations (archived: https://web.archive.org/web/20261010000331/https://www.aurora.il.us/Property-Business/Zoning-and-Planning/New-Data-Center-and-Warehouse-Regulations); “City Council Approves Regulations on Data Centers,” March 25, 2026 (moratorium enacted September 25, 2025; ordinances approved March 24, 2026), https://www.aurora.il.us/News-articles/City-Council-Approves-Regulations-on-Data-Centers (archived: https://web.archive.org/web/20260511095055/https://www.aurora.il.us/News-articles/City-Council-Approves-Regulations-on-Data-Centers); “CyrusOne Noise Mitigation Updates,” April 23, 2026: “a permanent solution to the noise complaints that have affected the area,” https://www.aurora.il.us/News-articles/CyrusOne-Noise-Mitigation-Updates (archived: https://web.archive.org/web/20260424002055/https://www.aurora.il.us/News-articles/CyrusOne-Noise-Mitigation-Updates)

    [11u] Ben Howell, WGLT / Illinois Newsroom, “In data center hubs Aurora and DeKalb, two different approaches to setting restrictions,” August 11, 2026. CyrusOne Aurora campus drew “consistent complaints from nearby residents,” mainly about rooftop cooling fans; DeKalb City Manager Bill Nicklas on metered water at Meta and on the newer facility “not using water for cooling.” https://ipmnewsroom.org/in-data-center-hubs-aurora-and-dekalb-two-different-approaches-to-setting-restrictions/ (archived: https://web.archive.org/web/20261024145913/https://ipmnewsroom.org/in-data-center-hubs-aurora-and-dekalb-two-different-approaches-to-setting-restrictions/)

    [11w] United City of Yorkville, City Council Packet, June 10, 2025 (ArchiveCenter Item 6268). Written public comment correspondence, packet pp. 234 to 236: resident email of March 25, 2025 (“could cause significant noise pollution in this area to residents, causing neurological and mental health stressors in addition to medical issues and complications”) with links to Washington Department of Ecology, EPA DERA, American Cancer Society, and California Air Resources Board diesel pages, and City Administrator Bart Olson’s replies of March 27 and 31, 2025: that none of the data centers nearer the resident’s home will use well water, “neither their own or the City wells,” and “They are not anticipated to begin operation until well after we have converted to the Lake Michigan source”; “We have spoken with our government counterparts in Loudoun County Virginia, which is the data center capital of the world. They have spoken a bit about noise complaints being the most frequent issue cited by neighbors, but they tended to downplay the severity of it compared to your assertion of medical issues and complications.” Staff memorandum, Sara Mendez, Planner I, to the Planning and Zoning Commission, May 7, 2025, “PZC 2025-05 Data Center Development Standards, Text Amendment,” packet pp. 394 to 410, comparing Loudoun County, Prince William County, and Chandler standards (“While Yorkville is not looking to adopt Loudoun County’s standards exactly, it aims to implement similar best practices tailored to the City’s specific needs”); Loudoun generator testing hours as tabulated in the memo: May 1 to September 30, 5 to 7 p.m.; October 1 to April 30, 11 a.m. to 5 p.m.; table of twelve data center projects with nearest distance to a residential property line: Cyrus One ~2,230 feet; Prologis (Project Steel) ~3,500 feet; Daniels (South) ~130 feet; Daniels (North) ~98 feet; Green Door 50 acres ~4,300 feet; Green Door-Hagemann ~7,300 feet; Green Door-Kelaka ~1,500 feet; Green Door-Meyer ~0 feet; Hamman-Kelaka ~0 feet; Magnolia Hill Partners ~2,600 feet; Pioneer (Project Cardinal) ~460 feet; PGP Development ~650 feet. Draft ordinance, packet pp. 389 to 393, adopted as Ordinance 2025-53 on June 24, 2025 by a 7-0 roll call (draft minutes of the June 24, 2025 City Council meeting, in the July 22, 2025 City Council Packet, ArchiveCenter Item 6360, p. 20). https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6268 (archived: https://web.archive.org/web/20251030032646/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6268) and https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6360 (archived: https://web.archive.org/web/20261025162554/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6360)

    [11x] United City of Yorkville, Ordinance No. 2025-77, approving the Planned Unit Development Agreement for Project Cardinal, passed November 10, 2025 (7-0), signed by the mayor November 13, 2025, published November 14, 2025; city-posted executed copy, mayor’s signature and clerk’s attestation dated November 13, 2025, Pioneer Development signature and date lines blank. Section 2.1: vesting applies “Upon commencement of the Project within three (3) years of the Effective Date.” Section 2.2: “Section 10-4-10 of the UDO is reserved for additional regulations applicable to Energy Industrial Uses. No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” No reference to Ordinance 2025-53. Section 2.14: “seventy-eight (78) feet, inclusive of any rooftop mechanical equipment or appurtenances.” Section 3.5: water obligations “addressed exclusively in the Utility Agreement.” https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId= (archived: https://web.archive.org/web/20261025151237/https://www.yorkville.il.us/DocumentCenter/View/13587/Ordinance-2025-77—record?bidId=). Annexation agreement, Ordinance No. 2025-78: https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId= (archived: https://web.archive.org/web/20261025151421/https://www.yorkville.il.us/DocumentCenter/View/13588/Ordinance-2025-78—record?bidId=). Packet version: City Council Packet, November 10, 2025 (ArchiveCenter Item 6499), Planned Unit Development Agreement between the United City of Yorkville and Pioneer Development, LLC (Project Cardinal), packet pp. 272 to 290. Section 2.1: entitlements “fully vested and protected from amendments and changes to City ordinances, codes, or regulations for a period of twenty (20) years from the Effective Date.” Section 2.2: “No new or amended standards, code provisions, or special regulations for Energy Industrial Uses shall apply to the Subject Property during the twenty (20) year vested term from the Effective Date of this Agreement, unless Developer agrees in writing or to the extent required by state or federal law.” Section 2.3: approximately ten-year build-out; Phasing Plan “advisory only and non-binding.” Section 2.4: “All data center buildings shall be at least five hundred feet (500′) from the nearest residential or commercial structure outside the boundaries of the Subject Property,” measured “from existing, occupied, residential or commercial buildings as of the date of PUD approval.” Section 2.10: 100-foot Transition Zone Type D buffer with a 12-foot berm facing residential properties and 8 feet elsewhere; “No additional berms or landscape requirements shall be imposed unless Developer agrees in writing.” Section 2.11: “the most appropriate location for Mechanical Equipment is on the rooftops; therefore, whenever practical, mechanical equipment shall be placed on the rooftops”; project subject to the City Noise Ordinance “as it existed when the PUD application was approved by the City Council.” Section 2.14: 78-foot maximum height including rooftop equipment. Section 2.17: “all primary power used for the data center campus on the Subject Property will be delivered from the Commonwealth Edison power grid” unless the City Council approves otherwise. Section 3.4: continuous noise monitoring devices at the onset of each construction phase, a preliminary report within 60 days after each building is operational, devices maintained for the life of the project. Section 3.11: operational testing of generators “during the hours of 11:00 a.m. to 5:00 p.m., Monday through Friday, and not on any Holidays.” https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499 (archived: https://web.archive.org/web/20261025154939/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6499)

    [11b] United City of Yorkville, Ordinance No. 2025-53, data center standards, passed June 24, 2025 (7-0), published June 27, 2025, replacing Unified Development Ordinance Section 10-4-10 in its entirety: https://www.yorkville.il.us/DocumentCenter/View/13005/Ordinance-2025-53?bidId= (archived: https://web.archive.org/web/20261025151332/https://www.yorkville.il.us/DocumentCenter/View/13005/Ordinance-2025-53?bidId=). As codified, UDO Section 10-4-10, history note “(Ord. No. 2025-53, effective 06/27/2025)”: initial noise study with baseline measurements and predictive modeling; final study on “actual sound level measurements”; mitigation plan “including the penalty for tonal equipment”; annual monitoring by the city’s consultant for three years or, alternatively, continuous monitors from the onset of construction; rooftop HVAC or mechanical units “shall require the approval of City Council”; 70-foot height including rooftop equipment within 1,500 feet of a residence; generator testing 11 a.m. to 5 p.m. weekdays, non-holidays; 50-foot battery setback; 500-foot building separation; 100-foot landscape buffers. No water or well provisions. https://online.encodeplus.com/regs/yorkville-il/doc-viewer.aspx?secid=290 (archived: https://web.archive.org/web/20261025034754/https://online.encodeplus.com/regs/yorkville-il/doc-viewer.aspx?secid=290). UDO Section 10-7-6.A: “All parcels within a subdivision shall be required to connect to the United City of Yorkville’s Public Water Supply System.” https://online.encodeplus.com/regs/yorkville-il/doc-viewer.aspx?secid=326 (archived: https://web.archive.org/web/20261025034848/https://online.encodeplus.com/regs/yorkville-il/doc-viewer.aspx?secid=326)

    [11y] United City of Yorkville, Planning and Zoning Commission, transcript of the public hearing on PZC 2025-08 (Pioneer Development, LLC, Project Cardinal), July 9, 2025, Vitosh Reporting Service (ArchiveCenter Item 6395, “PZC 7-9-25 Minutes & Transcript”). Sworn testimony of Matt McCarron for Pioneer Development: Ashburn homes “within 500 feet of data center campuses in Ashburn have been appreciated by approximately 70 percent over the last decade” (transcript p. 26); “legacy Ashburn data center campuses are built as close as a hundred, 130 feet from residential property lines. We’re committing to a minimum 500-foot setback” (pp. 26 to 27); generator testing “is only going to occur once or twice a year” and generators “are really never used outside of testing” (p. 25); “all backup generators meet Tier 4 final EPA standards” (p. 29); “if it’s curtailed in an emergency, we would be curtailed first and we would have backup generators. We are not going to cause a brownout” (p. 84). https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6395 (archived: https://web.archive.org/web/20261025162533/https://www.yorkville.il.us/ArchiveCenter/ViewFile/Item/6395)

    [14] Industrial Noise and Vibration Centre, “Silencing also improved data center fan noise efficiency by 20 percent,” case study. [Source is the vendor who performed the work; independently published peer review does not exist for this specific result.] https://invc.com/resources/noise-control-case-studies/fans/data-center-fan-noise-attenuation-increases-efficiency-20/ (archived: https://web.archive.org/web/20260707112501/https://invc.com/resources/noise-control-case-studies/fans/data-center-fan-noise-attenuation-increases-efficiency-20/)

    [31] Health Canada / Statistics Canada, “Wind Turbine Noise and Health Study: Summary of Results,” November 2014. 1,238 participating households; 12 developments in Ontario and 6 in Prince Edward Island with “315 and 84 wind turbines respectively.” Self-reported sleep, dizziness, tinnitus, migraines, high blood pressure, and other illnesses showed no association with wind turbine noise levels; “WTN was not observed to be related to hair cortisol concentrations, blood pressure, resting heart rate or measured sleep”; “In all cases, annoyance increased with increasing exposure to WTN levels,”. The summary called its results preliminary pending peer review; the peer-reviewed papers are [31a]. https://www.canada.ca/en/health-canada/services/health-risks-safety/radiation/everyday-things-emit-radiation/wind-turbine-noise/wind-turbine-noise-health-study-summary-results.html (archived: https://web.archive.org/web/20261011053025/https://www.canada.ca/en/health-canada/services/health-risks-safety/radiation/everyday-things-emit-radiation/wind-turbine-noise/wind-turbine-noise-health-study-summary-results.html)

    [31a] Michaud, D.S., et al., Health Canada Wind Turbine Noise and Health Study, peer-reviewed results, 2016. “Exposure to wind turbine noise: Perceptual responses and reported health effects,” Journal of the Acoustical Society of America 139(3):1443-1454, DOI 10.1121/1.4942391: “Self-reported health effects (e.g., migraines, tinnitus, dizziness, etc.), sleep disturbance, sleep disorders, quality of life, and perceived stress were not related to WTN levels.” https://pubmed.ncbi.nlm.nih.gov/27036283/ (archived: https://web.archive.org/web/20261011154040/https://pubmed.ncbi.nlm.nih.gov/27036283/). Annoyance paper, JASA 139(3):1455-1466, DOI 10.1121/1.4942390: “for each 5 dB increase in WTN levels, the odds of reporting to be either very or extremely (i.e., highly) annoyed increased by 2.60.” https://pubmed.ncbi.nlm.nih.gov/27036284/ (archived: https://web.archive.org/web/20261014135119/https://pubmed.ncbi.nlm.nih.gov/27036284/). Stress biomarkers paper, JASA 139(3):1467-1479, DOI 10.1121/1.4942402: WTN exposure had no apparent influence on hair cortisol, resting blood pressure, or heart rate. https://pubmed.ncbi.nlm.nih.gov/27036285/ (archived: https://web.archive.org/web/20250205133304/https://pubmed.ncbi.nlm.nih.gov/27036285/). Sleep paper, Sleep 39(1):97-109, DOI 10.5665/sleep.5326: “Self-reported and objectively measured sleep outcomes consistently revealed no apparent pattern or statistically significant relationship to WTN levels.” https://pubmed.ncbi.nlm.nih.gov/26518593/ (archived: https://web.archive.org/web/20260430093401/https://pubmed.ncbi.nlm.nih.gov/26518593/)

    [32] National Institute for Occupational Safety and Health (NIOSH), Health Hazard Evaluation Report No. 2019-0119-3362, “Evaluation of Low Frequency Noise, Infrasound, and Health Symptoms at an Administrative Building and Men’s Shelter,” October 2019. Citing Johnson (1982): the review “did not find evidence of hearing threshold shifts from continuous exposures to levels of 118 dB or less for 24 hours”; “The frequency-specific or overall sound levels we measured are not known to cause adverse health effects.” https://www.cdc.gov/niosh/hhe/reports/pdfs/2019-0119-3362.pdf (archived: https://web.archive.org/web/20260909192039/https://www.cdc.gov/niosh/hhe/reports/pdfs/2019-0119-3362.pdf)

    [32a] Leventhall, G., “Low Frequency Noise. What we know, what we do not know, and what we would like to know,” Journal of Low Frequency Noise, Vibration and Active Control, Vol. 28, No. 2, pp. 79-104, 2009. Median hearing threshold about 97 dB at 10 Hz and about 107 dB at 4 Hz (Table I, p. 80); quoting Berglund and Lindvall, “There is no reliable evidence that infrasounds below the hearing threshold produce physiological or psychological effects” (p. 92). Reprint: https://scispace.com/pdf/low-frequency-noise-what-we-know-what-we-do-not-know-and-zeeq9a7cmr.pdf (archived: https://web.archive.org/web/20250520182235/https://scispace.com/pdf/low-frequency-noise-what-we-know-what-we-do-not-know-and-zeeq9a7cmr.pdf)

    [36a] City of Chandler, Arizona, Ordinance No. 5033, Zoning Code amendment PLH22-0053 adding Chapter 35, Section 35-2214 (Data Centers), and Council Memo dated December 8, 2022 (Planning and Zoning Commission October 19, 2022, 7-0; introduced and tentatively adopted December 5, 2022). Memo: potential impacts “primarily from unwanted noise”; “As these data centers have developed closer to the urbanized area of Chandler, including residential areas, the potential for noise compatibility issues has increased”; “an industry migration from water-cooled to electrically-cooled facilities”; the lack of rules “has caused confusion for both the data center industry and Chandler residents.” Ordinance 35-2214(3) to (7): on-site liaison for noise complaints; pre-construction “sound study performed by a third-party acoustic engineer” at “the property line of the nearest property”; mitigation to prevent noise “from exceeding the ambient noise levels that were observed in the baseline study”; post-construction study “during peak operation of the Data Center mechanical equipment” and annual studies for five years; generator testing announced 24 hours in advance and limited to 9:00 a.m. to 5:00 p.m., Monday through Friday. No decibel limit. https://www.chandleraz.gov/sites/default/files/departments/development-services/PLH22-0053-Ordinance-No-5033-Data-Center.pdf (archived: https://web.archive.org/web/20261012204157/https://www.chandleraz.gov/sites/default/files/departments/development-services/PLH22-0053-Ordinance-No-5033-Data-Center.pdf) and https://www.chandleraz.gov/sites/default/files/departments/development-services/PLH22-0053-Council-Memo.pdf (archived: https://web.archive.org/web/20261010000250/https://www.chandleraz.gov/sites/default/files/departments/development-services/PLH22-0053-Council-Memo.pdf). City release, “Chandler’s data center ordinance now in effect,” January 11, 2023 (effective January 5, 2023): https://www.chandleraz.gov/news-center/chandlers-data-center-ordinance-now-effect (archived: https://web.archive.org/web/20261010004135/https://www.chandleraz.gov/news-center/chandlers-data-center-ordinance-now-effect)

    [36b] ABC15 Arizona, “Loud hum consuming Chandler neighborhood,” February 26, 2019. Residents near Dobson and Queen Creek roads; noise attributed to 24 chillers at a CyrusOne data center; CyrusOne statement that it continues to comply with Chandler’s ordinances; council discussion of enforcing the noise ordinance. https://www.abc15.com/news/region-southeast-valley/chandler/loud-hum-consuming-chandler-neighborhood (archived: https://web.archive.org/web/20260218122654/https://www.abc15.com/news/region-southeast-valley/chandler/loud-hum-consuming-chandler-neighborhood)

    [41a] 35 Ill. Adm. Code 901.102, Sound Emitted to Class A Land (Illinois Pollution Control Board noise regulations, Part 901, with Part 900 definitions and measurement procedures). Allowable octave-band sound pressure levels from Class B land (commercial and service uses) to Class A land (residential), nighttime: 63 dB at 31.5 Hz, 61 at 63 Hz, 55 at 125 Hz, 47 at 250 Hz, 40 at 500 Hz, 35 at 1,000 Hz, 30 at 2,000 Hz, 25 at 4,000 and 8,000 Hz; daytime: 72, 71, 65, 57, 51, 45, 39, 34, 32; Class C (manufacturing and industrial) sources have higher limits; measurements “at least 25 feet from the property-line noise source” at any point within the receiving Class A land. https://ilga.gov/ftp/JCAR/AdminCode/035/035009010001020R.html (archived: https://web.archive.org/web/20261025154950/https://ilga.gov/ftp/JCAR/AdminCode/035/035009010001020R.html)