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 03:07:44 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 99.1 | 91.2 | 77.7 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.98% | 100.00% |
| p50 latency | 18.2 ms | 32.5 ms | 105.9 ms |
| p95 latency | 31.6 ms | 62.6 ms | 193.6 ms |
| p99 latency | 54.4 ms | 163.8 ms | 281.6 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.47 blocks | 0.37 blocks | 0.47 blocks |
| Rate limited | 0 | 7 | 1,337 |
| Unsupported | 0 | 0 | 18 |
| Samples | 8,325 | 8,174 | 1,945 |
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.0points
- Latency+8.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.4
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.