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-29 00:20:20 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 90.7 | 83.5 | 77.5 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 32.3 ms | 103.3 ms | 106.3 ms |
| p95 latency | 63.7 ms | 113.9 ms | 180.9 ms |
| p99 latency | 160.3 ms | 123.4 ms | 230.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.43 blocks | 0.73 blocks |
| Rate limited | 0 | 2 | 273 |
| Unsupported | 0 | 0 | 5 |
| Samples | 1,569 | 1,602 | 382 |
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.2points
- Latency+7.1
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.2points
- Latency+12.8
- Head freshness+0.4
- Availability+0.0
- Correctness+0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.