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 10:51:56 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 9 |
| Score | 70.1 | 69.5 | 0.0 |
| Status | Degraded | Degraded | Poor |
| Availability | 100.00% | 99.94% | 0.00% |
| p50 latency | 106.3 ms | 120.5 ms | 0.0 ms |
| p95 latency | 196.0 ms | 209.6 ms | 0.0 ms |
| p99 latency | 228.8 ms | 228.2 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.57 blocks | 0.41 blocks | no cohort |
| Rate limited | 1,502 | 1 | 1,638 |
| Unsupported | 19 | 0 | 0 |
| Samples | 2,220 | 9,482 | 1,876 |
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.6points
- Latency+0.8
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +0.6, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+70.1points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.3
- Latency*+0.8
The parts add to +70.1, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.