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.9 days observed · generated 2026-08-27 17:50:52 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 96.7 | 92.1 | 84.8 | 78.4 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.98% | 99.98% |
| p50 latency | 19.8 ms | 33.9 ms | 105.1 ms | 106.9 ms |
| p95 latency | 50.4 ms | 71.7 ms | 122.6 ms | 195.7 ms |
| p99 latency | 742.0 ms | 169.2 ms | 147.5 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 652 | 1,193 | 18,011 |
| Unsupported | 0 | 0 | 0 | 220 |
| Samples | 112,100 | 110,254 | 111,523 | 25,980 |
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
+4.6points
- Latency+4.8
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +4.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+11.9points
- Latency+12.0
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.3points
- Latency+18.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.3, exactly — the score is a weighted sum, so it comes apart.