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
7d window · 3.4 days observed · generated 2026-08-28 06:48:32 UTC
| Metric | dRPC | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 91.6 | 78.2 | 77.2 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.99% | 99.90% |
| p50 latency | 33.7 ms | 106.8 ms | 119.6 ms |
| p95 latency | 70.7 ms | 195.0 ms | 211.0 ms |
| p99 latency | 172.0 ms | 245.1 ms | 233.6 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.36 blocks | 0.49 blocks | 0.40 blocks |
| Rate limited | 682 | 21,385 | 3 |
| Unsupported | 0 | 262 | 0 |
| Samples | 130,915 | 30,932 | 132,880 |
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
+13.4points
- Latency+13.3
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.4points
- Latency+14.3
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.