Categories
Mining Infrastructure

Selling more capacity than you can deliver is normal practice in enterprise colocation and structurally unsafe in Bitcoin mining. Why the difference exists and how to detect it.

Walk into a conventional enterprise colocation hall and ask the operator whether the sum of their customers’ contracted power exceeds what the building can actually deliver at once, and a competent operator will tell you yes. That is not a confession. It is the business model, and it is sound.

Ask the same question of a Bitcoin mining host and the same answer means something entirely different.

The difference is one assumption, and when that assumption fails it does not fail gracefully. It is worth understanding properly, because oversubscription is close to invisible from the outside until the moment it is extremely visible from the inside.

Why Overselling Works in a Normal Data Centre

Enterprise workloads are bursty. A rack of application servers provisioned for a worst-case afternoon spends most of its life well below that ceiling. Across dozens of customers with different businesses, different time zones and different peak hours, the individual peaks do not line up. The sum of what everyone could draw is far above the sum of what everyone does draw at any one moment.

Operators plan around that gap. The engineering term is diversity: the ratio between coincident demand and the total connected load. A hall designed to the sum of nameplate ratings would be enormously overbuilt, and the customer would pay for every unused amp.

So the contracted total exceeds the deliverable total, deliberately and safely, and nobody is harmed. The practice has decades of operational evidence behind it.

Why It Does Not Work for Mining

An ASIC miner has no bursty workload. It is given a job and it runs that job at essentially constant draw, continuously, until something stops it. There is no overnight trough, no weekend dip, no quarter-end lull. A hall full of miners from twelve different customers behaves, electrically, as one machine.

Diversity, in other words, is approximately zero. The assumption that makes overselling safe in enterprise colocation is simply absent.

This has a consequence that deserves stating plainly: a mining host who oversubscribes is not taking a calculated risk that peaks will not coincide. The peaks always coincide. They are taking a position that at some point they will have to take capacity away from somebody.

How It Shows Up

The host does not generally announce this. It surfaces as operational symptoms that look like other problems.

Curtailment that does not match the grid. Your machines are throttled or switched off, and the stated reason is a grid or demand-response event. Sometimes that is exactly what it is, and participating in those programmes is legitimate and can be lucrative, as our guide to curtailment revenue and demand response sets out. The question worth asking is whether the curtailment events you experience correspond to events you can verify independently from the grid operator’s own public data. Curtailment that does not line up with anything external is worth a conversation.

Reduced power mode presented as optimisation. Underclocking a fleet is a real efficiency technique with real justifications. It is also an elegant way to fit more machines into a constrained envelope while describing it as a service. The distinction is whether it was discussed and agreed, or simply appeared.

Breaker trips on restart, not during steady state. This one is diagnostic. A site can run comfortably within its limits for months and still trip when everything restarts together after an outage, because starting current exceeds running current. A facility that is comfortable at steady state but has a history of difficult restarts is telling you something about how little headroom it holds. Our note on transformer inrush current covers the mechanism.

New customers arriving without new infrastructure. The clearest signal of all, and the easiest to observe if you visit. Capacity that grows without transformers, switchgear or utility work growing alongside it came from somewhere.

Detecting It Before You Sign

Three questions do most of the work, and none of them is adversarial.

What is the utility interconnection rated at, and may I see it? Advertised capacity is a marketing number. The interconnection agreement with the utility is a document. If a facility advertises materially more than its interconnection supports, either an upgrade is genuinely in progress, with a timeline and a contract behind it, or the gap is being covered by hoping customers do not all run at once. Our due diligence inspection checklist treats this as a site-visit item, and it is the single highest-value question on this list.

What is the total connected load you have sold? Not capacity installed. Capacity contracted. Compared against the deliverable figure above, this is the whole question in one number. An operator who runs a straightforward business will answer it. An operator who treats it as commercially confidential has told you something anyway.

If every machine on this site ran at full draw simultaneously, what happens? This is the mining-specific version, and it is the one that separates hosts who have thought about their own load profile from hosts who have inherited a data-centre playbook. The honest answers are good answers: “we are sized for it,” or “we are not, and here is the contractual order in which capacity is reduced, and here is what you are credited.” The answer to be wary of is reassurance without structure.

If the answer involves credits, read how they are defined. A credit that only applies to a qualifying outage, where capacity reduction is explicitly excluded from the definition of an outage, is not a credit. Our guide to hosting SLAs goes through how those definitions are constructed.

Detecting It Afterwards

If you are already deployed, the evidence is in your own data rather than the host’s.

Independent measurement is the foundation. A host’s dashboard reports what the host chooses to report, and when capacity is being rationed the reporting is rarely where it shows first. Sub-metering at your own racks, covered in our guide to sub-metering and power monitoring, gives you a record that exists independently of anyone’s goodwill.

With that in place, the pattern to look for is correlation. Isolated throttling of your fleet alone suggests something specific to your equipment. Throttling that arrives at the same moment for everything on the site, repeatedly, without a matching external grid event, suggests a site-level constraint. Neither observation proves anything on its own, but a log of them is a very different conversation from a recollection of them.

It is also worth separating this from ordinary thermal behaviour. Machines derate in summer heat, and that is physics rather than overselling. Our material on rack density and airflow design covers how to tell a cooling limit from a power limit, and the distinction matters here: if the hall cannot remove the heat, more electrical capacity would not help you anyway.

Where Oversubscription Is Defensible

This is not a case that the practice is always wrong, and an article that said so would be misleading.

A host that explicitly sells interruptible capacity at a lower rate, states the terms, and reduces load in a published order is running a legitimate and useful product. Operators who can tolerate interruption get cheaper power; the host gets to use capacity that would otherwise sit idle. Several good businesses are built on exactly that trade, and it pairs naturally with demand-response participation.

The problem is not selling interruptible capacity. The problem is selling interruptible capacity at firm prices without saying so. The difference between the two is disclosure, and disclosure is visible in the contract.

The Short Version

Oversubscription in enterprise colocation is sound engineering resting on a real statistical property. Carried into Bitcoin mining, where machines run flat out continuously and diversity is close to zero, that property is gone, and what remains is an undisclosed queue for capacity that someone eventually has to be removed from.

You cannot see it from the outside. You can ask three questions about interconnection rating, total contracted load and simultaneous draw, and you can notice whether the answers contain numbers. Most of the risk in this topic is carried by people who never asked, not by people who got bad answers.

If you want those three numbers for a site you are considering, including ours, ask us. They are not confidential, and an operator treating them as confidential is itself the answer.

Explore Rax Mining

Categories