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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 16:09:28 UTC
| Metric | Merkle | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 7 | 8 | 9 |
| Score | 69.4 | 47.3 | 0.0 |
| Status | Degraded | Poor | Poor |
| Availability | 100.00% | 23.11% | 0.00% |
| p50 latency | 110.9 ms | 14.1 ms | 0.0 ms |
| p95 latency | 216.0 ms | 96.1 ms | 0.0 ms |
| p99 latency | 332.7 ms | 154.7 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.49 blocks | no cohort | no cohort |
| Rate limited | 1,352 | 0 | 1,447 |
| Unsupported | 14 | 247 | 0 |
| Samples | 1,918 | 8,362 | 1,658 |
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.1points
- Availability+29.7
- Latency−14.8
- 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.
Merklevs1RPC
+69.4points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.4
- Latency*+0.0
The parts add to +69.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.