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
1h window · 60 minutes observed · generated 2026-08-28 11:41:41 UTC
| Metric | Merkle | Cloudflare |
|---|---|---|
| Rank | 6 | 8 |
| Score | 70.0 | 47.7 |
| Status | Degraded | Poor |
| Availability | 100.00% | 23.24% |
| p50 latency | 107.3 ms | 13.3 ms |
| p95 latency | 194.0 ms | 89.5 ms |
| p99 latency | 1194.0 ms | 141.1 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.58 blocks | no cohort |
| Rate limited | 282 | 0 |
| Unsupported | 2 | 50 |
| Samples | 411 | 1,603 |
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.
MerklevsCloudflare
+22.3points
- Availability+29.7
- Latency−14.4
- Head freshness*+9.3
- Correctness−2.2
The parts add to +22.3, 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.