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 01:22:48 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 91.2 | 83.6 | 77.6 |
| Status | Excellent | Good | Good |
| Availability | 99.87% | 99.94% | 100.00% |
| p50 latency | 33.0 ms | 103.4 ms | 104.4 ms |
| p95 latency | 61.9 ms | 119.3 ms | 196.3 ms |
| p99 latency | 193.3 ms | 145.0 ms | 316.7 ms |
| Correctness | 99.87% | 99.94% | 100.00% |
| Head lag | 0.39 blocks | 0.41 blocks | 0.62 blocks |
| Rate limited | 2 | 21 | 251 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,584 | 1,611 | 371 |
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 dRPC, the highest scorer of those selected.
dRPCvsBlast API
+7.6points
- Latency+7.6
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.6points
- Latency+13.4
- Head freshness+0.3
- Availability−0.1
- Correctness−0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.