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
6h window · 6.0 hours observed · generated 2026-08-27 13:17:26 UTC
| Metric | Merkle | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 70.3 | 49.1 | 0.0 |
| Status | Degraded | Poor | Poor |
| Availability | 100.00% | 23.19% | 0.00% |
| p50 latency | 107.9 ms | 15.8 ms | 0.0 ms |
| p95 latency | 198.4 ms | 89.8 ms | 0.0 ms |
| p99 latency | 231.3 ms | 130.5 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.48 blocks | no cohort | no cohort |
| Rate limited | 1,361 | 19 | 1,475 |
| Unsupported | 17 | 249 | 0 |
| Samples | 2,022 | 8,579 | 1,691 |
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
+21.1points
- Availability+29.7
- Latency−15.8
- Head freshness*+9.4
- Correctness−2.2
The parts add to +21.1, 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.3points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.4
- Latency*+0.8
The parts add to +70.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.