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
1h window · 60 minutes observed · generated 2026-08-28 21:12:33 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 88.4 | 69.8 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 19.1 ms | 34.0 ms | 108.7 ms |
| p95 latency | 31.2 ms | 65.5 ms | 207.7 ms |
| p99 latency | 59.3 ms | 212.0 ms | 312.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.31 blocks |
| Rate limited | 0 | 2 | 253 |
| Unsupported | 0 | 0 | 6 |
| Samples | 1,617 | 1,574 | 379 |
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
+11.0points
- Latency+11.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.6points
- Latency+29.8
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +29.6, exactly — the score is a weighted sum, so it comes apart.