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 11:55:31 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 78.7 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.96% | 100.00% |
| p50 latency | 18.8 ms | 32.8 ms | 107.0 ms |
| p95 latency | 32.8 ms | 116.9 ms | 202.7 ms |
| p99 latency | 60.8 ms | 209.1 ms | 250.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | 0.56 blocks |
| Rate limited | 0 | 21 | 1,576 |
| Unsupported | 0 | 0 | 19 |
| Samples | 9,597 | 9,443 | 2,253 |
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
+20.7points
- Latency+20.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.9points
- Latency+29.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.