# Why do data centers hum—and how can that be reduced?

Take the disturbance seriously, identify the source and path, then verify the promised control after startup.

Canonical: https://brightaifuture.com/guides/data-center-noise-neighbors
Format: guide
Source publication: Not established
Bright publication: 2026-09-19
Substantive update: None recorded
Evidence and review: Primary-source review completed 2026-09-19; Bright did not reproduce the cited research.

## Separate continuous sources from episodic operation

Cooling towers, chillers, dry-cooler fans, pumps, air handlers and transformers can create continuous or load-varying sound. Backup generators are normally a different operating case: routine testing, emergency operation, and in some markets a defined grid call. Construction noise is another temporary phase and should not be folded into an operating-level claim.

An equipment reading inside the site is not the sound level at a home. Sound changes with distance, source height and direction, intervening buildings and terrain, ground conditions, wind and temperature gradients. Multiple nearby campuses may also combine at the receptor.

## One A-weighted number cannot describe every hum

dBA is useful and widely regulated, but it downweights lower frequencies. A narrowband transformer or fan tone can be more noticeable than broadband sound at a similar overall level. A quiet nighttime background can also make a constant source more salient without moving it near a hearing-damage threshold.

JLARC reported complaint-triggered measurements of 40–59 dBA in selected Virginia cases. Those readings were total sound, not isolated data-center contribution, and were not representative of every facility. They show why the exact sampling context must stay beside the number.

## Design the control around the actual path

Better siting and orientation can keep high-output equipment and openings away from sensitive receptors. Quieter equipment, variable-speed operation, acoustic enclosures, intake and exhaust silencers, treated louvers and correctly dimensioned barriers can reduce specific paths. Routine generator testing can be scheduled for daytime where local rules allow.

None of those measures is a universal guarantee. Lower-frequency sound is harder to block; barriers need adequate geometry; operating controls must preserve safety and reliability; and moving one source can expose another receptor. Model normal operation, peak cooling, routine generator testing and a clearly defined emergency case instead of quoting one best-case point.

## Verification is the difference between a promise and a solution

Before construction, record the baseline at relevant property lines and homes, including daytime, nighttime and octave-band conditions. Model manufacturer sound-power spectra with terrain, buildings, barriers, weather assumptions and simultaneous equipment states. After startup, return to the same receptors with calibrated instruments and documented load conditions.

A useful rule also names the remedy: operating modification, equipment treatment, temporary curtailment where lawful, a corrective plan and a retest. Publish enough of the report for residents to compare the prediction with the measured result. A phone recording remains valuable as a time-and-experience log, not as the final compliance instrument.

## Limitations

Noise impact is site-specific; no universal safe setback follows from the reviewed evidence.

Complaint-triggered measurements are not representative facility averages or source-isolated readings.

Local dBA and dBC limits are policy choices, not universal health or disturbance thresholds.

The only located operating before/after mitigation figure is supplier-reported and lacks a public raw consultant report and residential-receptor outcome.

Bright did not perform acoustic measurements or reproduce any project model.

## Provenance and history

{
  "provenance": {
    "publisher": "Bright",
    "role": "Source-backed evergreen explanation; not a new scientific result"
  }
}

## Original sources

- [Virginia JLARC: Data Centers in Virginia, Part 2](https://jlarc.virginia.gov/pdfs/reports/Rpt598-2.pdf)
- [Loudoun County: Data Centers—Noise and Air Quality Concerns](https://www.loudoun.gov/6405/Noise-Air-Quality-Concerns)
- [East Brandywine Township data-center noise requirements](https://ecode360.com/51398306)
- [Henry County adopts data-center regulations](https://henrycountyva.gov/m/newsflash/home/detail/148)
- [Evaluation of smartphone sound measurement applications](https://pmc.ncbi.nlm.nih.gov/articles/PMC5102154/)
- [FHWA noise barrier design principles](https://www.fhwa.dot.gov/Environment/noise/noise_barriers/design_construction/design/design03.cfm)
- [Phoenix data-center chiller mitigation case study](https://hushcore.net/wp-content/uploads/Hushcore-Case-Study-Standard-SCE-System-Phoenix-AZ.pdf)

## Continue exploring

- [A township requires data-center noise to be measured before and after construction](https://brightaifuture.com/discoveries/east-brandywine-noise-verification)