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:43:13 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 77.9 | 76.8 | 58.5 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.96% | 75.73% |
| p50 latency | 107.4 ms | 119.1 ms | 2024.4 ms |
| p95 latency | 193.5 ms | 211.5 ms | 6590.4 ms |
| p99 latency | 230.7 ms | 234.4 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.50 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 1,410 | 1 | 1,563 |
| Unsupported | 16 | 0 | 0 |
| Samples | 2,034 | 9,249 | 2,154 |
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.0points
- Latency+1.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +1.0, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+19.4points
- Availability+9.7
- Latency+8.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +19.4, exactly — the score is a weighted sum, so it comes apart.