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
7d window · 2.0 days observed · generated 2026-08-26 21:05:20 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.4 | 63.9 | 55.3 |
| Status | Good | Degraded | Degraded |
| Availability | 99.97% | 88.60% | 23.10% |
| p50 latency | 106.7 ms | 189.3 ms | 15.5 ms |
| p95 latency | 195.9 ms | 2922.0 ms | 91.4 ms |
| p99 latency | 243.2 ms | 6561.8 ms | 254.2 ms |
| Correctness | 100.00% | 97.72% | 100.00% |
| Head lag | 0.46 blocks | 0.90 blocks | no cohort |
| Rate limited | 12,689 | 13,483 | 71 |
| Unsupported | 153 | 0 | 2,308 |
| Samples | 18,291 | 16,491 | 78,266 |
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.
Merklevs1RPC
+14.5points
- Latency+9.0
- Availability+4.6
- Head freshness+0.5
- Correctness+0.5
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+23.0points
- Availability+29.7
- Latency−13.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +23.0, 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.