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
7d window · 3.0 days observed · generated 2026-08-27 20:25:46 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 97.1 | 91.9 | 78.4 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.94% | 99.98% |
| p50 latency | 19.8 ms | 33.9 ms | 107.0 ms |
| p95 latency | 48.6 ms | 72.0 ms | 195.2 ms |
| p99 latency | 721.4 ms | 170.7 ms | 241.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.49 blocks |
| Rate limited | 0 | 668 | 18,666 |
| Unsupported | 0 | 0 | 227 |
| Samples | 116,276 | 114,372 | 26,960 |
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
+5.1points
- Latency+5.3
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.7points
- Latency+18.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.