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
- NodeReal
- dRPC
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 11:39:16 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 4 | 8 | 9 |
| Score | 78.5 | 48.7 | 0.0 |
| Status | Good | Poor | Poor |
| Availability | 99.96% | 23.19% | 0.00% |
| p50 latency | 32.8 ms | 12.9 ms | 0.0 ms |
| p95 latency | 117.6 ms | 83.9 ms | 0.0 ms |
| p99 latency | 212.7 ms | 134.6 ms | 0.0 ms |
| Correctness | 99.99% | 100.00% | not measured |
| Head lag | 0.37 blocks | no cohort | no cohort |
| Rate limited | 21 | 6 | 1,572 |
| Unsupported | 0 | 271 | 0 |
| Samples | 9,006 | 9,151 | 1,809 |
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 dRPC, the highest scorer of those selected.
dRPCvsCloudflare
+29.8points
- Availability+29.7
- Head freshness*+9.5
- Latency−7.2
- Correctness−2.2
The parts add to +29.8, 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.
dRPCvs1RPC
+78.5points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.5
- Latency*+9.0
The parts add to +78.5, 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.