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-27 05:24:37 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 99.2 | 91.0 | 77.9 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.92% | 100.00% |
| p50 latency | 19.6 ms | 34.1 ms | 107.2 ms |
| p95 latency | 35.9 ms | 69.9 ms | 195.0 ms |
| p99 latency | 155.3 ms | 172.6 ms | 247.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.48 blocks |
| Rate limited | 0 | 133 | 6,075 |
| Unsupported | 0 | 0 | 76 |
| Samples | 37,892 | 37,314 | 8,687 |
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
+8.3points
- Latency+8.4
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.3points
- Latency+21.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.3, exactly — the score is a weighted sum, so it comes apart.