Oklahoma city condemns container Bitcoin mining site after three-million-gallon water leak
A facility operating under a 2023 stop-work order shows why utility connections and permit compliance are part of data centre risk.
A cryptocurrency mining facility in El Reno, Oklahoma, has been condemned by the city after a leak released roughly three million gallons of water and forced local schools to close, according to a Tom's Hardware report published on 6 September that cites local station KOCO. The site is operated by Athlon Blockchain LLC and consists of computing equipment housed in shipping containers.
The water escaped from an underground fire hydrant line on the property. The loss was large enough that schools, businesses, and city and county offices in El Reno closed during the preceding week. The city has since said it will carry out routine compliance reviews and is preparing legal action to recover the costs it incurred.
The regulatory history reported alongside the incident is what has drawn attention. El Reno issued a stop-work order against the facility in 2023, citing multiple fire and life-safety code violations together with expired building and electrical permits. The property owner was given until the end of 2023 to bring the site into compliance. According to the report, the facility nevertheless continued to operate in the years since.
Few technical details of the leak itself have been published beyond its source and volume. What is known is that the failure was on infrastructure connected to the municipal supply, that it affected the wider community rather than only the operator, and that it occurred at a site the city had already flagged as non-compliant. The report does not describe what caused the line to fail or give a timeline for repairs, and it notes that the facility had operated for years despite the order.
Why it matters
Data centres of every kind, from hyperscale AI campuses to container-based mining sites, depend on municipal water and power in ways that are invisible until something breaks. This case shows that a facility's risk to its neighbours is not only about how much it consumes but about whether its infrastructure is built and maintained to code. As communities weigh new data centre proposals, permit compliance and enforcement are becoming as central to the conversation as megawatts. The episode is also a reminder that stop-work orders only matter if they are enforced.
Data centres of every kind, from hyperscale AI campuses to container-based mining sites, depend on municipal water and power in ways that are invisible until something breaks.
Permits expire and code violations found
Building and electrical permits lapsed; fire and life-safety violations recorded.
Stop-work order issued in 2023
Owner given until the end of 2023 to bring the container site into compliance.
Facility keeps operating
The report says the site ran for years after the order.
Hydrant line leaks about 3 million gallons
Schools, businesses and city and county offices close for the week.
City condemns site and seeks costs
Routine compliance reviews promised; legal action to recoup costs being prepared.
What you can learn from this
Data centres are tied into shared utility networks. A fire hydrant line on a private site is fed by the same pressurised municipal main that serves homes and schools, so a break anywhere on that line drains the shared system. Utilities size mains for expected demand, and a single uncontrolled outflow of millions of gallons can drop pressure across a district. That is why an incident on one property can close public buildings that have no other connection to it. Boil-water notices often follow as well, because low pressure can let contaminants enter the pipes.
Fire protection and process water are different systems with different rules. Hydrant and sprinkler lines must stay pressurised and are governed by fire codes, while cooling water is governed by plumbing and environmental permits. Container-based mining sites often rely on air cooling and need little process water, but they still require compliant fire lines because of the electrical load inside each container. Understanding which system failed tells you which code, and which inspector, is responsible.
Permits and stop-work orders form a compliance chain. A building permit certifies that plans were reviewed; an electrical permit covers wiring and load; occupancy or operating approval follows inspection. A stop-work order suspends that chain until violations are fixed, and expired permits mean the chain was never completed. When a site operates through an order, the paper trail becomes the basis for later legal action, which is why cities document these steps carefully. For a learner, the practical lesson is that a permit is evidence of review, not a formality.
Modular and containerised builds trade speed for scrutiny. Shipping-container data centres can be deployed in months rather than years and moved when power prices change, which suits cryptocurrency mining. The downside is that they can be treated as temporary equipment rather than buildings, and the utility connections that serve them may not get the same engineering review as a permanent structure. Jurisdictions differ on how they classify them, and that ambiguity is where compliance gaps appear. Ask which classification applies before assuming a site was inspected.
Siting risk includes the operator's neighbours. Traditional data centre risk assessments focus on threats to the facility: power loss, flooding, fire. This case points the other way, at the harm a facility can cause to its surroundings when infrastructure fails. Modern siting reviews increasingly ask both questions, which is why grid impact studies and water impact statements are becoming standard parts of an application. The neighbours are stakeholders whether or not they are customers.
We teach this
How to use this in practice
Map the utility dependencies of one facility you know. Take a server room, office, or a local data centre and draw every inbound connection: electrical feed, water main, fire line, network. For each, write who owns it, who inspects it, and what happens downstream if it fails. Mark which connections are private up to the property line and which are shared beyond it, because that boundary decides who is exposed when something fails. Done is a one-page dependency map with one named contact per connection and at least one item you could not answer, which is the item to research next.
Look up the permit record for a real site. Most cities publish building and electrical permit searches online. Pick any data centre or industrial address near you, find its permits, and note whether they are active, expired or closed. If your city does not publish one, note the department you would have to call instead; that gap is itself a finding. Done is a short record of what you found and how long it took, so you understand what a compliance check actually involves.
Audit a small computer room against basic fire and electrical checkpoints. Walk through a room you have access to and check that circuits are labelled, that load per circuit is documented, that extinguishers are in date and that nothing blocks exits. Photograph anything that fails so the fix can be verified later, and write down the load figures rather than trusting memory. Done is a checklist with a pass or fail beside each line and a date for the next review.
Draw the compliance timeline as a flow. Put the reported steps in order: permits expire, violations found, stop-work order issued, deadline passes, operation continues, incident occurs, city acts. Under each step, note what control could have interrupted the sequence. Then draw a second version in which the order was enforced, to make the difference visible. Done is a diagram you could show a planning committee to explain why enforcement matters.
Sources
Our reporting is an original summary; full coverage is at the links above.
Don't just read about it — build it.
Square 1 teaches the skills behind the headlines, with every line of your work graded by AI. Find your starting point in 3 minutes.
Get your free skill report