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 · 3.0 days observed · generated 2026-08-27 21:00:29 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.4 | 62.2 | 54.1 |
| Status | Good | Degraded | Degraded |
| Availability | 99.98% | 84.43% | 23.11% |
| p50 latency | 107.0 ms | 225.7 ms | 15.4 ms |
| p95 latency | 195.1 ms | 4391.3 ms | 89.5 ms |
| p99 latency | 242.0 ms | 7602.5 ms | 253.6 ms |
| Correctness | 100.00% | 97.48% | 100.00% |
| Head lag | 0.49 blocks | 0.91 blocks | no cohort |
| Rate limited | 18,819 | 20,128 | 96 |
| Unsupported | 227 | 0 | 3,448 |
| Samples | 27,196 | 24,471 | 117,039 |
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
+16.2points
- Latency+9.0
- Availability+6.2
- Correctness+0.5
- Head freshness+0.5
The parts add to +16.2, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+24.3points
- Availability+29.7
- Latency−12.7
- Head freshness*+9.4
- Correctness−2.2
The parts add to +24.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.