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 14:44:41 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 7 |
| Score | 85.6 | 78.8 | 69.4 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 37.3 ms | 108.4 ms | 109.2 ms |
| p95 latency | 82.5 ms | 124.8 ms | 226.0 ms |
| p99 latency | 174.7 ms | 139.8 ms | 332.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.44 blocks | 0.53 blocks |
| Rate limited | 7 | 0 | 258 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,578 | 1,606 | 383 |
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
+6.9points
- Latency+6.8
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+16.3points
- Latency+16.1
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +16.3, exactly — the score is a weighted sum, so it comes apart.