Six Federal Cases Are Testing Where a Data Center Can Sit

Since April 6, five putative class actions have been filed in federal district courts by residents living near data centers, each alleging that the facility’s cooling systems and backup generators push unreasonable noise onto their properties. PSV pulled every docket rather than relying on the trade coverage, and the roster is specific: Digi Power X in the Western District of New York, Alliance Cloud Services in the Western District of Michigan, DataOne USA in the District of New Jersey, xAI together with SpaceX and MZX Tech in the Northern District of Mississippi, and Microsoft in the Eastern District of Wisconsin. All five are pleaded as state common law claims, principally private nuisance and negligence, carried into federal court on diversity jurisdiction.

The Microsoft case is the fullest record and the most active. Garret Ostergaard, David Wade and Joy Wade filed on July 1 over the Fairwater campus at 4800 90th Street in Mount Pleasant, Wisconsin, pleading a class of residents within 1.5 miles and invoking both ordinary diversity and the Class Action Fairness Act, which requires at least 100 class members and more than $5 million in aggregate controversy. The complaint describes a 315-acre campus of three buildings totaling 1.2 million square feet drawing 337.6 megawatts, and it quotes a Microsoft representative saying the company is aware of the noise concerns at the Mount Pleasant facility and is investigating root causes. Those figures and that quotation are the plaintiffs’ characterizations of the record, not PSV findings. Microsoft was served on July 17 and the parties filed their Rule 26(f) plan on August 19, so the case is into discovery planning.

This is the part the secondary coverage has wrong, and it matters because an operator could reasonably conclude from a headline count that the claims are failing. They are not being tested. In the New Jersey case against DataOne, over a facility in Vineland, the court issued an order to show cause on June 12 on its own motion, and the problem it identified was not the nuisance theory. It was that the complaint had not adequately alleged the citizenship of a limited liability company defendant, which for diversity purposes follows the citizenship of every one of its members. Plaintiffs filed a notice of voluntary dismissal a week later and the case was terminated on June 22. That is a pleading defect on an LLC caption, and it is fixable in state court or in a refiled federal complaint.

The Mississippi case against xAI ran further and stopped for a different reason. xAI and MZX Tech moved to dismiss for failure to state a claim on July 27, SpaceX moved separately to dismiss for lack of jurisdiction the same day, the magistrate judge stayed the case on August 5 pending a ruling on the jurisdictional motion, and plaintiffs filed a notice of voluntary dismissal on August 17 before any of it was decided. No court has ruled on whether data center noise states a nuisance claim. The one order that might have told us something, on the partial motion to dismiss two counts in the Michigan case, was entered on August 13 and is not in the public file, so PSV cannot report what it held. The honest read for an operator is that the theory is untested rather than rejected, and that the plaintiffs’ bar is iterating: Weitz & Luxenberg appears in two of these cases and Liddle Sheets in two more, which is a coordinated campaign learning from its own procedural losses.

The useful artifact here is not a case summary, it is a standing exposure sheet across the sites a firm owns, has under contract, or is entitling. Inputs are the ones a development or asset management team already holds: the site plan showing where chillers, cooling towers, dry coolers and generator yards sit relative to the property line, the parcel boundary set, the residential parcels within about two miles, the applicable municipal noise ordinance with its measurement standard and its limits by time of day, any acoustical study in the file, and the permit conditions actually issued. Add two public pulls the team usually does not make: the municipality’s and the state environmental agency’s complaint and public comment records for the facility, and the local zoning agenda for any pending data center ordinance.

The output is one row per site with four columns that decide everything: distance from the nearest noise-generating equipment to the nearest residential parcel line, what the ordinance measures and whether the file contains a measurement in those units, whether a complaint record exists and how old the newest entry is, and whether a moratorium or new zoning standard is on a local agenda. An assistant can assemble that sheet and keep it current, and it can read a proposed ordinance against a project’s permit dates to flag a vested-rights question. It should cite the document and page behind every cell. The reviewer is the development lead for entitlement rows and the asset manager for operating rows, and the approval gate is that no row changes an underwriting assumption, a reserve, or a disclosure until counsel has read the underlying record. Nothing in this workflow is a legal conclusion, and none of it should be represented to a buyer or a lender as one.