You’re out of free articles.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Sign In or Create an Account.
By continuing, you agree to the Terms of Service and acknowledge our Privacy Policy
Welcome to Heatmap
Thank you for registering with Heatmap. Climate change is one of the greatest challenges of our lives, a force reshaping our economy, our politics, and our culture. We hope to be your trusted, friendly, and insightful guide to that transformation. Please enjoy your free articles. You can check your profile here .
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Subscribe to get unlimited Access
Hey, you are out of free articles but you are only a few clicks away from full access. Subscribe below and take advantage of our introductory offer.
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Create Your Account
Please Enter Your Password
Forgot your password?
Please enter the email address you use for your account so we can send you a link to reset your password:
People near the site of the disaster say they’re sick. But officials haven’t recognized any link between those symptoms and the fire.

People say they can still taste the metal from the Moss Landing fire. But no one in the local, state, or federal government is able to say why.
The story of Moss Landing got little attention compared to the scale of the disaster. On January 16 — days before Trump reentered office, and as fires continued to burn in and around Los Angeles, when tempers and attention spans were already strained — the Moss Landing Power Plant ignited. We still don’t know what caused the fire, but we do know a few crucial facts: Nearly all of the batteries at the 300 megawatt facility, one of the world’s largest, burned up in the fire, sending a colossal plume of black smoke soaring up from the site for days.
Two months after the blaze was extinguished, many people who live in the vicinity of Moss Landing, a couple hours south of San Francisco, say they’re still sick from the fire. Community organizers on the ground say the number of sick people is in the hundreds, at least. The symptoms range, but there are a few commonalities. Many report having bloody noses in the days immediately following the fire. In the long weeks that followed, they’ve had headaches that don’t respond to pain medications, rashes that resemble burns, and a recurring metallic taste in their mouths. They all say their symptoms go away if they leave their homes and go further away from the site. But the U.S. Environmental Protection Agency and California state regulators have given the all clear.
I have spent weeks trying to get to the bottom of what happened at Moss Landing. I’ve interviewed people who lived in the area and say they’ve experienced breathing issues and other difficulties, many of whom have gathered on Facebook to share photos, stories, and symptoms. Others have offered testimony about these illnesses in public fora and town halls. Multiple lawsuits have been filed against Vistra, the company that runs Moss Landing, over the fire, citing these health issues. Vistra denies the existence of evidence proving pollution from the fire is making people sick, and told me in a statement that the company is “committed to doing everything we can to do right by our community.”
“Moss Landing is not only home to our facility, it’s home to our employees and neighbors,” the statement reads.
And yet, the people say, their symptoms persist. One of the people who told me about their condition is Sheryl Davidson, a former receptionist who lives in the rural nearby town of Prunedale. One of her joys used to be doing Medieval cultural re-enactments, but since the fire she’s been unable to participate.
“My nose just started bleeding. It was traumatic,” she told me. “And I had asthma, but my asthma was miniscule. My whole life, I just had an inhaler. But the inhaler wasn’t working.”
Davidson has other symptoms, including headaches. She says a lump also developed in her face beneath one of her eyes, of which she sent me photos. Despite concerns that something in the air from the fire may have made her sick, she hasn’t left her home, a house she’d lived in since she was a child.
Part of the reason: No one is telling her to leave.
Officials in Monterey County, where Moss Landing is located, acknowledged to me in a statement that they received reports from medical providers that local residents sought care for symptoms related to the battery fire. The EPA said on January 20 that air monitoring throughout the fire incident found no substantial releases of hydrogen fluoride, a fatal pollutant released from battery fires. Records indicate that EPA tested for the particulate matter as well, but there’s no evidence it monitored specifically for heavy metals in the air. Vistra told me it has been doing environmental observations since the incident and is sharing the results with regulators, but said in a statement that it “has not detected risks to public health at this time.”
Davidson may have stayed, but others have left Prunedale, including Brian Roeder, who remembers seeing the fire break out while at home and deciding to leave town with his wife and son out of an abundance of caution. When they got back days later, the fire had been put out. But Roeder told me his wife, who he said is immunocompromised, began reporting breathing issues shortly after they returned. His son started coughing, as well. They quickly left home again, and have been living out of short-term rental apartments far away from the battery plant for weeks.
“This community has been significantly damaged, and they are not coming in to help anybody,” Roeder told me. “There’s been behind the scenes efforts, there’s been some work, but nothing commensurate with the size of this disaster.”
“I know that L.A. caught on fire at the exact same time,” Roeder continued. “That was the huge focus for the state. I know that planes were going down and we had a change in administration. But the fact remains that we, here, cannot explain the absence of support for what is happening from the state. And there’s been a pronounced absence.”
Roeder also started a community organization called Never Again Moss Landing, which has been collecting its own samples of the environment in consultation with a professional lab. In doing so, Roeder became part of a broader effort in the U.S. to create public safeguards for battery storage technology in the wake of Moss Landing. Ground zero for this push is, fittingly, California, where the state Public Utility Commission has responded to the fire by requiring battery storage facility owners to make emergency response plans and adhere to modern fire codes for battery storage.
Some Democratic lawmakers in California want to go further, empowering localities to be the final decisionmakers on whether storage projects get built, as opposed to state regulators.
In some pockets of the U.S., this push for battery safety risks morphing into a threat to the energy transition. For my newsletter, The Fight, I’ve chronicled how towns and counties across the U.S., from New York City to rural Texas, are now banning battery storage, citing the Moss Landing fire and the fear another battery fire could happen in their backyards.
By many metrics, Moss Landing is an outlier. The Moss Landing facility was a giant field of batteries inside a former factory, essentially trapping all these combustible mini-bombs prone to “thermal runaway,” a phenomenon where rising heat from a fire leads to a chain reaction of chemical ignition, inside an insulated box. Concerns about thermal runaway are a reason why almost all battery storage today is installed in storage containers and with an appropriate distance between individual batteries.
But Moss Landing is also a crucial test case for the future of battery storage and public trust.
This morning, the renewables sector took a big stride towards attempting to calm the rage against battery storage. American Clean Power, the leading renewables trade group, released an analysis of 35 battery storage fires in the U.S. from 2012 through the end of last year. Many of the incidents involved “early-generation” battery tech, it said, adding that “improved safety measures, such as advanced thermal management, suppression systems, and containment enclosures, significantly reduc[ed] the likelihood of large-scale incidents.”
The analysis does not speculate as to what may have caused the fire at Moss Landing, simply noting investigations into the incident are ongoing. But at the same time, ACP released a new blueprint for safe battery storage development. In the blueprint, the association acknowledges that some of its recommendations — including a requirement that all battery storage facilities meet a new fire safety standard produced years after Moss Landing was commissioned — are aimed at “holistically addressing concerns generated by the Moss Landing Fire.”
Residents are deeply suspicious of the official assessments denying what, to them, are obvious health impacts. To be candid, I can’t blame them. It strains credulity to imagine a battery fire of this size and scope right next door to you somehow creating no pollution worthy of public concern.
“When you burn [batteries] it moves toxic chemicals into the air,” said Tracey Woodruff, a former EPA senior scientist and policy advisor specializing in chemical contamination of the environment, who now works at the University of California San Francisco. “If this is an uncontrolled burn, you can’t just say there isn’t going to be fallout from that or exposure to the population.”
There’s data making people afraid too. In late January, researchers at San Jose State University alerted the public that they’d discovered “unusually high concentrations of heavy-metal nanoparticles” and a “hundreds- to thousand-fold” increase in nickel, manganese, and cobalt — metals all present in Moss Landing’s batteries — in soil two miles from the power plant in the Elkhorn Slough Reserve, one of the state’s biggest estuaries. Exposure to these metals can cause serious health issues, some of which mirror the symptoms described by residents in the area who are sick.
Exposure to dust with heavy metals can be dangerous at even relatively low levels. A county health advisory shared with local medical professionals in February urged doctors to complete a comprehensive physical of anyone concerned about the impacts of the fire on their health. It noted that breathing or coming into direct skin contact with “heavy metal dusts and other particulate matter from smoke” can result in a metallic taste and difficulty breathing, as well as exacerbate underlying conditions like asthma.
Discovering the metals’ omnipresence in the Slough after the fire led Ivano Aiello, a researcher at SJSU who collected that data, to conclude that the contamination is probably more widespread than is publicly understood.
“I freaked out [after the study] because I was breathing the stuff. I was out there for days and I had no idea,” he told me. “Then I alerted the authorities … and they did their own investigation.”
Subsequent studies conducted by county and state environmental officials, including within the Elkhorn Slough, found no level of these heavy metals that they said could be conclusively tied to the fire. On March 19, farm advisors at the University of California Cooperative Extension undertook a “limited study” that found a “slight deposition of metals (copper and manganese) may have occurred in one agricultural field closest to the battery fire site,” but that the “concentration of metals measured were within normal ranges for all soil types evaluated.” Dole, the giant produce company, which has operations in the area, told me that on its end “no health impacts have been reported and no soil contamination has been detected as a result of the Moss Landing battery fire.”
But Roeder and many other members of the surrounding communities are worried there isn’t enough testing being done to find out whether contaminants entered the atmosphere, especially since air pollution is rarely spread evenly. Like Covid-19, the only way we will ever know the extent of the problem is with more testing, testing, testing.
Roeder is trying to do this work himself. On what he says is his own dime, he and other members of Never Again Moss Landing have collected dust samples across the region in consultation with a credentialed lab in the state, BioMax, which he told me reached out after the fire.
On Wednesday, a local NBC affiliate reported that Don Smith, a toxicologist at the University of California San Diego, confirmed elevated levels of nickel, cobalt, and manganese in the dust samples collected by Never Again Moss Landing. “There is reason to be concerned,” Smith told the TV station, adding that people living near the plant should wear masks regularly if they’re interacting with dust in their homes and be careful not to disturb soil in their yards. “Both manganese and, to a lesser extent, cobalt are known to be neurotoxins. And nickel, of course, is recognized as a carcinogen.”
Frustratingly, though, there is no solid proof to date of a conclusive link between the illnesses and metal exposure — just a lot of people with symptoms, a study that hasn’t been replicated in other pieces of research, and samples collected by residents who are also involved in litigation against the company. Still, that’s a lot of evidence of a problem. Medical mysteries are also common in environmental catastrophes like the Flint water crisis and the infamous DuPont PFOA debacle in Parkersburg, West Virginia, in which obviously sick residents butted heads with regulators for years, demanding information and testing.
What’s next for Moss Landing? The three counties most impacted — Monterey, Santa Cruz, and San Benito — just concluded a community health survey that solicited comments from potentially impacted residents and received more than 1,500 responses, according to figures I reviewed that were shared at a recent Monterey County public meeting. When that study is out, we’ll have a comprehensive view of the locations where the sick live to see where it lines up with the plume that emitted from Moss Landing.
Taking a wider view, any society that’s going to rely primarily on intermittent energy sources like solar and wind needs battery storage to keep the lights on. That will require winning the public’s trust in battery technology. The Moss Landing fire was bad, and over time risks becoming an East Palestine moment for the energy transition. But the lack of a loud, sizable government response to calm the nerves of people publicly claiming illness is likely to be even more damaging to the future of the battery sector.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Plus, the Trump administration appointed a new “beacon of rational thought.”
We got a look at another major tech company’s latest energy and carbon emissions data — and it’s a doozy. On Wednesday, Microsoft released its annual sustainability report, giving us another year’s worth of energy and emissions data for a company that Heatmap’s annual insiders poll once judged to be one of the best hyperscalers for climate change.
The headline: Microsoft’s climate pollution surged last year. Its carbon emissions increased 25% year-over-year, the biggest single-year rise since at least the pandemic. The company emitted the equivalent of 21 million tons of carbon dioxide in 2025, under standard measurement methods. (It emitted slightly less under its own bespoke measurement system, which counts fuel credits and customer energy use differently.)
Electricity, which the company is buying in larger amounts than ever before to power AI data centers, is driving a good share of that increase. In 2024, carbon pollution produced by generating electricity (as well as from making chilled water and steam) was responsible for 2% of Microsoft’s total corporate carbon footprint. In 2025, that same category made up 13% of its overall emissions. The company’s power use rose by more than 24% over the same period.
That means Microsoft’s power use isn’t rising as fast as other companies’. Google’s most recent sustainability report said its own electricity consumption leapt 37% during the same period.
The report suggests, too, that Microsoft is increasingly wary of local fights over data center development — and how water has come to play an outsize role in those battles. The company reports that 2025 was the first year ever that it “replenished” more water on global scales than it withdrew. But “the next phase of our work is increasingly local,” write Brad Smith, the company’s vice chair and president, and Melanie Nakagawa, its chief sustainability officer. That line is clearly in reference to water, specifically — Smith and Nakagawa add that the company hopes to “restore more water to the watersheds where we operate than we withdraw” — but it could also cover the widespread local opposition to data centers that has exploded over the same period.
There’s one more thing to flag about this report: Although it just came out, it covers Microsoft’s 2025 fiscal year, which began in July 2024 and ended more than a year ago. That means it’s inherently an out-of-date view — it shows us what Redmond was doing as the AI and data center boom got underway, but not what it’s doing now. We’ve known for some time that the company is struggling to meet booming AI power demand while maintaining its power commitments; it paused carbon removal buying in April and revised its own clean energy commitments in May.
I should add that Microsoft would prefer that we look at other numbers in the report. First, under its in-house measurement scheme, the company says it released only 20 million tons of carbon pollution over the past year, a figure that appears in its top-line charts. Second, Microsoft estimates that it would have done even more harm to the climate — producing 34 million tons of climate emissions — if not for its corporate policies of buying zero-carbon electricity, using renewable fuels, and improving the energy efficiency and carbon footprint of its XBox game consoles and Surface tablets.
We asked Microsoft for a follow-up interview, but unfortunately they didn’t make anyone available. I’ll be back tomorrow to look at Microsoft’s report in context with other hyperscalers.
Speaking of a sudden rise in gaseous emissions, the Trump administration today named a new leader of the federal government’s marquee in-house climate research office, the U.S. Global Change Research Program. Per Politico, the new top dog is Matthew Wielicki, a UCLA PhD who (1) has a Substack, (2) refers to himself (in the third person) as a “beacon of rational thought” and “professor in exile” on said Substack, and (3) has suggested on X that climate change belongs in the “Department of Imaginary Problems.”
What can I say? Back during President Trump’s first term, his administration tried to bury the publication of the National Climate Assessment by dumping it on a holiday weekend. Now it seems to have taken another strategy. All I can say is, Dr. Wielicki, from one beacon of rational thought to another: I look forward to following your work.
Water pollution in Wyoming has big implications for the future of data center development.
Did a Meta data center introduce a rare, dangerous bacteria into the sewers system of Wyoming’s capitol city? It’s an environmental pollution mystery with an answer that could decide the future of American AI infrastructure development.
Our drama begins in Cheyenne, Wyoming, where the city’s board of public utilities just wrapped up a lengthy investigation into the presence of Cupriavidus gilardii, a potentially lethal bacteria resistant to heavy metals, in the city’s wastewater treatment systems. Apparently, in February, board staff detected the contamination and shut off public access to the city’s water reuse system, a supply of treated non-potable water fed with treated wastewater and used for lawns, athletic fields, and other green spaces. Officials were worried that spraying this water could release into the environment a bacteria found to cause fatal health outcomes in immunocompromised or elderly people who are infected by it.
The board then identified a culprit – Goat Systems LLC, a Delaware-registered firm without a website Meta tasked with overseeing its large $800 million hyperscale project in Cheyenne dubbed Project Cosmo. Goat Systems lost its wastewater disposal permit. The board plans to also fine Goat Systems for violating city code “along with additional fees for our remediation efforts,” board public affairs coordinator Erin Lamb told me in an email. (The only person publicly affiliated with Goat Systems is Pamela Gregorski, an employee for a company that specializes in creating LLCs. Gregorski, who is linked to other LLCs handling Meta projects across the country, did not reply to requests for comment.)
In public comments and statements to me, the board linked the bacteria to water used to flush the Meta data center’s closed-loop cooling system so debris could be removed before the facility was operational. “We were able to connect the Meta data center campus to this through sampling their site,” Lamb said.
This finding led Cheyenne to also indefinitely ban data center projects in the city from ever disposing of “fill-and-flush water” in the sewer system again.
Meta has not denied contamination was found by the city, but says repeated sampling at its project site failed to come up with any evidence confirming they were the source. One can imagine a scenario where the data center and its design played no role in this bacteria showing up, or that city officials erroneously tagged the tech company with responsibility at a time when they’re dealing with political troubles already.
But what is happening in Cheyenne, first reported last week by Wyoming local press, will have consequences for the future of AI infrastructure whether or not Meta was actually even responsible. Right now, all over the country, tech companies are failing to get permits for their data centers because people are worried about water use. These closed-loop data center designs are supposed to address those concerns, letting large hyperscalers contain, cycle, and reuse the water they use for months or even years. A story like this gaining traction in public discourse around data centers will inevitably damage the sector’s public image unless rectified – and fast.
Cheyenne’s claims about the Meta data center being responsible for the bacteria have already metastasized on social media, disseminated through channels often cited by data center opponents on the ground elsewhere in the country. “REPORT: ‘RARE’ BACTERIA DISCHARGED INTO WYOMING WATERSHED LINKED TO DATA CENTER,” reads one post by a Facebook user Izzy Bella that has been shared more than 2,600 times. “Think of this the next time you hear blatant greenwashed lies like ‘closed loop cooling.” This post has been shared by major anti-data center groups on Facebook, including Pennsylvania Data Center Resistance, a social media page for organizing against projects in the Keystone State.
Going solely off what happened in Wyoming, some in the state are concerned the process of cleaning these loops before opening a data center can produce some nasty byproducts. Dr. Jonathan Brand, a civil engineering professor at University of Wyoming, has been studying the data center buildout in Wyoming for years, watching what’s happened in Cheyenne closely, and like me has way more questions than answers.
Usually, Brand said, a company using water in metal-intensive industrial applications – think a metal plating facility – has to test that fluid before it’s dumped into a municipal sewer system. The chain of events spelled out by the board left him “guessing that didn’t happen here,” and he’s worried the bacteria formed within whatever petri dish-like environment was created inside the network of looping pipes before it was flushed.
“The bacterium was the canary they saw, but you could have a lot of residual metals, which is not something we normally test for at a wastewater plant,” he said. “What else was in that discharge? Nobody else has let us know that and they’re probably not going to.”
City officials claim the water was tested before it entered the sewer and was missed, but there’s a trust deficit between locals and the government on what happened. Little of this information was public until a few weeks ago. Cheyenne residents first learned trouble was afoot on June 26, when the board posted a press release “reminding all residential, commercial, and industrial customers that the discharge of hazardous substances into the sanitary sewer system is strictly prohibited.” Nothing was included about data centers at all; all the board said was that the bacteria was dumped by “an industrial user within the system.”
Then Exie Brown, a Cheyenne resident and GOP candidate for state house, blasted a press release out on social media declaring “a credible source with knowledge of the [board] investigation and sampling” told him the “industrial user” was a data center.
I reached out to Brown asking how he learned about this. His answers were cryptic. “I was given a piece of paper with that name of a bacteria on it,” he told me over the phone, declining to name the “very credible source” who told him about the contamination. “That it was released into our waste water system, that it came from a data center, that it was Meta, that they found out in February, and I needed to check into this.” When I asked why the piece of paper, he replied: “Because they [the source] wanted to keep this quiet. Off the phones and stuff.”
City officials deny any malintentions behind the delay and claim they’re learning about all of this at the same pace as the average resident. “We learned here a week or so ago,” Cheyenne mayor Patrick Collins told me in an interview. He added this wouldn’t have stirred as much interest “had it been something else,” referencing the fact it was from a data center.
“As I understand it, the contractor that was building the site was flushing out a closed-loop cooling system, and when they tested the water everything seemed to be fine, but when it was released into our system, bacteria had grown and was released into our wastewater treatment,” Collins said. “It just happened to be a data center. It’s an unfortunate and highly regrettable situation.”
The mayor acknowledged this contamination will make it “a little tougher” to argue for more data centers in the city. There are currently 10 operational data centers in Cheyenne and surrounding Laramie County, according to estimates from pro-business group Cheyenne LEADS, which has said five projects are under construction – including the Meta facility – and at least nine others are “in various stages of planning or due diligence.”
On Monday, the Cheyenne city council will vote on whether to annex land owned by various nearby property owners for more data center deals, including parcels owned by the family of U.S. Senator Cynthia Lummis. Before this event, Cheyenne was incredibly resistant to the anti-data center backlash, handily rejecting proposals to pause development.
Collins thinks Cheyenne will still be open to the tech sector. But the bacteria changed things. “I recognize there’s going to be challenges as we move forward. It’s something we’re going to have to look into. This was a regrettable situation that happened.”
We will see more transparency soon from the Cheyenne city government about the contamination. The board tells me it’s planning a press conference next week where Lamb told me “more information will be made available.”
Francis Brennan, a public affairs manager in the company’s strategic response division, provided me with a statement from an unnamed “Meta spokesperson” claiming that Fortis – the construction company hired by Meta and Goat Systems LLC – was directly handling water disposal on site. After the board “shared that it found a substance in the city’s wastewater” the construction company “began hauling it offsite.” Meta claimed Fortis has not been able to corroborate the presence of this bacteria in comparable water samples.
“Meta is committed to being a good neighbor in Cheyenne, including through the protection of local water resources, and will continue encouraging collaboration between Fortis and the board until this situation is revoked,” the statement read. Meta declined to answer follow-up questions..
Fortis confirmed they were responsible for dumping water on site when the contamination was discovered. They stated they’ve been unable to confirm the presence of the bacteria. In a statement provided to me, the company said: “Immediately upon learning of the issue, we stopped discharging water into the city’s wastewater system. We have since engaged in a thorough investigation that has included ongoing repeat testing by independent environmental specialists and have found no trace of the substance.”
A conversation with Ross Marchard of the Taxpayers Protection Alliance
This week’s conversation is with Ross Marchard, executive director for the Taxpayers Protection Alliance, a center-right advocacy group that focuses on what it sees are onerous policies potentially hindering responsible collection and use of tax dollars. TPA’s position on AI clearly skews pro-free market, as they’ve recently defended Anthropic from Trump administration attacks. TPA also recently took on the mantle of defending data centers from noise complaints, publishing a paper on Tuesday “debunking myths about data centers being excessively noisy.” The paper references various analyses of data centers by state legislators and local regulators to argue that claims the sector is generally noisy are false.
I asked TPA’s executive director to chat with me about why and how the organization will try to quell these fears. The conversation was really interesting so I decided to share it with you in full, sans light editing for clarity and consistency.
What prompted you to write this report?
Obviously, data center projects have been getting so much media attention. With that attention there’s an outsized share of misinformation in coverage of these data center projects, and politicians have irresponsibly spread this misinformation to try and enact moratoria and heavy-handed restrictions on these projects
TPA wanted to get the truth out. Make sure local residents living alongside these data centers have access to all the information they need. Make sure this misinformation is countered.
Before we get into the noise aspect, how is this focusing on “taxpayer protection”?
Sure, well, great case in point is Loudon County. They’ve embraced data centers and look what’s happened, they take in a billion dollars a year in revenue from these data centers and it’s allowed them to lower property taxes. You see a wider pattern across communities. They rake in a tremendous amount of tax revenue and increasingly common well-paying jobs, six-figure blue collar jobs that are a direct result of allowing data centers into communities.
I know you’re based in D.C., near Loudon County. I went to a data center in Sterling, Virginia, in that county, and it was especially noisy. Sort of a worst case scenario on that. Your report talks about misinformation around noise and data center – where is the misinformation happening on this issue?
We saw a recent court case out of New Jersey that alleges data centers generally are as loud as helicopters. Look, anything is possible for a particular project. But what we can say based on our analysis of the data, studies and sound impact assessments, and analyses by state and local governments is that this isn’t the case for the vast majority of data centers.
No use of land is going to be sound-free. I live right on Georgia Avenue in Washington, D.C., so I know noise. But everything we analyzed showed data centers and energy generation on site are going to make some noise but not enough to be harmful to human health. Often it’s no louder than the typical conversation between two people.
Speaking of Loudon County, though, I can point to an example of a project I myself visited that was I’m sure welcomed at first on tax revenue grounds. Now people seem to regret that decision.
As someone trying to address those who are concerned, is it helpful for you to really just call this concern rooted in misinformation? Is this really going to be potent when projects like the one in Sterling exist?
First and foremost, it’s very important to listen to people and their concerns. If folks are living alongside a data center and say they’re hearing loud noises, that warrants investigation. But it’s also important to look at the full array of evidence and we’ve done that. So far, it does not appear to be the case based on the overwhelming amount of evidence that is publicly available that data centers use a lot of water, use inordinate amounts of electricity, or are loud in a way that disrupts human health.
What do you think the policy solutions are to address these noise concerns? How do you listen to people, without going into overgeneralization, as you put it?
People tend to point out the loudest data centers are the ones with on site energy generation. If you ask the operators of data centers and the companies building data centers, they’ll tell you more often than not the reason they’re putting generation on site because the utility permitting process takes far too long. That’s the result not necessarily of utility regulations but state regulations foisted upon utilities. So you have to look at everything from state regulation to grid operation regulation. If you make the process easier for data centers to get hooked up to the grid, you’ll see less on site energy generation, and a lot of the noise complaints will go away.
So from your standpoint, a solution to the noise complaint is that it should be easier to hook up to the grid?
Yes. If you allow data centers to get hooked up to the grid, you’ll see fewer diesel generators and that’ll mean fewer noise complaints.
Now, I want to be clear, the vast majority of data centers with noise complaints – those are usually because of on-site energy generation – are not unduly noisy. If you want to cut down on those complaints, what makes the most sense is to make it easier for data centers to hook up.
Fun question to close: what was the last song you listened to?
“Yellow” by Coldplay.
Are you listening to “Yellow” while you’re writing about data centers?
I listen to the song sometimes when I’m writing about data centers. It’s also a very good somber reflection song, which is a pretty common sentiment amongst millennials.