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-26 22:17:03 UTC
| Metric | Merkle | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 7 | 8 | 9 |
| Score | 69.4 | 52.0 | 0.0 |
| Status | Degraded | Degraded | Poor |
| Availability | 100.00% | 22.90% | 0.00% |
| p50 latency | 110.0 ms | 13.5 ms | 0.0 ms |
| p95 latency | 220.4 ms | 72.4 ms | 0.0 ms |
| p99 latency | 1113.0 ms | 282.8 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.50 blocks | no cohort | no cohort |
| Rate limited | 251 | 0 | 272 |
| Unsupported | 2 | 46 | 0 |
| Samples | 339 | 1,593 | 311 |
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
+17.4points
- Availability+29.8
- Latency−19.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +17.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.
Merklevs1RPC
+69.4points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.4
- Latency*+0.0
The parts add to +69.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.