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-28 00:20:30 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 99.2 | 91.3 | 83.8 | 77.7 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.1 ms | 31.7 ms | 103.3 ms | 107.3 ms |
| p95 latency | 30.8 ms | 61.8 ms | 118.9 ms | 201.7 ms |
| p99 latency | 54.4 ms | 148.1 ms | 147.0 ms | 301.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.39 blocks | 0.41 blocks | 0.37 blocks |
| Rate limited | 0 | 1 | 0 | 256 |
| Unsupported | 0 | 0 | 0 | 5 |
| Samples | 1,617 | 1,568 | 1,606 | 382 |
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
+7.9points
- Latency+8.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.4points
- Latency+15.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.5points
- Latency+21.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.