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
7d window · 2.6 days observed · generated 2026-08-27 11:57:46 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 95.6 | 92.4 | 78.6 |
| Status | Excellent | Excellent | Good |
| Availability | 99.96% | 99.93% | 99.98% |
| p50 latency | 19.8 ms | 33.8 ms | 106.5 ms |
| p95 latency | 56.3 ms | 72.1 ms | 196.2 ms |
| p99 latency | 796.9 ms | 168.6 ms | 243.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.48 blocks |
| Rate limited | 0 | 629 | 16,495 |
| Unsupported | 0 | 0 | 200 |
| Samples | 102,553 | 100,872 | 23,749 |
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
+3.2points
- Latency+3.4
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +3.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.1points
- Latency+17.1
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.1, exactly — the score is a weighted sum, so it comes apart.