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 17:33:37 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 89.6 | 78.3 | 70.9 |
| Status | Good | Good | Degraded |
| Availability | 99.95% | 99.99% | 100.00% |
| p50 latency | 34.6 ms | 109.0 ms | 110.5 ms |
| p95 latency | 68.4 ms | 127.4 ms | 191.2 ms |
| p99 latency | 177.3 ms | 154.5 ms | 235.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.41 blocks | 0.53 blocks |
| Rate limited | 23 | 39 | 1,413 |
| Unsupported | 0 | 0 | 19 |
| Samples | 8,856 | 8,989 | 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
+11.3points
- Latency+11.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +11.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.7points
- Latency+18.5
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.