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
30d window · 3.6 days observed · generated 2026-08-28 11:21:03 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 91.1 | 84.2 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.98% | 99.99% |
| p50 latency | 33.6 ms | 105.1 ms | 106.8 ms |
| p95 latency | 72.7 ms | 122.1 ms | 195.2 ms |
| p99 latency | 174.6 ms | 147.0 ms | 244.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.49 blocks |
| Rate limited | 703 | 1,545 | 22,587 |
| Unsupported | 0 | 0 | 276 |
| Samples | 138,155 | 139,888 | 32,653 |
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.8points
- Latency+6.8
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.0points
- Latency+12.9
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.