Correction Record What the Cheyenne water contamination posts got wrong Last updated: 21 July 2026 A real regulatory case is circulating on social media as a public health scare. Cheyenne cited a Meta construction contractor for discharging a rare bacterium into the city reuse water system, then fined the contractor $10,000 and barred the discharge. The bacterium reached irrigation water, not drinking water, no illnesses have been reported, and the contractor is appealing. This is the gap between the record and the posts. Figures labeled claim are operator-stated or agency-stated and not independently audited; derived figures are calculated here. Sources are listed at the foot of this article. What actually happened, from the primary record On 15 January 2026, staff at the Cheyenne Board of Public Utilities noticed unusual white bacterial colonies on petri dishes during routine fecal-coliform testing of wastewater. The Wyoming Public Health Laboratory identified the organism on 23 February as Cupriavidus gilardii , a metal-resistant bacterium that occurs naturally in soil, groundwater, and surface water. On 24 March, lab sequencing tied the organism to a construction discharge from the Meta Cheyenne Data Center site, operated for the build by Goat Systems LLC through its contractor Fortis Construction. The discharge was fill-and-flush water from a closed-loop cooling system being commissioned. A closed-loop system is filled once, flushed to clear construction debris and pipe scale, then sealed. The data center is still under construction and not yet operating. According to the utility, a total of 801,475 gallons of wastewater was discharged across January, February, and March, and every sample taken during that window fell within the allowable limits for the additives the contractor had disclosed in advance. The bacterium was not on that disclosed list. That is the complete factual core. Everything beyond it is either the utility acting with caution or the internet adding weight the record does not carry. How the utility traced it to the contractor The tracing is the part most worth understanding, because it is stronger than proximity but narrower than the headlines suggest. The utility did not start at the data center. It started with the bacterium and worked backward, and the finding rests on a direct sample rather than a guess about the newest tenant. The sequence, from the utility timeline, runs like this. On 15 January, lab staff spotted unusual white bacterial colonies while running routine fecal-coliform tests on effluent from both wastewater plants. Samples went to the Wyoming Public Health Laboratory on 12 February, and on 23 February the state lab identified the organism as Cupriavidus gilardii . Only then, on 10 March, did the utility begin checking industrial dischargers, and it prioritized the Meta site because it was the newest one connected to the system. That prioritization alone would be weak evidence. It is not what the finding rests on. The evidence is a positive match from the site itself. On 18 March, staff collected water from the predischarge storage tank at the Meta Cheyenne Datacenter CHY1-2 site and sent it for genetic sequencing. On 24 March, the state lab reported that the sample contained Cupriavidus gilardii , the same organism found in the city system. The utility also ran a control: on 30 March it sampled three Microsoft campus sewer outfalls, and those came back negative. One discharger's water carried the bacterium and a comparable one's did not, which is why the utility named a source rather than describing a citywide condition. What the sample proves is bounded. It shows the bacterium was present in the water leaving the contractor's site. It does not show where the bacterium came from or how it entered that water. The utility states plainly that it does not know how the organism got into the discharge, and its own later sampling found the same bacterium occurring naturally in Cheyenne lakes and ponds with no data center connection. So the discharge is the documented route into the sewer, not a proven origin. That distinction is the ground the contractor is contesting: Goat Systems has appealed the citation and, per local reporting, has asked the utility for the underlying sampling data, chain-of-custody records, and lab analyses that link the contamination to its site. The utility also says it does not believe the discharge was malicious. The documented sequence from first detection to the contractor's appeal. Source: Cheyenne Board of Public Utilities timeline and FAQ, 20 July 2026. What the coverage added Each record below sets the reported framing against what the Cheyenne Board of Public Utilities documented in its 20 July timeline and FAQ. Reported Viral posts and headlines described the city water system being contaminated, inviting readers to picture their tap. Record The utility states the incident never affected drinking water. It involved the reclaimed water system, treated wastewater used to irrigate parks and a golf course. The predischarge tank sampled at the site was not even connected to the sewer at the time. Reported A harmful, deadly bacterium threatening communities downstream. Record The utility reports no confirmed illness. During the two days contaminated reuse water reached the Prairie View Golf Course, no members of the public were present. Some bacteria passed into Crow Creek, which the utility classifies as 2C water, not used for drinking and not known to support game fish; both treatment plants passed their toxicity testing. The mortality figures circulating online come from a separate medical case series of roughly 32 rare infections in immunocompromised patients, not from Cheyenne. Reported Meta contaminated the water, stated as settled. Record The citation went to the contractor entity, Goat Systems LLC, not to Meta directly. Goat Systems has appealed the violation and requested a hearing, so the finding is contested, not final. The utility says it does not know how the bacterium entered the discharge and does not believe the discharge was malicious. CLAIM Reported The data center introduced a bacterium foreign to the area. Record The utility later tested its own surface waters and found the same bacterium occurring naturally in Sloans Lake, Kiwanis Lake, Peanut Pond, and other sites with no data center connection, confirmed by the state lab on 8 June. The organism is ambient in Cheyenne. The data center discharge was the identified route into the sewer, not the origin of the bacterium. The story that is actually supported Strip out the scare framing and a real story remains. A metal-consuming bacterium that can corrode piping, and that the contractor never disclosed, entered a municipal reuse system through construction water. The utility spent months flushing sewer mains, disinfecting a three-million-gallon pond with chlorine and sodium hypochlorite, and substituting drinking water for irrigation while it worked. It then issued a Notice of Significant Noncompliance, an administrative $10,000 fine, and a surcharge for cleanup costs that has not yet been totaled. The genuinely new development is the policy. Cheyenne now refuses fill-and-flush and closed-loop cooling wastewater from all data centers until further notice, and requires future projects to haul that water to specialized treatment facilities rather than send it to the city sewer. For a region rezoning thousands of acres of ranch land for data center campuses, that is the consequential part, and it is one of the first municipal discharge bans of its kind tied to AI infrastructure construction. Does this affect Cheyenne residents? By the utility's account, drinking water was never involved and no illnesses have been reported. The direct effects were operational: a suspended reuse irrigation program, potable water used on parks and a golf course for several weeks, and months of staff time and chemical treatment. The utility notified the Wyoming Department of Environmental Quality on 24 February and county public health on 18 June, and defends its four-month delay in a public notice by saying it judged the risk low and wanted to avoid public panic. Whether that delay was appropriate is a fair question, and it is the part of this story most worth watching, not the bacterium itself. Sources Cheyenne Board of Public Utilities, timeline of events regarding Cupriavidus gilardii , released 20 July 2026 (primary). Document Cheyenne Board of Public Utilities, frequently asked questions on the Notice of Significant Noncompliance to Goat Systems LLC, 20 July 2026 (primary). Document Alyssa Tolman, "Cheyenne BOPU traces rare bacteria discharge to Meta data center contractor," Wyoming Tribune Eagle, 2 July 2026. Article Angus M. Thuermer Jr., "White colonies of petri dish bacteria led to data center pollution fine," WyoFile, 20 July 2026. Article "Meta appeals Cheyenne BOPU's violation notice linking its contractor to contamination," Cap City News, 15 July 2026. Article Derivations disclosed No figures in this article are derived. The discharge volume (801,475 gallons), the fine ($10,000), the dates, and the water classification (2C) are each stated directly in the Cheyenne Board of Public Utilities timeline or FAQ. The mortality context is attributed to the medical case series named in secondary coverage and is not applied to this event. Open questions The origin of the bacterium within the contractor's discharge is unknown, per the utility. The total cleanup surcharge has not been determined. The appeal by Goat Systems is unresolved, and its outcome will decide whether the citation and fine stand. This article will be updated as the hearing proceeds. Corrections policy AI Race Facts corrects errors visibly, with a dated note stating what changed. If any figure or attribution here is shown to be wrong, the correction will appear at the foot of this article rather than as a silent edit. Last updated: 21 July 2026