Tenderly RPC Performance with Independent Metrics

RPC Inspector Pro performs automatic network detection and compatibility checks.

Transport formats:
https:// for HTTP endpoints; http:// also works
wss:// for WebSocket endpoints; ws:// also works
grpc:// for gRPC endpoints; grpcs:// or a naked host like example.com:443 also works

Do not submit gRPC endpoints as https://..., even when they use port 443. Instead, for gRPC endpoints use the prefix grpcs:// or just like example.com:443.

Inspector Pro supports:
HTTP/HTTPS JSON-RPC latency: EVM, SVM, Polkadot / Substrate, Cosmos / Tendermint, and UTXO
WebSocket subscriptions: EVM, SVM, Polkadot / Substrate, and Cosmos / Tendermint
gRPC: Sui and SVM Yellowstone / Geyser
Mixed gRPC + WebSocket: SVM block subscriptions

Latency scenarios:
EVM: eth_getBlockByNumber then eth_getLogs(hash)
SVM: getSlot(finalized) then getBlock(slot)
Polkadot / Substrate: chain_getFinalizedHead then chain_getBlock(hash)
Cosmos / Tendermint: /status then /block?height=
UTXO: getblockchaininfo then getblock(hash, 1)

Subscription scenarios:
EVM: newHeads over WebSocket
SVM: blockSubscribe(finalized) or slotSubscribe over WebSocket
SVM: block or slot subscriptions over Yellowstone / Geyser gRPC
Mixed SVM: Yellowstone gRPC in A with WebSocket in B for block subscriptions
Polkadot / Substrate: subscribeFinalizedHeads over WebSocket
Cosmos / Tendermint: NewBlockHeader over WebSocket
Sui: SubscribeCheckpoints over gRPC

For each run, Inspector Pro launches probes in the AWS regions selected by the user. Each endpoint runs in its own dedicated probe Lambda invocation to ensure fair allocation of compute resources. Depending on the auto-selected scenario, probes execute the corresponding RPC, WebSocket, or gRPC workflow, record timings around successful responses, and count failures such as timeouts or rate limits. After collection completes, the results are aggregated into the report page shown in the browser.

Inspector Pro supports public endpoints, API keys in the URL, and most common auth headers such as x-api-key, Authorization, or x-token. Basic auth is not currently supported as a separate mode. Note that we do not store auth header values and we do NOT store the full URL because it might contain an API key. Instead, we record only the URL host: domain and subdomain, if any.

NO. We do not store auth header values, and we do NOT store the full endpoint URL because it might contain an API key. For reporting, we record only the URL host: domain and subdomain, if any. If applicable, you can also rotate the API key after using Inspector Pro.

You can share the dedicated results page URL with anyone. You can also export the underlying data using the “Export” button near the top-right of the results tables.

The IP column contains the IP addresses of the endpoints which were resolved by the lambdas in that region. If you wish, you can look up the values to check which CDNs and data centers are used for that region by the provider of the endpoint.

Inspector Pro API is free. Get in touch with Simon on LinkedIn

Inspector Pro runs distributed probes across AWS regions, using Lambda, Node.js, and DynamoDB to collect and aggregate measurements.

We know it best but we are working to add GCP and Azure.

NO. CompareNodes is an independent company.