Live RPC provider comparison
Compare public RPC providers on live traffic. Goldsky measures latency, errors, bad data, and block lag every hour from Goldsky Edge requests in 4 AWS regions.
- Pick a view. Choose a chain, a method group or a single method, a region, and a time window.
- Compare providers. Each row is one provider. Lower is better in every column.
- Goldsky Boost is a cache in front of the provider you use now. With Boost on, the table shows Boost’s cache-hit latency and the share of each provider’s calls it answers from cache.
Chain
Method
Region
Window
Boost
RPC providers on Monad: All methods, All regions, last 7d
| Provider | p50 | p90 | Errors | Bad data | Block lag |
|---|---|---|---|---|---|
 QuickNode: Goldsky vs QuickNode | 8.2 ms (best) | 77 ms (best) | 0.29% (best) | 1% | 0.0 (best) |
| eth_call | 10 ms | 76 ms | 0.48% | 1.6% | |
| eth_getBlockByNumber | 4.7 ms | 52 ms | 0.0037% | 0% | |
| eth_getLogs | 9.7 ms | 213 ms | 0% | 0.00083% | |
| debug_traceBlockByNumber | 6.6 ms | 12 ms | 0% | 0% | |
| debug_traceBlockByHash | 17 ms | 208 ms | 0% | 0.0098% | |
| eth_getTransactionReceipt | 17 ms | 81 ms | 0.09% | 0% | |
| debug_traceTransaction | 15 ms | 212 ms | 0% | 2.6% | |
| eth_getTransactionByHash | 4.2 ms | 52 ms | 0.025% | 0% | |
| eth_getBlockReceipts | 4.4 ms | 84 ms | 0% | 0% | |
| eth_getBlockByHash | 2.6 ms | 4.7 ms | 0% | 0% | |
| trace_call | 8.8 ms | 17 ms | 0% | 0% | |
| trace_transaction | 58 ms | 92 ms | 0% | 0% | |
 Alchemy: Goldsky vs Alchemy | 9.4 ms | 96 ms | 3.5% | 0.014% | 0.0 (best) |
| eth_getBlockByNumber | 8.6 ms | 70 ms | 0.0037% | 0% | |
| eth_call | 16 ms | 91 ms | 13% | 0.0024% | |
| eth_getLogs | 6.2 ms | 16 ms | 0% | 0% | |
| eth_getTransactionReceipt | 677 ms | 3044 ms | 9.9% | 0% | |
| eth_getTransactionByHash | 433 ms | 4274 ms | 18% | 0% | |
| debug_traceBlockByNumber | 9.8 ms | 19 ms | 0% | 0% | |
| eth_getBlockReceipts | 19 ms | 729 ms | 0% | 0% | |
| trace_call | 7.9 ms | 14 ms | 0% | 0% | |
 Nirvana Labs | 77 ms | 251 ms | 0.47% | 0.0042% (best) | 0.1 |
| eth_getBlockByNumber | 85 ms | 256 ms | 0.3% | 0.0000072% | |
| eth_call | 63 ms | 194 ms | 0.81% | 0.0027% | |
| eth_getLogs | 55 ms | 111 ms | 0.026% | 0.00067% | |
| debug_traceBlockByHash | 79 ms | 265 ms | 0.0062% | 0.015% | |
| eth_getTransactionReceipt | 84 ms | 281 ms | 0.44% | 0.037% | |
| debug_traceBlockByNumber | 88 ms | 284 ms | 0.025% | 0% | |
| eth_getTransactionByHash | 171 ms | 285 ms | 0.45% | 0.29% | |
| debug_traceTransaction | 61 ms | 97 ms | 0% | 13% | |
| trace_call | 31 ms | 89 ms | 0% | 0% | |
| trace_transaction | 59 ms | 96 ms | 0% | 0% | |
| eth_getBlockReceipts | 178 ms | 894 ms | 0% | 0% | |
| Average | 65 ms | 241 ms | 0.49% | 0.2% | 0.0 |
Measured hourly from Goldsky Edge traffic in 4 AWS regions. Latency counts every attempt. Average pools the requests of the providers shown with figures. Data through .
How to read the table
Columns
- p50
- Median response time. Half of the requests were faster. Every attempt counts.
- p90
- 90th-percentile response time. 9 in 10 requests were faster.
- Errors
- Share of requests that returned an error.
- Bad data
- Share of requests that returned missing data, a wrong empty result, or another wrong response.
- Block lag
- How many blocks the provider’s latest block is behind the chain tip, as the median of the hourly values.
Method groups
- Blocks
eth_getBlockByNumbereth_getBlockByHash- Logs
eth_getLogs- Transactions
eth_getTransactionBy*- Receipts
eth_getTransactionReceipteth_getBlockReceipts- Calls
eth_call- Traces
trace_*debug_trace*arbtrace_*- All
- Every method in the groups above.
Cut your RPC costs with Boost
Put Boost CDN in front of your current provider. Users save about 45% on average. Onboarding benchmarks Boost against your current provider.
Robinhood
HyperEVM
Arc
Solana
Ethereum
Polymarket
Base
Tempo
Bitcoin