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 · 2.9 days observed · generated 2026-08-27 19:09:13 UTC
| Metric | Tenderly | dRPC | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 8 |
| Score | 96.9 | 92.0 | 78.4 | 62.4 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.96% | 99.94% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 33.9 ms | 107.0 ms | 225.7 ms |
| p95 latency | 49.4 ms | 71.9 ms | 195.7 ms | 4391.3 ms |
| p99 latency | 729.6 ms | 170.5 ms | 242.7 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 661 | 18,327 | 19,619 |
| Unsupported | 0 | 0 | 224 | 0 |
| Samples | 114,220 | 112,337 | 26,473 | 23,880 |
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
+4.9points
- Latency+5.0
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +4.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.5points
- Latency+18.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+34.5points
- Latency+27.5
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +34.5, exactly — the score is a weighted sum, so it comes apart.