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 14:56:35 UTC
| Metric | Merkle | Cloudflare |
|---|---|---|
| Rank | 6 | 8 |
| Score | 70.8 | 48.0 |
| Status | Degraded | Poor |
| Availability | 100.00% | 23.18% |
| p50 latency | 108.2 ms | 16.5 ms |
| p95 latency | 191.4 ms | 95.9 ms |
| p99 latency | 231.3 ms | 157.4 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.46 blocks | no cohort |
| Rate limited | 1,498 | 12 |
| Unsupported | 18 | 279 |
| Samples | 2,235 | 9,636 |
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
+22.8points
- Availability+29.7
- Latency−14.1
- Head freshness*+9.4
- Correctness−2.2
The parts add to +22.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.