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 16:22:34 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 90.8 | 83.9 | 77.9 |
| Status | Excellent | Good | Good |
| Availability | 99.93% | 99.99% | 100.00% |
| p50 latency | 33.8 ms | 105.9 ms | 107.1 ms |
| p95 latency | 71.2 ms | 122.3 ms | 193.1 ms |
| p99 latency | 173.9 ms | 149.3 ms | 235.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.50 blocks |
| Rate limited | 140 | 370 | 5,981 |
| Unsupported | 0 | 0 | 73 |
| Samples | 37,243 | 37,641 | 8,629 |
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.0points
- Latency+6.9
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.9points
- Latency+12.8
- 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.