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
24h window · 24 hours observed · generated 2026-08-27 17:52:48 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 91.2 | 83.9 | 78.0 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.94% | 99.99% | 100.00% |
| p50 latency | 19.3 ms | 33.8 ms | 106.2 ms | 107.3 ms |
| p95 latency | 34.0 ms | 70.0 ms | 122.8 ms | 193.8 ms |
| p99 latency | 75.6 ms | 171.3 ms | 150.0 ms | 235.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | 0.42 blocks | 0.52 blocks |
| Rate limited | 0 | 136 | 323 | 6,104 |
| Unsupported | 0 | 0 | 0 | 75 |
| Samples | 38,653 | 38,046 | 38,522 | 8,820 |
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.2points
- Latency+8.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.5points
- Latency+15.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.5, 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.