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 03:08:39 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 91.5 | 78.0 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.96% | 100.00% |
| p50 latency | 19.3 ms | 33.3 ms | 107.5 ms |
| p95 latency | 32.9 ms | 68.0 ms | 192.5 ms |
| p99 latency | 68.0 ms | 174.0 ms | 238.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.54 blocks |
| Rate limited | 0 | 101 | 5,971 |
| Unsupported | 0 | 0 | 70 |
| Samples | 37,516 | 36,885 | 8,766 |
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.9points
- Latency+8.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, 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.