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-27 20:04:56 UTC
| Metric | Merkle | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 70.8 | 46.6 | 0.0 |
| Status | Degraded | Poor | Poor |
| Availability | 100.00% | 23.16% | 0.00% |
| p50 latency | 110.6 ms | 17.7 ms | 0.0 ms |
| p95 latency | 191.8 ms | 103.7 ms | 0.0 ms |
| p99 latency | 236.0 ms | 277.2 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.59 blocks | no cohort | no cohort |
| Rate limited | 1,313 | 0 | 1,416 |
| Unsupported | 18 | 244 | 0 |
| Samples | 1,949 | 8,224 | 1,630 |
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.2points
- Availability+29.7
- Latency−12.6
- Head freshness*+9.3
- Correctness−2.2
The parts add to +24.2, 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.
Merklevs1RPC
+70.8points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.3
- Latency*+1.5
The parts add to +70.8, 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.