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
6h window · 6.0 hours observed · generated 2026-08-28 00:44:08 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 91.9 | 78.0 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 18.2 ms | 32.7 ms | 106.6 ms |
| p95 latency | 31.7 ms | 63.8 ms | 189.8 ms |
| p99 latency | 53.8 ms | 165.4 ms | 278.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.36 blocks | 0.52 blocks |
| Rate limited | 0 | 11 | 1,527 |
| Unsupported | 0 | 0 | 17 |
| Samples | 9,295 | 9,133 | 2,235 |
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
+7.6points
- Latency+7.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.