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 · 3.2 days observed · generated 2026-08-28 00:43:41 UTC
| Metric | Tenderly | dRPC | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 8 |
| Score | 97.5 | 91.8 | 78.3 | 61.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.97% | 99.94% | 99.98% | 83.57% |
| p50 latency | 19.7 ms | 33.8 ms | 106.9 ms | 265.3 ms |
| p95 latency | 46.1 ms | 71.2 ms | 195.0 ms | 4975.4 ms |
| p99 latency | 684.1 ms | 170.5 ms | 243.6 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.38% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 671 | 19,811 | 21,137 |
| Unsupported | 0 | 0 | 240 | 0 |
| Samples | 123,256 | 121,221 | 28,640 | 25,979 |
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
+5.6points
- Latency+5.8
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+19.2points
- Latency+19.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +19.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+35.6points
- Latency+28.1
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +35.6, exactly — the score is a weighted sum, so it comes apart.