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
30d window · 47 hours observed · generated 2026-08-26 19:11:14 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 78.4 | 77.4 | 64.0 |
| Status | Good | Good | Degraded |
| Availability | 99.97% | 99.87% | 88.84% |
| p50 latency | 106.6 ms | 118.4 ms | 189.3 ms |
| p95 latency | 196.1 ms | 209.2 ms | 2922.0 ms |
| p99 latency | 244.4 ms | 233.3 ms | 6561.8 ms |
| Correctness | 100.00% | 99.98% | 97.72% |
| Head lag | 0.46 blocks | 0.39 blocks | 0.90 blocks |
| Rate limited | 12,211 | 0 | 12,955 |
| Unsupported | 149 | 0 | 0 |
| Samples | 17,581 | 75,252 | 15,886 |
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
+14.3points
- Latency+8.9
- Availability+4.5
- Head freshness+0.5
- Correctness+0.5
The parts add to +14.3, exactly — the score is a weighted sum, so it comes apart.