Skip to main content
Infrastructure

Endpoints

A load-balanced reverse proxy for Bittensor RPC, plus the registry of callable Subtensor and subnet endpoints behind it.

LiveLoad-balanced reverse proxyfinney · mainnet

One endpoint for Bittensor RPC

POST JSON-RPC to a single URL and Metagraphed routes it across the healthiest, most in-sync public endpoints — with failover, edge caching, and abuse controls. No key, no account, no single point of failure.

POSThttps://api.metagraph.sh/rpc/v1/finney
Try it
curl -s 'https://api.metagraph.sh/rpc/v1/finney' \
  -X POST -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}'
  • Health-aware load balancing

    Requests fan out across the public endpoint pool, weighted by live probe health and score.

  • Block-height routing

    Nodes trailing the freshest reported tip are demoted behind synced peers, so reads hit current state.

  • Automatic failover

    A dead or transient upstream is retried against the next-best endpoint — transparent to the caller.

  • Edge caching

    Block-pinned reads (chain_getBlockHash/Block/Header) are cached at the edge for instant repeat hits.

  • Read-only + rate-limited

    Only safe read methods pass the allowlist; 100 requests/min per client keeps the pool healthy.

Proxy usage

Updated

Snapshot freshness unknown — verify before relying on this data.

Requests
2
7d
p50
191 ms
p95 389 ms
Success
100.0%
2 ok
Errors
0.0%
0 failed
Failover
0.0%
0 retried
Cache hits
0.0%
0 served
By networkfinney2
Per-endpoint distribution
EndpointProviderRequestsShareErrorsAvg latency
onfinality-finney-rpconfinality2100.0%0.0%290 ms
Endpoints
1402tracked
RPC pools
55 proxy
Archive-capable
8
Healthy
93%82/88 probed

Latency & severity heatmap

Latency heatmap · provider × kind
<150ms<400ms<1sslow/down

RPC pools

PoolRegionMembersArchiveEligibility
finney-rpc5yesProxy
finney-wss4yesProxy
finney-archive8yesProxy
test-rpc2Proxy
test-wss2Proxy

Proxy-eligible members serve live traffic through the reverse proxy above; the proxy prefers in-sync, healthy nodes and fails over automatically.

Callable endpoints

101 of 101
URL
000subtensor-rpcopentensorOK3073ms
000subtensor-rpcopentensorOK2437ms
000subtensor-rpcnodiesUnknown
000subtensor-rpcopentensorOK2823ms
000subtensor-rpconfinalityOK1438ms
000subtensor-wss
wss://bittensor-finney.api.onfinality.io/public-ws
onfinalityOK505ms
000subtensor-wss
wss://archive.chain.opentensor.ai:443
opentensorOK1276ms
000subtensor-wss
wss://lite.chain.opentensor.ai:443
opentensorOK1067ms
000subtensor-wss
wss://entrypoint-finney.opentensor.ai:443
opentensorOK1232ms
001data-artifactmacrocosmosUnknown
002data-artifactinference-labsUnknown
006data-artifactnuminousOK1087ms
007data-artifactallwaysOK871ms
007sseallwaysOK247ms
009data-artifactmacrocosmosUnknown
014data-artifactcacheonOK272ms
015data-artifactoroUnknown
015data-artifactoroUnknown
015data-artifactoroUnknown
017data-artifact404-genUnknown
019data-artifactblockmachineUnknown
019data-artifactblockmachineUnknown
019data-artifactblockmachineUnknown
022data-artifactdesearchUnknown
022data-artifactdesearchUnknown
Page 1 of 5 · showing 25 of 101

Incidents timeline

Incidents · 24h
  • Host-24hnowlinks
  • endpoint-srf-ee8180c137f9a543
    1 ongoing1 total
  • endpoint-srf-5aa367d8193a4a6a
    1 ongoing1 total
  • endpoint-srf-34a4ac83864d4ae7
    1 ongoing1 total
  • endpoint-srf-6acf119341034de8
    1 ongoing1 total
  • endpoint-srf-db88986ea3dcbe82
    1 ongoing1 total