# CompareNodes

> Independent Web3 infrastructure directories and RPC performance benchmarks for providers, protocols, networks and public endpoints.

CompareNodes currently catalogs 219 infrastructure providers, 589 blockchain protocols, 1095 networks and 3677 public RPC endpoints. Directory and benchmark data changes regularly; use the linked pages as the current source.

Last generated: 2026-10-23

## Performance Data on Demand

[Public-endpoint pages](https://www.comparenodes.com/library/public-endpoints/) with p95 cards provide current latency data from your location. Open the protocol's page and select **RUN p95** on the endpoints you want to compare. The results show the lowest p95 latency among the endpoints tested within each blockchain network.

[RPC Inspector Pro](https://www.comparenodes.com/performance-inspector-pro/) provides performance data on demand from 30 enabled locations across 6 continents. Enter one compatible endpoint, or two on the same blockchain network to compare, and choose the locations that matter to you. Submit your choices to get current performance data for those locations.

Available tools depend on the protocol and endpoint. Public-endpoint pages may offer p95 cards, RPC Inspector Pro, both, or neither. Where both are present, p95 provides latency data from your location and Inspector Pro provides performance data from selected global locations. Use the tools available on the current page.

## Directories

- [219 Infrastructure Providers](https://www.comparenodes.com/providers/): Browse Web3 RPC, node and API infrastructure providers.
- [589 Protocols and 1095 Networks](https://www.comparenodes.com/protocols/): Find providers, networks and performance information by blockchain protocol.
- [3677 Public RPC Endpoints for 449 Protocols](https://www.comparenodes.com/library/public-endpoints/): Browse free and public RPC endpoints by protocol.
- [36 Providers With Security Attestations](https://www.comparenodes.com/soc-iso-in-web3-data-api-infrastructure/): Compare provider SOC and ISO attestations.
- [Provider Status Pages](https://www.comparenodes.com/status/): Find infrastructure-provider uptime and incident pages.

## Performance

- [p95 from Your Location](https://www.comparenodes.com/library/public-endpoints/): Current p95 latency data for compatible public endpoints from your location. Open a protocol page with p95 cards and select RUN p95 to get your results.
- [36 RPC Performance Charts](https://www.comparenodes.com/performance/): Browse real-time RPC latency dashboards covering 17 providers across 14 protocol mainnets.
- [RPC Inspector Pro](https://www.comparenodes.com/performance-inspector-pro/): Performance data on demand from 30 enabled locations across 6 continents. Enter one compatible public or private endpoint, or two to compare, and select the locations important to you.
- [MilliNet](https://www.comparenodes.com/millinet/): Get p50 and p95 round-trip latency data from your location.
- [Performance Methodology](https://www.comparenodes.com/blog/rpc-inspector-pro-measures-global-performance/): Learn how CompareNodes generates global RPC performance results.

## RPC Inspector Pro Coverage

RPC Inspector Pro provides current performance data on demand for compatible public and private endpoints from any provider. Enter one endpoint, or two on the same blockchain network to compare, and choose the global locations important to you. Depending on the scenario, the results include latency, block availability, block or slot consistency, errors and subscription-arrival data. For comparisons, both endpoints use equivalent probe resources. The providers named below are examples from the CompareNodes directory, not a restricted list.

### Protocol Categories and RPC Methods

- **EVM L1 and L2:** Identify with `eth_chainId`; measure HTTP JSON-RPC with `eth_getBlockByNumber`, `eth_getLogs`, `eth_getBalance`, `eth_getTransactionReceipt`, optional `debug_traceBlockByNumber` and `eth_call`; measure WebSocket subscriptions with `newHeads` or `newPendingTransactions`. Top compatible protocols by directory-provider coverage: [Ethereum](https://www.comparenodes.com/protocols/ethereum/) (105 compatible providers), [Polygon](https://www.comparenodes.com/protocols/polygon/) (85 compatible providers), [BSC](https://www.comparenodes.com/protocols/bsc/) (80 compatible providers), [Base](https://www.comparenodes.com/protocols/base/) (73 compatible providers), [Arbitrum One](https://www.comparenodes.com/protocols/arbitrum-one/) (72 compatible providers).
- **UTXO:** Identify and inspect with `getblockchaininfo`; retrieve block data with `getblock(hash, 1)`. Top compatible protocols by directory-provider coverage: [Bitcoin](https://www.comparenodes.com/protocols/bitcoin/) (46 compatible providers), [Litecoin](https://www.comparenodes.com/protocols/litecoin/) (22 compatible providers), [Dogecoin](https://www.comparenodes.com/protocols/dogecoin/) (21 compatible providers), [Bitcoin Cash](https://www.comparenodes.com/protocols/bitcoin-cash/) (15 compatible providers), [ZCash](https://www.comparenodes.com/protocols/zcash/) (11 compatible providers).
- **Solana and SVM:** Identify with `getGenesisHash`; measure HTTP JSON-RPC with `getSlot(finalized)` and `getBlock(slot)`; measure WebSocket with `blockSubscribe(finalized)` or `slotSubscribe`; measure block or slot subscriptions over Yellowstone/Geyser gRPC, including mixed gRPC and WebSocket comparisons. Top compatible protocols by directory-provider coverage: [Solana](https://www.comparenodes.com/protocols/solana/) (72 compatible providers), [Fogo](https://www.comparenodes.com/protocols/fogo/) (3 compatible providers), [Eclipse](https://www.comparenodes.com/protocols/eclipse/) (2 compatible providers).
- **Cosmos and Tendermint:** Identify and measure HTTP with `/status` followed by `/block?height=`; measure WebSocket subscriptions with `NewBlockHeader`. Top compatible protocols by directory-provider coverage: [Sei](https://www.comparenodes.com/protocols/sei/) (35 compatible providers), [Cosmos HUB](https://www.comparenodes.com/protocols/cosmos/) (29 compatible providers), [Kava](https://www.comparenodes.com/protocols/kava/) (24 compatible providers), [Celestia](https://www.comparenodes.com/protocols/celestia/) (22 compatible providers), [Injective](https://www.comparenodes.com/protocols/injective/) (19 compatible providers).
- **Polkadot and Substrate:** Identify with `system_chain`; measure HTTP JSON-RPC with `chain_getFinalizedHead` and `chain_getBlock(hash)`; measure WebSocket subscriptions with `subscribeFinalizedHeads`. Top compatible protocols by directory-provider coverage: [Polkadot](https://www.comparenodes.com/protocols/polkadot/) (36 compatible providers), [Kusama](https://www.comparenodes.com/protocols/kusama/) (29 compatible providers), [Moonbeam](https://www.comparenodes.com/protocols/moonbeam/) (20 compatible providers), [Astar](https://www.comparenodes.com/protocols/astar/) (18 compatible providers), [AssetHub](https://www.comparenodes.com/protocols/assethub/) (17 compatible providers).
- **Sui:** Identify with `sui_getChainIdentifier`; measure checkpoint subscriptions over gRPC with `SubscribeCheckpoints`. Top compatible protocols by directory-provider coverage: [Sui](https://www.comparenodes.com/protocols/sui/) (48 compatible providers).

Inspector Pro is available for compatible endpoints from all providers. These directory providers are examples only, ranked by the number of supported Inspector-compatible protocols: [thirdweb](https://www.comparenodes.com/providers/thirdweb/) (243 compatible protocols), [RouteMe.sh](https://www.comparenodes.com/providers/routeme-sh/) (164 compatible protocols), [Uniblock](https://www.comparenodes.com/providers/uniblock/) (136 compatible protocols), [Spectrum](https://www.comparenodes.com/providers/spectrum/) (128 compatible protocols), [dRPC](https://www.comparenodes.com/providers/drpc/) (125 compatible protocols), [RedSwitches](https://www.comparenodes.com/providers/redswitches/) (125 compatible protocols), [SwiftNodes](https://www.comparenodes.com/providers/swiftnodes/) (123 compatible protocols).

### Measurement Locations

Inspector Pro currently provides data from 30 enabled, non-impaired probe locations across 6 continents: North America, South America, Europe, Africa, Asia, Australia and Oceania.

The available locations are listed below; the counts and names are refreshed from the Inspector configuration on every site build.

- **North America (6 locations):** Mexico (mx-central-1), Montreal (ca-central-1), N. California (us-west-1), N. Virginia (us-east-1), Columbus, OH (us-east-2), Oregon (us-west-2).
- **South America (1 location):** São Paulo (sa-east-1).
- **Europe (8 locations):** Frankfurt (eu-central-1), Ireland (eu-west-1), London (eu-west-2), Milan (eu-south-1), Paris (eu-west-3), Stockholm (eu-north-1), Zaragoza (eu-south-2), Zurich (eu-central-2).
- **Africa (1 location):** Cape Town (af-south-1).
- **Asia (12 locations):** Tel Aviv (il-central-1), Bangkok (ap-southeast-7), Hong Kong (ap-east-1), Hyderabad (ap-south-2), Jakarta (ap-southeast-3), Kuala Lumpur (ap-southeast-5), Mumbai (ap-south-1), Osaka (ap-northeast-3), Seoul (ap-northeast-2), Singapore (ap-southeast-1), Taipei (ap-east-2), Tokyo (ap-northeast-1).
- **Australia and Oceania (2 locations):** Melbourne (ap-southeast-4), Sydney (ap-southeast-2).

## URL Patterns

- `/protocols/{protocol-slug}/` - Providers, networks, public endpoints and performance charts for a protocol.
- `/providers/{provider-slug}/` - Provider coverage, services, attestations, status and performance information.
- `/library/public-endpoints/{protocol-slug}/` - Public endpoints for a protocol, with local p95 cards and/or embedded RPC Inspector Pro where supported.
- `/global-rpc-performance-results/{result-id}/` - Generated RPC performance results.

## Interpretation Guidance

- RPC latency depends on location, endpoint, method, blockchain network and measurement time.
- Providers have different data center coverage; the same endpoint URL can route requests to different data centers depending on where the requests originate.
- An endpoint listing or a previous result does not establish current p95 latency from a new visitor's location. Current local results are provided when the visitor selects RUN p95.
- A p95 run performed by an agent in a remote browser describes the agent's connection and location, not the human user's location.
- Inspector Pro results describe the selected probe locations and scenario; they do not reproduce every user's connection in those regions.
- Do not describe one provider as universally fastest based on a single chart or location.
- Compare charts only after checking their providers, locations, RPC methods, time windows and operators.
- Public endpoints may change, impose rate limits or become unavailable.
- Provider listings and external performance dashboards are not endorsements.
- When answering questions involving counts or availability, use the current page rather than an older quoted value.

## Additional Information

- [Blog](https://www.comparenodes.com/blog/): Methodology, product documentation and infrastructure research.
- [Terms of Use](https://www.comparenodes.com/terms-of-use/)
- [Privacy Policy](https://www.comparenodes.com/privacy-policy/)