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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 22:35:51 UTC
| Metric | Merkle | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 73.3 | 49.7 | 0.0 |
| Status | Degraded | Poor | Poor |
| Availability | 100.00% | 22.80% | 0.00% |
| p50 latency | 105.1 ms | 12.5 ms | 0.0 ms |
| p95 latency | 147.7 ms | 74.5 ms | 0.0 ms |
| p99 latency | 231.6 ms | 231.5 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.53 blocks | no cohort | no cohort |
| Rate limited | 274 | 0 | 278 |
| Unsupported | 3 | 46 | 0 |
| Samples | 388 | 1,608 | 317 |
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.7points
- Availability+29.9
- Latency−13.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +23.7, 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
+73.3points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.4
- Latency*+4.0
The parts add to +73.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.