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
30d window · 2.6 days observed · generated 2026-08-27 10:07:35 UTC
| Metric | Merkle | Cloudflare |
|---|---|---|
| Rank | 6 | 9 |
| Score | 78.6 | 55.2 |
| Status | Good | Degraded |
| Availability | 99.98% | 23.10% |
| p50 latency | 106.4 ms | 15.0 ms |
| p95 latency | 195.9 ms | 86.7 ms |
| p99 latency | 243.0 ms | 251.8 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.48 blocks | no cohort |
| Rate limited | 16,006 | 96 |
| Unsupported | 198 | 2,928 |
| Samples | 23,038 | 99,401 |
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
+23.4points
- Availability+29.7
- Latency−13.5
- 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.