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 01:52:57 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 77.6 | 76.7 | 58.7 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.97% | 76.33% |
| p50 latency | 105.9 ms | 118.4 ms | 2024.4 ms |
| p95 latency | 193.5 ms | 210.1 ms | 6590.4 ms |
| p99 latency | 220.4 ms | 231.3 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.51 blocks | 0.40 blocks | 0.95 blocks |
| Rate limited | 1,481 | 2 | 1,609 |
| Unsupported | 18 | 0 | 0 |
| Samples | 2,126 | 9,503 | 2,205 |
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.9points
- Latency+1.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +0.9, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+18.9points
- Availability+9.5
- Latency+8.2
- Correctness+0.7
- Head freshness+0.5
The parts add to +18.9, exactly — the score is a weighted sum, so it comes apart.