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 21:12:30 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 89.4 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.98% | 100.00% |
| p50 latency | 18.8 ms | 33.7 ms | 107.3 ms |
| p95 latency | 32.5 ms | 76.6 ms | 200.9 ms |
| p99 latency | 61.0 ms | 188.6 ms | 263.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | 0.50 blocks |
| Rate limited | 0 | 96 | 6,053 |
| Unsupported | 0 | 0 | 73 |
| Samples | 37,644 | 36,986 | 8,735 |
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
+10.0points
- Latency+10.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+22.0points
- Latency+22.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.