Skip to main content

Providers

The teams and operators behind these public interfaces.

Providers
138
Official or claimed
92 (67%)
Endpoints
3,414

Updated · registry ·

Directory. Every provider, and whether their sources still resolve.

Providers (138)

ProviderKindAuthoritySubnetsEndpointsSourcesSurfaces
404-GENsubnet-teamcommunity18—8
Academiasubnet-teamofficial13—3
Actual Computersubnet-teamprovider-claimed17—7
AdTAOsubnet-teamofficial116—16
Affinesubnet-teamcommunity115—15
Albedosubnet-teamcommunity17—7
Allwayssubnet-teamprovider-claimed146—46
Almanacsubnet-teamcommunity16—6
AlphaCoresubnet-teamofficial12—2
Alveus Labssubnet-teamcommunity142—42
Astridsubnet-teamcommunity17—7
Aureliussubnet-teamcommunity164—64
Babelbitsubnet-teamcommunity120—20
Backprop Financedata-providerprovider-claimed129129—129
Basilicasubnet-teamcommunity11—1
Beamsubnet-teamcommunity138—38
BitAdssubnet-teamofficial14—4
Bitcast · bitcastsubnet-teamcommunity1121—121
Bitcast · bitcast-networksubnet-teamcommunity118—18
BitMindsubnet-teamofficial117—17
Bitrecssubnet-teamofficial16—6
Bitsec.aisubnet-teamcommunity136—36
Bitstartersubnet-teamofficial15—5
BlockMachineinfrastructure-providerprovider-claimed132—32
ByteLeapsubnet-teamcommunity14—4
Byzantiumsubnet-teamofficial18—8
Cacheonsubnet-teamofficial120—20
ChipForgesubnet-teamofficial14—4
Chutessubnet-teamofficial171—71
CliqueAIsubnet-teamcommunity16—6
Coldintsubnet-teamofficial19—9
Compellesubnet-teamofficial15—5
Compute Hordesubnet-teamofficial19—9
Connitosubnet-teamofficial19—9
DegenBrainsubnet-teamprovider-claimed116—16
Desearchsubnet-teamofficial150—50
Dittosubnet-teamofficial126—26
Djinnsubnet-teamofficial119—19
dogelayersubnet-teamcommunity16—6
Dwellirinfrastructure-providerprovider-claimed00—0
8 Ballsubnet-teamofficial17—7
Eirelsubnet-teamcommunity00—0
Enduresubnet-teamofficial13—3
Tag101subnet-teamcommunity13—3
EvolAIsubnet-teamofficial17—7
FlameWireinfrastructure-providerprovider-claimed00—0
ForeverMoneysubnet-teamofficial17—7
GetBlockinfrastructure-providerprovider-claimed00—0
Gittensorsubnet-teamprovider-claimed148—48
Gittensorydata-providerprovider-claimed15—5
Glyph Researchsubnet-teamofficial12—2
gmsubnet-teamcommunity116—16
Gopher AIsubnet-teamofficial18—8
Gradientssubnet-teamprovider-claimed164—64
Graphite AIsubnet-teamofficial135—35
Green Computesubnet-teamofficial1104—104
GroundLayersubnet-teamofficial16—6
Handshake58subnet-teamofficial110—10
Hanlin AIsubnet-teamprovider-claimed110—10
Harnyxsubnet-teamcommunity15—5
HashiChainsubnet-teamofficial13—3
Heraldsubnet-teamcommunity142—42
Hippiussubnet-teamofficial144—44
Honesubnet-teamofficial110—10
Inference Labssubnet-teamofficial121—21
InfiniteHashsubnet-teamofficial16—6
ItsAIsubnet-teamofficial18—8
Leadpoetsubnet-teamcommunity110—10
Leomasubnet-teamcommunity135—35
Liquiditysubnet-teamcommunity110—10
lium.iosubnet-teamofficial1157—157
Luminar Networksubnet-teamofficial19—9
Macrocosmossubnet-teamofficial499—99
MANTISsubnet-teamofficial113—13
Metagraphedregistryregistry-observed00—0
Minossubnet-teamcommunity116—16
minotaursubnet-teamcommunity111—11
Mobius Fundsubnet-teamofficial19—9
NATIXsubnet-teamofficial110—10
Nepher Roboticssubnet-teamofficial1146—146
NexisGensubnet-teamcommunity15—5
NIOMEsubnet-teamcommunity15—5
Nodexosubnet-teamprovider-claimed215—15
Nodiesinfrastructure-providerprovider-claimed11—1
NOVAsubnet-teamcommunity115—15
Numinoussubnet-teamofficial123—23
One Covenantsubnet-teamprovider-claimed335—35
oneoneonesubnet-teamofficial18—8
OnFinalityinfrastructure-providerprovider-claimed12—2
OpenTensorinfrastructure-providerofficial318—18
OROsubnet-teamofficial187—87
OxMarketssubnet-teamcommunity165—65
Perturbsubnet-teamcommunity15—5
Platform Networksubnet-teamofficial134—34
Poker44subnet-teamcommunity110—10
qBittensor Labssubnet-teamofficial29—9
RalphLabsAIsubnet-teamofficial110—10
ReadyAIsubnet-teamofficial117—17
RedTeamsubnet-teamofficial17—7
Ridgessubnet-teamofficial145—45
Scoresubnet-teamcommunity119—19
Shiftlayersubnet-teamprovider-claimed00—0
SignalPlussubnet-teamprovider-claimed00—0
SILX Labssubnet-teamofficial18—8
SOMAsubnet-teamofficial155—55
Sparketsubnet-teamofficial15—5
SubnetRadardata-providerprovider-claimed128128—128
Sundae Barsubnet-teamofficial114—14
Swarmsubnet-teamcommunity118—18
Synthsubnet-teamcommunity136—36
AlphaRidge.aisubnet-teamofficial146—46
TalkHeadsubnet-teamcommunity17—7
ChronoLLMsubnet-teamofficial120—20
TAO Private Networksubnet-teamcommunity00—0
TaoFisubnet-teamofficial17—7
Taofu Labssubnet-teamcommunity120—20
TaoLendsubnet-teamprovider-claimed13—3
TaoMarketCapdata-providerprovider-claimed114149—149
Taopedia Articlesdocs-providercommunity128128—128
TAOS IMsubnet-teamofficial18—8
Taostatsdata-providerprovider-claimed11—1
Targonsubnet-teamofficial111—11
Tensorclawsubnet-teamprovider-claimed19—9
Tensorplexsubnet-teamofficial18—8
Tensorplex subnet-docsdocs-providercommunity129134—134
TensorUSDsubnet-teamofficial110—10
Thirty Spokessubnet-teamcommunity13—3
TrajectoryRLsubnet-teamofficial110—10
Trishoolsubnet-teamofficial18—8
Unarbossubnet-teamofficial18—8
Vanta Networksubnet-teamofficial110—10
VectorChatsubnet-teamprovider-claimed00—0
Verathossubnet-teamofficial165—65
Vidaiosubnet-teamofficial114—14
Vocencesubnet-teamcommunity153—53
Yanez Compliancesubnet-teamcommunity111—11
Zeussubnet-teamcommunity113—13
Zipcodesubnet-teamcommunity148—48

138 matching of 138 loaded providers · verifying sources · registry

Leaders. Who serves the most endpoints.

  1. 01lium.iosubnet-team157
  2. 02TaoMarketCapdata-provider149
  3. 03Nepher Roboticssubnet-team146

Why providers are tracked separately

One operator often runs surfaces for several subnets, and one subnet often depends on several operators. Modelling them separately is what makes it possible to see that an outage spans four subnets because they share a host, rather than reading it as four unrelated incidents.

Attribution rules

A provider is attached to a surface only where the operator declares it or a first-party source shows it. Where ownership is unclear the surface stays unattributed rather than being assigned on a guess, because a wrong attribution is a claim about somebody's business.

Reading an uptime figure

Uptime here is the share of our probes that got a usable answer over the window, not an operator's SLA. A provider running one endpoint that has never failed and a provider running forty with one flapping host can show similar percentages, so the endpoint count beside it is part of the reading.

Raw identifiers & sources
providers
https://api.metagraph.sh/api/v1/providers
source-health
https://api.metagraph.sh/api/v1/source-health