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:21:14 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 78.8 | 78.1 | 69.5 |
| Status | Good | Good | Degraded |
| Availability | 99.96% | 99.96% | 100.00% |
| p50 latency | 33.9 ms | 106.2 ms | 108.4 ms |
| p95 latency | 117.3 ms | 121.7 ms | 202.3 ms |
| p99 latency | 199.1 ms | 133.7 ms | 237.7 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.57 blocks |
| Rate limited | 18 | 175 | 1,372 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,532 | 8,681 | 1,983 |
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.7points
- Latency+0.6
- Head freshness+0.1
- Correctness+0.0
- Availability+0.0
The parts add to +0.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+9.3points
- Latency+9.0
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +9.3, exactly — the score is a weighted sum, so it comes apart.