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-28 17:46:00 UTC
| Metric | Merkle | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 69.7 | 69.5 | 47.6 |
| Status | Degraded | Degraded | Poor |
| Availability | 100.00% | 99.87% | 23.11% |
| p50 latency | 109.9 ms | 123.3 ms | 14.2 ms |
| p95 latency | 205.4 ms | 209.7 ms | 93.7 ms |
| p99 latency | 293.9 ms | 225.5 ms | 161.9 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.45 blocks | 0.39 blocks | no cohort |
| Rate limited | 1,525 | 0 | 0 |
| Unsupported | 16 | 0 | 277 |
| Samples | 2,180 | 9,356 | 9,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
+0.2points
- Latency+0.2
- Head freshness−0.1
- Availability+0.1
- Correctness+0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+22.1points
- Availability+29.7
- Latency−14.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +22.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.