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-27 20:23:55 UTC
| Metric | Merkle | Cloudflare |
|---|---|---|
| Rank | 6 | 8 |
| Score | 71.3 | 47.2 |
| Status | Degraded | Poor |
| Availability | 100.00% | 23.01% |
| p50 latency | 108.9 ms | 17.9 ms |
| p95 latency | 181.6 ms | 99.0 ms |
| p99 latency | 194.9 ms | 277.2 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.65 blocks | no cohort |
| Rate limited | 278 | 0 |
| Unsupported | 2 | 47 |
| Samples | 400 | 1,614 |
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
+24.1points
- Availability+29.8
- Latency−12.6
- Head freshness*+9.2
- Correctness−2.2
The parts add to +24.1, 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.