DePIN capacity utilisation

Why this and not node counts. Node count is the number most DePIN dashboards lead with, and it is the easiest to grow without demand. The question that separates infrastructure from subsidy is what fraction of that deployed capacity is doing paid work — capacity growing faster than utilisation is overcapacity, not growth. Every figure below is computed from the network’s own public endpoint, and every row links to it.

These are not utilisation. They answer “what fraction of registered nodes are switched on?”, which is fleet health, not busy hardware. We separate them because publishing both in one table invites a false reading: a network showing 99% liveness is not “better utilised” than one showing 27% CPU utilisation — the two numbers answer different questions. Where a network’s denominator is cumulative registrations rather than a live fleet, that is flagged inline.

Refused: IO gpus utilisation.
io.net's GPU_TOTAL is NOT registered GPU supply — it equals DEVICES_ACTIVE exactly on every archived day (1,213/1,213 ... 1,199/1,199), and GPU_HIRED + GPU_IDLE == GPU_TOTAL exactly. So hired/total is a FILL RATE on the already-active pool, near-tautological, and it excludes every passive device. It reads 96.7% while true device utilisation (active/registered) is 46.2% and FALLING — registered devices grew 2,057 -> 2,594 (+26%) in 7 days while active stayed flat near 1,200. Publishing 96.7% beside Akash's 30.5% (utilisation of REGISTERED capacity) would invert the actual story: io.net is the network accumulating idle supply fastest, not the one running hottest.

Scope, stated plainly. This covers the 3 networks where we hold both sides of the ratio from a first-party endpoint — not all 171 networks we track. Utilisation is undefined without a published capacity denominator, and most networks do not publish one. We are adding them as we verify them; the count above is the honest current number, and we would rather show 3 real rows than 171 modelled ones.

Ratios we refused to publish: one network reports storage-used exceeding storage-total by 64x, and another reports a lifetime-cumulative denominator that would yield a meaningless 0.1%. Both are excluded until the upstream fields are understood.

curl "https://kairossignal.com/v1/network/AKT"    # every metric, with source and as_of
curl "https://kairossignal.com/v1/supply"        # free 12-network sample