Residents who live near data centers frequently describe the noise as inescapable: a constant mechanical hum from cooling systems, a periodic roar from backup generator tests, a low-frequency vibration that passes through walls and windows. They also describe a second frustration, often more demoralizing than the noise itself: filing complaints with local authorities and receiving no meaningful response.
The gap between the noise that exists and the enforcement that follows is not accidental. It is a product of how noise ordinances are written, who enforces them, how data center noise interacts with standard measurement methods, and how seriously complaints are treated when they come from individuals rather than organized groups. This article explains each of those factors, and what residents can do to change the dynamic.
How Noise Ordinances Work
Local noise ordinances are the primary legal mechanism for regulating noise in most American communities. They are adopted by city councils or county boards and enforced by code enforcement offices, building departments, or in some jurisdictions the police.
Most ordinances regulate noise by establishing maximum decibel levels — measured at a specific point, usually the property line of the affected residential property — that are permitted by zone and time of day. A typical structure might allow up to 55 decibels (dB or dBA) at a residential property line during daytime hours (often 7 a.m. to 10 p.m.) and 45 to 50 decibels at night. Some ordinances set different limits for industrial zones, commercial zones, and residential zones, with the residential limits applying at the nearest residential receptor regardless of what zone the noise source occupies.
Some ordinances go further and restrict specific types of noise: tonal noise (a single sustained frequency, like a constant hum), impulsive noise (sudden loud events), or low-frequency noise. Others include generator testing restrictions — prohibiting or limiting the hours during which backup generators may be run for non-emergency testing.
Penalties for violations vary. They typically begin with a warning or notice of violation, followed by escalating fines for continued violations. In some jurisdictions, repeated violations can result in permit conditions or revocation of operating permits.
Why Data Centers Frequently Violate Residential Noise Ordinances
Data centers are major sources of continuous mechanical noise. The cooling systems — chillers, cooling towers, air handlers, condenser fans — run at full capacity around the clock. Each unit may produce noise at a moderate level, but a large facility with dozens or hundreds of cooling units creates a combined sound level that frequently exceeds residential noise limits at adjacent property lines.
The EESI has documented that the compounding effect of thousands of servers and associated cooling equipment can raise noise levels to 96 decibels within a facility, and cooling towers from gas-fired power infrastructure can emit up to 70 dBA within 400 feet. Backup generator tests, which facilities typically conduct monthly, involve running large diesel generators — often reaching 105 decibels at the source — that can be heard and felt at significant distances.
In Prince William County, Virginia, residents have documented that data center noise routinely exceeds 60 decibels at their properties. The county’s noise ordinance exempts air conditioning equipment — a provision that facilities have relied on to argue their cooling systems are similarly exempt, even though industrial cooling infrastructure operates at a scale completely different from a residential air conditioning unit.
Beyond the raw decibel level, data center noise has characteristics that standard ordinances were not designed to address. Much of it is low-frequency — below 200 Hz — which is difficult to measure accurately with standard sound level meters and difficult to block with conventional noise barriers. Low-frequency noise penetrates walls more effectively than higher-frequency sound, which is why residents describe it as present inside their homes even when windows are closed. The tonal, continuous nature of the noise — the same pitch, without interruption, day and night — is experienced by many residents as more disturbing than intermittent louder sounds, because there is no quiet period during which the body can recover.
EESI reported health effects documented among data center neighbors that include headaches, vertigo, nausea, sleep disturbances, ear pain, and hypertension. In Greenbrier, Arkansas, residents near a Bitcoin mining center reported 24/7 noise leading to increased blood pressure and anxiety. In Granbury, Texas, residents of a mobile home park less than 100 yards from a facility housing 60,000 computers reported vertigo, nausea, high blood pressure, migraines, fluid coming from the ears, and insomnia.
The Enforcement Problem
Enforcement of noise ordinances against data centers is frequently inadequate, for reasons that are structural rather than accidental.
Individual complaints are not prioritized. Code enforcement offices respond to complaints one at a time. A single resident calling to report noise from a data center is likely to receive a single inspection visit, at a time the inspector chooses, with equipment that may or may not be appropriate for measuring the type of noise involved. If the reading at the time of the inspection happens to fall within the limit — because the measurement was taken at a different location, during a different operational mode, or with equipment that does not capture low-frequency components — the complaint is closed.
Most ordinances were not written for this kind of noise. As EESI noted, “most county or community noise ordinances are written to address noisy block parties rather than data centers.” A provision that sets a 55-decibel limit without specifying the measurement location, the duration, the frequency range, or the equipment to be used gives inspectors significant discretion — and gives facilities significant room to argue compliance. The data center operator may commission its own sound study using methodology favorable to a compliance finding; without an independent measurement, the complaint may go nowhere.
Facilities are large economic actors. Data centers represent significant investments and significant tax revenue. Local officials — including code enforcement supervisors — are aware of this. A complaint from a single resident about noise from a facility that represents tens or hundreds of millions of dollars in investment is not treated the same as a complaint about a neighbor’s leaf blower. This is not a cynical observation; it is a documented pattern. EESI cited the characterization of data centers as “the goose that lays the golden eggs,” noting that this status contributes to the laxity of enforcement response.
Low-frequency noise is hard to measure and harder to prove. Standard sound level meters are calibrated primarily for frequencies above 200 Hz. Low-frequency components are underweighted in the A-weighted decibel measurement (dBA) that most ordinances use. A facility generating significant low-frequency noise — experienced by residents as a persistent, interior rumble — may produce a dBA reading that appears compliant even as residents report serious health and quality-of-life impacts.
How to Document Noise
Documentation is the foundation of any effective enforcement effort. The goal is to produce a record that is specific, time-stamped, location-anchored, and difficult to dismiss as subjective.
Smartphone sound level meter apps. Two apps are commonly recommended by health and noise professionals:
- NIOSH SLM (National Institute for Occupational Safety and Health Sound Level Meter app): Developed by a federal agency specifically for accurate noise measurement, available for iOS. Validated for compliance measurements. Produces readings in dBA with timestamps.
- Decibel X: Available for iOS and Android, widely used for noise documentation. Logs measurements with time and allows export.
Smartphone measurements are not as accurate as professional calibrated equipment, and they are not admissible as expert evidence in formal proceedings. But they are sufficient to document patterns — to show that at 2 a.m. on a Tuesday at the property line, the reading was 62 dB; that the same location at the same time the following week produced 64 dB; that this pattern persists every night of the week. That documentation supports the credibility of a complaint and demonstrates that the noise is real, consistent, and measurable.
When taking measurements with any app: note the exact location (use GPS coordinates or a precise description), note the date and time, note the weather conditions (wind can affect readings), and take measurements at multiple locations including the property line and inside the residence with windows closed.
Noise logs. In addition to electronic measurements, keep a written log. For each noise event or measurement: date, time, duration, description of the sound (hum, roar, vibration, tonal), your location, any health effects you experienced, and whether any other household members were affected. Log every significant episode, even if it seems repetitive. The accumulation of log entries over weeks and months is itself evidence of the sustained nature of the problem.
Professional acoustic measurements. When a complaint is likely to progress to a formal enforcement proceeding or legal challenge, professional acoustic measurements from a licensed consultant become worth the cost. A professional measurement uses calibrated equipment (Type 1 or Type 2 sound level meters per ANSI standards), applies the correct frequency weighting and time averaging called for by the applicable ordinance, and produces a report that can be submitted as expert evidence. Members of the Institute of Noise Control Engineering or the Acoustical Society of America can be located through those organizations’ directories.
How to File a Complaint
Who to contact. The enforcement agency for noise ordinances varies by jurisdiction. It may be the code enforcement or zoning enforcement office, the building department, or in some jurisdictions the police (for acute noise violations). Call your local government’s main line and ask specifically: “Who enforces the noise ordinance against an ongoing noise violation from an industrial facility?” Get a name and a direct contact.
What to include. A complaint should be specific: the address or location of the facility, the nature of the noise (continuous hum, periodic generator testing, both), the times and frequencies of occurrence, and the impact on your household (sleep, health, use of outdoor spaces). Attach any measurements you have taken. Note any prior complaints you have made and their outcome.
Submit in writing. Call if you need to initiate contact, but follow up in writing — email is sufficient — so there is a record. Written complaints are tracked in complaint management systems; phone calls often are not.
Follow up. After filing, ask for a written response. If an inspection is scheduled, ask what methodology will be used, what standard will be applied, and who will conduct it. After the inspection, request the results in writing.
Escalate when complaints produce no action. If the code enforcement office closes the complaint without meaningful action, escalate to the department director, then to the relevant elected official, then to the local health department if health effects are documented. A complaint on record with multiple agencies is harder to ignore than one filed only with code enforcement.
What Organized, Persistent, Documented Complaints Can Produce
Individual complaints, in isolation, rarely produce enforcement action against a data center. The asymmetry of resources is too large, the ordinances are too vague, and the political environment too often favors the operator. What changes the dynamic is organization.
In Chandler, Arizona, residents of the Brittany Heights neighborhood organized and persisted for nearly a decade after a data center arrived in late 2014. Their sustained complaints contributed to a 2022 zoning code amendment making it harder to site new data centers in the city, and to the city council’s unanimous rejection of a new proposed facility in 2025.
In Prince William County, Virginia, where data center noise levels routinely exceed 60 decibels at residential property lines, sustained resident complaints led Amazon to agree to retrofit some of its facilities with acoustical shrouds. In Loudoun County, county supervisors in 2026 were publicly discussing changes to both the zoning ordinance and the noise ordinance specifically in response to documented community complaints about data center noise in Sterling. “We can change the zoning ordinance. We can change the noise ordinance. We are looking at all possible mechanisms,” Supervisor Mike Turner stated.
The mechanism by which organized complaints produce results is not primarily through direct enforcement — though enforcement can happen. It is through the accumulation of a public record that local officials can no longer ignore, and through the leverage that documented complaints provide in permit renewal and expansion applications. When a facility applies to expand, an existing record of noise violations and unanswered complaints is a concrete reason for a planning commission to impose conditions or deny the application.
When the Local Ordinance Is Inadequate
In many jurisdictions, the existing noise ordinance is simply not equipped to address data center noise — because it uses inadequate measurement standards, because it exempts the type of equipment data centers use, or because the enforcement mechanism is effectively inaccessible to individual residents.
When the ordinance itself is the problem, the remedy is legislative: advocating for a stronger standard through the local legislative process.
This means engaging your city council or county board directly. Come with a specific proposal: a lower decibel limit at residential property lines during nighttime hours, a prohibition on or restriction of generator testing during specified hours, a provision requiring that measurements be taken at the property line closest to residential uses rather than at a location the facility operator designates, and a requirement that the measurement methodology account for low-frequency components rather than relying solely on A-weighted readings.
Bring documented evidence: your noise logs, your smartphone measurements, your medical records if health effects have occurred, and your correspondence with code enforcement. Ask neighbors to attend and speak. A council that hears from an organized group of residents is more likely to act than one that receives a single written complaint.
The Clean Air Act of 1970 gave the EPA authority over noise pollution, which it exercised through the 1970s before the Reagan Administration defunded the Office of Noise Abatement and Control in 1981. The EPA retains the legal authority to study noise and its effects, though it has not exercised it actively in decades.
In the meantime, the local ordinance is what exists — and changing it, improving it, and enforcing it are the available tools. They require time and persistence. But as the documented cases in Chandler, Prince William County, and Loudoun County show, they have produced real results when residents have organized to use them. A persistent, documented complaint effort is not a guarantee of enforcement, but it is the clearest path to being taken seriously by the officials and operators who, absent that pressure, have limited incentive to act.
This article was researched and drafted with AI assistance under human review. See our full AI and editorial practices.