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
- PublicNode
- Tenderly
- NodeReal
- Blast API
- dRPC
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 10:16:03 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 69.7 | 69.5 | 49.5 |
| Status | Degraded | Degraded | Poor |
| Availability | 100.00% | 99.96% | 23.12% |
| p50 latency | 106.0 ms | 120.7 ms | 12.5 ms |
| p95 latency | 200.6 ms | 207.0 ms | 79.3 ms |
| p99 latency | 250.3 ms | 223.0 ms | 132.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.55 blocks | 0.40 blocks | no cohort |
| Rate limited | 1,393 | 0 | 6 |
| Unsupported | 19 | 0 | 247 |
| Samples | 2,000 | 8,518 | 8,533 |
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.
MerklevsMEV Blocker
+0.2points
- Latency+0.3
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+20.1points
- Availability+29.7
- Latency−16.7
- Head freshness*+9.3
- Correctness−2.2
The parts add to +20.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.