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
7d window · 41 hours observed · generated 2026-08-26 13:47:40 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 9 |
| Score | 78.4 | 77.6 | 55.9 |
| Status | Good | Good | Degraded |
| Availability | 99.97% | 99.87% | 23.08% |
| p50 latency | 106.3 ms | 118.0 ms | 15.0 ms |
| p95 latency | 196.8 ms | 208.5 ms | 87.5 ms |
| p99 latency | 245.4 ms | 233.1 ms | 256.7 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.46 blocks | 0.40 blocks | no cohort |
| Rate limited | 10,799 | 0 | 41 |
| Unsupported | 133 | 0 | 1,961 |
| Samples | 15,544 | 66,524 | 66,519 |
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.
MerklevsCloudflare
+22.6points
- Availability+29.7
- Latency−14.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +22.6, 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.