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-28 13:38:48 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 7 |
| Score | 79.0 | 78.2 | 69.4 |
| Status | Good | Good | Degraded |
| Availability | 99.97% | 99.97% | 100.00% |
| p50 latency | 34.0 ms | 106.3 ms | 108.6 ms |
| p95 latency | 116.3 ms | 121.8 ms | 205.4 ms |
| p99 latency | 199.3 ms | 134.0 ms | 250.3 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.57 blocks |
| Rate limited | 19 | 175 | 1,451 |
| Unsupported | 0 | 0 | 14 |
| Samples | 9,001 | 9,151 | 2,090 |
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
+0.8points
- Latency+0.8
- Head freshness+0.1
- Correctness+0.0
- Availability+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+9.6points
- Latency+9.4
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +9.6, exactly — the score is a weighted sum, so it comes apart.