Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
Side by side
24h window · 24 hours observed · generated 2026-08-28 14:47:36 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 89.5 | 77.5 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.98% | 100.00% |
| p50 latency | 18.9 ms | 33.3 ms | 107.4 ms |
| p95 latency | 32.3 ms | 76.4 ms | 196.0 ms |
| p99 latency | 58.1 ms | 192.0 ms | 259.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.37 blocks | 0.54 blocks |
| Rate limited | 0 | 68 | 6,219 |
| Unsupported | 0 | 0 | 76 |
| Samples | 38,577 | 37,935 | 9,056 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against Tenderly, the highest scorer of those selected.
TenderlyvsdRPC
+9.9points
- Latency+10.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +9.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.9points
- Latency+21.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.9, exactly — the score is a weighted sum, so it comes apart.