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
24h window · 24 hours observed · generated 2026-08-27 20:24:33 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 9 |
| Score | 77.9 | 76.9 | 53.6 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.93% | 23.16% |
| p50 latency | 107.6 ms | 121.2 ms | 15.1 ms |
| p95 latency | 193.3 ms | 212.8 ms | 86.2 ms |
| p99 latency | 235.5 ms | 235.1 ms | 248.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.54 blocks | 0.40 blocks | no cohort |
| Rate limited | 5,999 | 3 | 25 |
| Unsupported | 74 | 0 | 1,115 |
| Samples | 8,695 | 37,860 | 37,947 |
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.1points
- Latency+1.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +1.1, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+24.4points
- Availability+29.7
- Latency−12.5
- Head freshness*+9.4
- Correctness−2.2
The parts add to +24.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.