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 20:22:29 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 70.7 | 69.5 | 46.7 |
| Status | Degraded | Degraded | Poor |
| Availability | 100.00% | 99.97% | 23.11% |
| p50 latency | 110.5 ms | 125.2 ms | 17.7 ms |
| p95 latency | 192.2 ms | 217.1 ms | 102.7 ms |
| p99 latency | 236.0 ms | 238.2 ms | 277.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.60 blocks | 0.40 blocks | no cohort |
| Rate limited | 1,403 | 0 | 0 |
| Unsupported | 18 | 0 | 257 |
| Samples | 2,070 | 8,692 | 8,701 |
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.2points
- Latency+1.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +1.2, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+24.0points
- Availability+29.7
- Latency−12.8
- Head freshness*+9.3
- Correctness−2.2
The parts add to +24.0, 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.