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 20:23:32 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 77.9 | 76.8 | 57.3 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.93% | 72.66% |
| p50 latency | 107.6 ms | 121.2 ms | 2024.4 ms |
| p95 latency | 193.3 ms | 212.8 ms | 6590.4 ms |
| p99 latency | 235.5 ms | 235.1 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.53 blocks | 0.40 blocks | 0.95 blocks |
| Rate limited | 5,997 | 3 | 6,493 |
| Unsupported | 74 | 0 | 0 |
| Samples | 8,689 | 37,831 | 7,808 |
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 Merkle, the highest scorer of those selected.
MerklevsMEV Blocker
+1.1points
- Latency+1.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +1.1, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+20.7points
- Availability+10.9
- Latency+8.6
- Correctness+0.7
- Head freshness+0.5
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.