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-28 00:41:27 UTC
| Metric | dRPC | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 91.4 | 78.0 | 76.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 100.00% | 99.93% |
| p50 latency | 33.1 ms | 107.4 ms | 122.0 ms |
| p95 latency | 68.7 ms | 193.1 ms | 213.7 ms |
| p99 latency | 172.8 ms | 256.1 ms | 235.0 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.36 blocks | 0.52 blocks | 0.40 blocks |
| Rate limited | 116 | 6,126 | 1 |
| Unsupported | 0 | 75 | 0 |
| Samples | 37,757 | 8,939 | 38,303 |
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.2
- 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.6points
- Latency+14.5
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.