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
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 01:09:43 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 9 |
| Score | 78.0 | 76.7 | 54.8 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.93% | 23.02% |
| p50 latency | 106.4 ms | 121.7 ms | 13.8 ms |
| p95 latency | 192.9 ms | 215.6 ms | 74.6 ms |
| p99 latency | 281.6 ms | 233.0 ms | 251.2 ms |
| Correctness | 100.00% | 99.96% | 100.00% |
| Head lag | 0.48 blocks | 0.38 blocks | no cohort |
| Rate limited | 1,383 | 0 | 15 |
| Unsupported | 14 | 0 | 247 |
| Samples | 2,023 | 8,353 | 8,362 |
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
+1.3points
- Latency+1.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +1.3, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+23.2points
- Availability+29.8
- Latency−13.8
- Head freshness*+9.4
- Correctness−2.2
The parts add to +23.2, 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.