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-27 15:38:22 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 88.9 | 78.4 | 70.9 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.96% | 99.99% | 100.00% |
| p50 latency | 20.3 ms | 34.3 ms | 108.5 ms | 110.0 ms |
| p95 latency | 33.9 ms | 71.0 ms | 126.8 ms | 191.4 ms |
| p99 latency | 63.9 ms | 185.3 ms | 152.5 ms | 290.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.41 blocks | 0.45 blocks |
| Rate limited | 0 | 30 | 45 | 1,452 |
| Unsupported | 0 | 0 | 0 | 16 |
| Samples | 9,152 | 8,991 | 9,132 | 2,129 |
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
+10.6points
- Latency+10.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.0points
- Latency+21.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.5points
- Latency+28.5
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +28.5, exactly — the score is a weighted sum, so it comes apart.