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 · 2.4 days observed · generated 2026-08-27 06:54:33 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 9 |
| Score | 78.8 | 77.9 | 55.4 |
| Status | Good | Good | Degraded |
| Availability | 99.98% | 99.89% | 23.11% |
| p50 latency | 106.5 ms | 118.5 ms | 15.0 ms |
| p95 latency | 195.5 ms | 209.2 ms | 87.3 ms |
| p99 latency | 243.2 ms | 232.7 ms | 252.9 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.40 blocks | no cohort |
| Rate limited | 15,157 | 2 | 77 |
| Unsupported | 183 | 0 | 2,774 |
| Samples | 21,793 | 94,202 | 94,183 |
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+0.9
- 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.
MerklevsCloudflare
+23.4points
- Availability+29.7
- Latency−13.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +23.4, 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.