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
1h window · 60 minutes observed · generated 2026-08-27 12:04:34 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 85.1 | 78.6 | 69.9 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.94% | 100.00% | 100.00% |
| p50 latency | 20.9 ms | 34.6 ms | 108.1 ms | 112.4 ms |
| p95 latency | 33.8 ms | 87.6 ms | 127.2 ms | 209.2 ms |
| p99 latency | 55.3 ms | 190.8 ms | 154.6 ms | 407.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.39 blocks | 0.44 blocks | 0.38 blocks |
| Rate limited | 0 | 5 | 20 | 248 |
| Unsupported | 0 | 0 | 0 | 1 |
| Samples | 1,608 | 1,577 | 1,608 | 349 |
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
+14.3points
- Latency+14.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.5points
- Latency+29.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.