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 00:44:12 UTC
| Metric | dRPC | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 90.5 | 77.9 | 76.8 |
| Status | Excellent | Good | Good |
| Availability | 99.87% | 100.00% | 99.96% |
| p50 latency | 34.7 ms | 107.4 ms | 119.1 ms |
| p95 latency | 72.5 ms | 193.5 ms | 211.5 ms |
| p99 latency | 179.5 ms | 230.7 ms | 234.4 ms |
| Correctness | 99.98% | 100.00% | 100.00% |
| Head lag | 0.39 blocks | 0.50 blocks | 0.41 blocks |
| Rate limited | 30 | 1,417 | 1 |
| Unsupported | 0 | 16 | 0 |
| Samples | 9,123 | 2,043 | 9,271 |
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.7points
- Latency+12.6
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +12.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+13.7points
- Latency+13.7
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.