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
6h window · 6.0 hours observed · generated 2026-08-27 04:12:40 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 90.5 | 84.1 | 77.7 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.99% | 100.00% |
| p50 latency | 32.7 ms | 103.0 ms | 104.4 ms |
| p95 latency | 68.2 ms | 115.4 ms | 193.2 ms |
| p99 latency | 164.9 ms | 139.1 ms | 251.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.42 blocks | 0.45 blocks |
| Rate limited | 30 | 76 | 1,316 |
| Unsupported | 0 | 0 | 19 |
| Samples | 8,313 | 8,387 | 1,861 |
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.5points
- Latency+6.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.8points
- Latency+12.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.