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:20:47 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 86.5 | 78.5 | 71.4 |
| Status | Good | Good | Degraded |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 35.6 ms | 108.8 ms | 108.7 ms |
| p95 latency | 81.0 ms | 125.2 ms | 181.6 ms |
| p99 latency | 195.8 ms | 152.8 ms | 194.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.41 blocks | 0.65 blocks |
| Rate limited | 7 | 16 | 278 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,586 | 1,614 | 403 |
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
+8.0points
- Latency+8.0
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+15.1points
- Latency+14.8
- Head freshness+0.4
- Availability−0.0
- Correctness+0.0
The parts add to +15.1, exactly — the score is a weighted sum, so it comes apart.