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
30d window · 4.1 days observed · generated 2026-08-28 22:19:23 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 98.5 | 90.9 | 78.0 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.95% | 99.99% |
| p50 latency | 19.6 ms | 33.9 ms | 107.0 ms |
| p95 latency | 39.8 ms | 72.6 ms | 196.1 ms |
| p99 latency | 544.7 ms | 175.2 ms | 244.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.49 blocks |
| Rate limited | 0 | 765 | 25,444 |
| Unsupported | 0 | 0 | 305 |
| Samples | 158,280 | 155,639 | 36,753 |
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.8
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+20.6points
- Latency+20.6
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.