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
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 4.2 days observed · generated 2026-08-29 01:26:21 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.0 | 61.7 | 53.6 |
| Status | Good | Degraded | Degraded |
| Availability | 99.99% | 83.07% | 23.12% |
| p50 latency | 107.0 ms | 320.2 ms | 14.6 ms |
| p95 latency | 196.0 ms | 4778.7 ms | 87.2 ms |
| p99 latency | 244.3 ms | 8408.8 ms | 248.3 ms |
| Correctness | 100.00% | 97.52% | 100.00% |
| Head lag | 0.49 blocks | 0.90 blocks | no cohort |
| Rate limited | 26,249 | 28,011 | 122 |
| Unsupported | 319 | 0 | 4,806 |
| Samples | 37,925 | 34,188 | 163,152 |
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.
Merklevs1RPC
+16.3points
- Latency+8.6
- Availability+6.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +16.3, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+24.4points
- Availability+29.7
- Latency−12.5
- Head freshness*+9.4
- Correctness−2.2
The parts add to +24.4, 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.