All 128 Bittensor subnets — live API health · Metagraphed

Bittensor ecosystemτ—curated—

128 active of 129Healthy 514/618Total stake

Data may be stale

129 subnets

#000 · Τ · 1,228 days old

#001 · α · 1,020 days old

#002 · β · 848 days old

#003 · γ · 649 days old

#004 · δ · 1,032 days old

#005 · ε · 882 days old

#006 · ζ · 780 days old

#007 · η · 863 days old

#008 · θ · 1,022 days old

#009 · ι · 1,021 days old

#010 · Ⱂ · 829 days old

#011 · λ · 822 days old

#012 · μ · 914 days old

#013 · ν · 963 days old

#014 · ㄷ · 554 days old

#015 · ο · 204 days old

#016 · π · 53 days old

#017 · ρ · 833 days old

#018 · σ · 1,005 days old

#019 · t · 956 days old

#020 · υ · 954 days old

#021 · φ · 789 days old

#022 · χ · 949 days old

#023 · ψ · 941 days old

#024 · ω · 875 days old

#025 · א · 811 days old

#026 · ב · 99 days old

#027 · ג · 988 days old

#028 · ד · 550 days old

#029 · ה · 758 days old

30 of 129

						7d %		Health

Domains

Registration churn

All 129 subnets

Looking for the ones you can integrate with? Subnets publishing a machine-readable API spec.

What a subnet is

A subnet is a self-contained incentive mechanism running on the Bittensor chain. Miners produce work, validators score it, and emission is distributed by the resulting consensus. The netuid identifies the slot, not the project: slots are competitive, so the team occupying netuid 38 today may not be the one occupying it next quarter. That is why every record here is dated.

How the health figures are produced

Every registered surface is probed on a 15-minute cycle and the outcome is recorded as-is. Uptime, latency and incident history are derived from those probes alone — no operator can set them, and neither can we. A subnet with no public interface is shown as having none rather than being quietly omitted.