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 09:13:19 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 88.3 | 78.0 | 70.0 |
| Status | Good | Good | Degraded |
| Availability | 99.94% | 99.99% | 100.00% |
| p50 latency | 31.4 ms | 104.8 ms | 105.3 ms |
| p95 latency | 64.1 ms | 120.2 ms | 194.3 ms |
| p99 latency | 158.1 ms | 147.3 ms | 228.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.61 blocks |
| Rate limited | 37 | 113 | 1,330 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,310 | 8,434 | 1,930 |
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
+10.2points
- Latency+10.2
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.3points
- Latency+18.0
- Head freshness+0.3
- Availability−0.0
- Correctness−0.0
The parts add to +18.3, exactly — the score is a weighted sum, so it comes apart.