AlternativesSourced from Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (plus Solana and Polkadot)
Tenderly alternatives
EVM developer platform with a multi-chain public RPC gateway
Tenderly runs a multi-chain public RPC gateway at `gateway.tenderly.co/public/<slug>` alongside its simulation and observability stack. The free, no-key tier covers nine EVM networks and gets pulled into the same dapps that pick PublicNode or dRPC as their default fallback endpoint. The question every developer faces before pasting a URL into a wallet config or a backend service is whether that endpoint is actually fast and reliable on the chain their product runs on, not whether the vendor's homepage says it is. This benchmark probes `eth_blockNumber` every 15 seconds against 15 audited no-key public RPC providers across 10 EVM chains (Ethereum, Arbitrum, Base, Optimism, Avalanche, BNB, Polygon, Linea, Scroll, Mantle), from three Railway regions (us-east, eu-west, sgp). Each provider gets the same identical JSON-RPC POST every cycle, so the recorded p50/p90/p99 reflects sustained round-trip latency rather than a marketing burst. The harness also classifies every response as `ok`, `http_err`, `jsonrpc_err`, `stale` or `timeout` and exposes archive-depth support for five historical depths (300 to 5,000,000 blocks). The cohort competing with Tenderly's gateway includes PublicNode, dRPC, 1RPC, MeowRPC, Nodies, Lava, Merkle, Flashbots Protect and Cloudflare, plus the chain-official foundation endpoints on Base, BNB, Arbitrum, Optimism and Avalanche. The leaderboard re-sorts every 15 seconds against fresh Prometheus samples, and the chain tab at the top of the page filters every query so the comparison stays per chain rather than smeared across an aggregate that mechanically favours single-chain endpoints.
Positioning
Tenderly built its RPC as an extension of a developer-tooling stack rather than as a standalone node fleet. The Node RPC product runs multi-region across EU and US, covers 80+ EVM networks, and exposes standard JSON-RPC and WebSocket. The architectural moat sits above the base RPC surface: the tenderly_ namespace ships simulateTransaction, simulateBundle, estimateGas, estimateGasBundle, traceTransaction, and decoding methods for inputs, errors, events, and ABI signatures. Node Extensions let a team write JavaScript or TypeScript that runs server-side under a custom JSON-RPC method name, so a project can compose a bespoke method (for example, simulate a mempool transaction) without deploying its own infrastructure. This is architecturally distinct from routing layers like dRPC and node fleets like PublicNode, neither of which owns a simulation engine or a scripting sidecar. For the rpc-capabilities axis, that translates into a coverage set biased toward pre-signing and post-mortem workflows: dry-running a transaction against forked state, tracing a decoded call graph, or profiling gas at bundle granularity. The typical use case is dApps whose UX depends on preview-before-sign or on gas quoting; teams migrate away when they need non-EVM chains or read-heavy public traffic that Node Extensions cannot cheaply serve.
About Tenderly: tenderly.co
Top 5 Tenderly alternatives
- Best
- 76 ms
- Median
- 269 ms
- Worst
- 720 ms
- Spread
- 8.0×220 ms → 1.75 s
- Samples · 24h
- 470,85013 providers
RPC latency · last 24 hours
RPC latency · last 24 hours
Region
Show
Product ledger · sorted by p50
| Product | p50 | Trend | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Color | № | 24h | ||||||||
| 01 | 76 ms | |||||||||
| 02 | 154 ms | |||||||||
| 03 | 183 ms | |||||||||
| 04 | 188 ms | |||||||||
| 05 | 249 ms | |||||||||
| 06 | 254 ms | |||||||||
| 07 | 269 ms | |||||||||
| 08 | 272 ms | |||||||||
| 09 | 272 ms | |||||||||
| 10 | 306 ms | |||||||||
| 11 | 334 ms | |||||||||
| 12 | 720 ms | |||||||||
| — | — | — | ||||||||
Same data as /benchmarks/rpc-capabilities, refreshed every minute. OpenChainBench is community-run; methodology is open.