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 20:24:30 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 86.5 | 78.5 | 71.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.94% | 100.00% | 100.00% |
| p50 latency | 17.7 ms | 35.5 ms | 108.7 ms | 108.9 ms |
| p95 latency | 31.3 ms | 81.2 ms | 124.7 ms | 181.6 ms |
| p99 latency | 64.4 ms | 195.8 ms | 152.8 ms | 194.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.52 blocks | 0.34 blocks | 0.43 blocks | 0.68 blocks |
| Rate limited | 0 | 7 | 16 | 275 |
| Unsupported | 0 | 0 | 0 | 2 |
| Samples | 1,595 | 1,576 | 1,606 | 399 |
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
+12.9points
- Latency+13.0
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.8points
- Latency+20.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.0points
- Latency+27.9
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +28.0, exactly — the score is a weighted sum, so it comes apart.