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 15:51:25 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 7 |
| Score | 99.4 | 84.0 | 69.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 19.7 ms | 35.5 ms | 109.5 ms |
| p95 latency | 33.8 ms | 88.7 ms | 209.6 ms |
| p99 latency | 83.3 ms | 176.6 ms | 332.7 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.51 blocks |
| Rate limited | 0 | 36 | 1,513 |
| Unsupported | 0 | 0 | 15 |
| Samples | 9,507 | 9,323 | 2,161 |
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
+15.4points
- Latency+15.5
- Head freshness−0.2
- Correctness−0.0
- Availability+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+30.0points
- Latency+30.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +30.0, exactly — the score is a weighted sum, so it comes apart.