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-26 22:30:24 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 78.0 | 77.2 | 64.1 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.88% | 89.01% |
| p50 latency | 107.0 ms | 119.0 ms | 259.6 ms |
| p95 latency | 196.4 ms | 210.5 ms | 2579.7 ms |
| p99 latency | 241.2 ms | 232.9 ms | 4625.5 ms |
| Correctness | 100.00% | 99.99% | 98.18% |
| Head lag | 0.46 blocks | 0.39 blocks | 0.94 blocks |
| Rate limited | 6,112 | 0 | 6,529 |
| Unsupported | 80 | 0 | 0 |
| Samples | 8,848 | 38,017 | 7,821 |
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
+0.8points
- Latency+0.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+13.9points
- Latency+8.6
- Availability+4.4
- Head freshness+0.6
- Correctness+0.4
The parts add to +13.9, exactly — the score is a weighted sum, so it comes apart.