Node health — what the headline counts hide

Findings from first-party endpoints · generated 2026-11-19T03:55:01Z

Four findings were tested against the underlying tables before anything was written here. Two survived, one survived only as a level, and one was refused. The refusals are at the bottom and they are the point: any scraper can produce numbers, and a competitor pointed at these same endpoints would have published all four.

1. Akash: the GPU market is tightening

Available GPUs fell -51.4% while active rose +85.8%. Idle supply is being absorbed.

DateTotal GPUsAvailableActive Available share
2026-08-0942329412769.5%
2026-08-1044330413868.6%
2026-08-1142924917958.0%
2026-08-1243024418556.7%
2026-08-1342522719753.4%
2026-08-1441922219653.0%
2026-08-1541716724940.0%
2026-08-1640115424638.4%
2026-08-1741216324839.6%
2026-08-1842015026835.7%
2026-08-1942216026137.9%
2026-08-2042416625639.2%
2026-08-2142216425738.9%
2026-08-2242222120052.4%
2026-08-2342722320152.2%
2026-08-2443021021148.8%
2026-08-2543120322647.1%
2026-08-2643221022148.6%
2026-08-2743516626838.2%
2026-08-2843318424842.5%
2026-08-2942518124342.6%
2026-08-3042517125040.2%
2026-08-3143317825041.1%
2026-09-0144719325143.2%
2026-09-0244718426241.2%
2026-09-0345016728237.1%
2026-09-0445818027739.3%
2026-09-0545516229235.6%
2026-09-0645716828836.8%
2026-09-0744816527936.8%
2026-09-0845518327040.2%
2026-09-0945815729634.3%
2026-09-1044713930231.1%
2026-09-1145013430929.8%
2026-09-1244213729931.0%
2026-09-1344913530830.1%
2026-09-1444914828333.0%
2026-09-1544614027631.4%
2026-09-1643315826936.5%
2026-09-1743415727236.2%
2026-09-1846017128437.2%
2026-09-1946517628437.8%
2026-09-2044514528732.6%
2026-09-2145715729434.4%
2026-09-2245614530531.8%
2026-09-2346316329535.2%
2026-09-244239632222.7%
2026-09-254239332422.0%
2026-09-264239232621.7%
2026-09-274029530323.6%
2026-09-2839710928427.5%
2026-09-2942410131923.8%
2026-09-304219732023.0%
2026-10-0142210031823.7%
2026-10-024329033420.8%
2026-10-034005733614.2%
2026-10-044005933614.8%
2026-10-054006732816.8%
2026-10-063738528322.8%
2026-10-073767429419.7%
2026-10-083819128323.9%
2026-10-0937617719747.1%
2026-10-1038319119149.9%
2026-10-1137716120542.7%
2026-10-1237015821042.7%
2026-10-1336915221641.2%
2026-10-1437114922140.2%
2026-10-1537011525531.1%
2026-10-1637512225332.5%
2026-10-1737311625631.1%
2026-10-1844716628137.1%
2026-10-1944315928335.9%
2026-10-2043513729831.5%
2026-10-2142112029928.5%
2026-10-2239613126533.1%
2026-10-233819928126.0%
2026-10-2437510726628.5%
2026-10-2537211126129.8%
2026-10-263679527025.9%
2026-10-273648826924.2%
2026-10-2851822628643.6%
2026-10-2951716234931.3%
2026-10-3051917134232.9%
2026-10-3152613538525.7%
2026-11-0151812139023.4%
2026-11-0251212737924.8%
2026-11-0341714427334.5%
2026-11-0441718123243.4%
2026-11-0541215126036.7%
2026-11-0638213524535.3%
2026-11-0737712824634.0%
2026-11-0837713224535.0%
2026-11-0941420420949.3%
2026-11-1039310623727.0%
2026-11-1142212524829.6%
2026-11-1244115927336.1%
2026-11-1345917828138.8%
2026-11-1445816629136.2%
2026-11-1544716128536.0%
2026-11-1644513830731.0%
2026-11-1745414430931.7%
2026-11-1838014323637.6%
Caveat, stated plainly: 102 daily observations is a direction, not a conclusion. A single large deployment would produce the same shape. We publish it because the direction is unambiguous and every point is checkable at console-api.akash.network — not because 4 points establish a trend.

2. Storj: the node count is inflated 4.1x

BucketNodesShare of total
Total (headline figure)124,981100%
Disqualified84,68667.8%
Active30,26324.2%

Quoting 124,981 nodes overstates the working network by 4.1x. Source: stats.storjshare.io.

Two things we will not claim. (a) The buckets are not a partition — active, disqualified, exited, offline and suspended sum to 126,150 against a stated total of 124,981, so they overlap by 1,169. We show only the two ratios that are well-defined against the total. (b) A tempting reading — “the network is accumulating dead nodes faster than live ones” — is not supported by our own data. Over 2026-08-06 to 2026-11-18, disqualified grew +4,451 while active grew -2,674. Active grew faster. We checked because the story was attractive.

3. ThreeFold: 75% of registered CPU is dark

367 nodes reporting up. 1,964 of 7,726 registered cores in use (25.4%). Source: gridproxy.grid.tf. See the utilisation report for the full capacity picture.

Refused — and why

“DefiLlama understates GEODnet revenue by 91%.” REFUSED.
GEODnet's API reports total_usage_revenue = 11,532,723; DefiLlama reports a 30-day revenue of 960,471. The ratio is 12.01x and is stable across all 7 days — which looks compelling and is meaningless as stated: GEODnet renders this field on its own homepage as “Current Annual Recurring Revenue” — an annualised run-rate — while DefiLlama's is a 30-day window. Annualise first and the two agree: 12.01 × 30/365 = 0.99, i.e. near parity. Dividing them as published manufactures a 91% “understatement” that does not exist.

This is the same error class our ontology already refuses for Akash (ACTIVE_LEASES / TOTAL_LEASES: a lifetime denominator yielding a meaningless 0.1%). Publishing it would have been a false public accusation against a third party, derived from a unit error.

Corrected 2026-09-06. This note previously called the field cumulative lifetime revenue and explained its mid-window fall as the series being “token-denominated and revalued daily”. Both readings were wrong: a cumulative total cannot fall, and dividing the value by GEOD spot swings 36% across the archive (42,559,689–57,920,771), so it is not a token quantity either. An annualised run-rate moves in both directions, which is what the archive shows. The refusal above stands; only its stated reason has changed.
“Filecoin revenue per miner rose 26% — oversupply is clearing.” REFUSED.
Active miners did fall (537→529). But the revenue increase behind that claim is a single day of a 24-hour series. Over the same window Filecoin's 30-day revenue fell 64.5% (2026-08-06 to 2026-11-18) — including a 17.6% drop in one day between 2026-08-07 and 2026-08-08, which is an upstream revision rather than anything organic. A per-unit ratio built on a 24h numerator over a 4-day window, when the 30-day series moves the other way, is a story rather than a finding.
Cross-network revenue-per-unit league tables. REFUSED.
A GEODnet weather station is not an Akash datacentre. The spread between them is arithmetically real and economically meaningless. Within-network direction is publishable; the cross-network level is not.

Capacity utilisation · All networks · Pricing · No predictive or performance claim is made anywhere on this site.