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 21:00:58 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 91.3 | 83.9 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.95% | 99.97% | 100.00% |
| p50 latency | 33.5 ms | 106.4 ms | 107.5 ms |
| p95 latency | 69.4 ms | 123.3 ms | 193.3 ms |
| p99 latency | 173.5 ms | 151.3 ms | 236.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.41 blocks | 0.54 blocks |
| Rate limited | 126 | 319 | 5,919 |
| Unsupported | 0 | 0 | 70 |
| Samples | 36,692 | 37,206 | 8,608 |
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.4points
- Latency+7.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.3points
- Latency+13.1
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.