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-28 14:46:57 UTC
| Metric | Merkle | Cloudflare |
|---|---|---|
| Rank | 7 | 8 |
| Score | 69.3 | 47.7 |
| Status | Degraded | Poor |
| Availability | 100.00% | 23.20% |
| p50 latency | 109.0 ms | 13.9 ms |
| p95 latency | 208.2 ms | 91.5 ms |
| p99 latency | 332.7 ms | 136.5 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.56 blocks | no cohort |
| Rate limited | 1,479 | 6 |
| Unsupported | 14 | 277 |
| Samples | 2,134 | 9,370 |
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
+21.7points
- Availability+29.7
- Latency−15.1
- Head freshness*+9.3
- Correctness−2.2
The parts add to +21.7, 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.