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
24h window · 24 hours observed · generated 2026-08-27 13:20:40 UTC
| Metric | dRPC | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 90.5 | 77.8 | 76.8 |
| Status | Excellent | Good | Good |
| Availability | 99.92% | 100.00% | 99.92% |
| p50 latency | 34.1 ms | 107.0 ms | 120.6 ms |
| p95 latency | 72.4 ms | 193.9 ms | 211.3 ms |
| p99 latency | 172.2 ms | 235.0 ms | 232.5 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.50 blocks | 0.40 blocks |
| Rate limited | 156 | 5,984 | 3 |
| Unsupported | 0 | 71 | 0 |
| Samples | 37,195 | 8,638 | 37,745 |
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.
dRPCvsMerkle
+12.6points
- Latency+12.5
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+13.6points
- Latency+13.6
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.