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
1h window · 60 minutes observed · generated 2026-08-27 20:20:10 UTC
| Metric | dRPC | NodeReal | Cloudflare | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 8 | 9 |
| Score | 86.2 | 82.4 | 47.4 | 0.0 |
| Status | Good | Good | Poor | Poor |
| Availability | 99.94% | 100.00% | 22.96% | 0.00% |
| p50 latency | 35.6 ms | 87.0 ms | 17.9 ms | 0.0 ms |
| p95 latency | 81.0 ms | 99.0 ms | 95.5 ms | 0.0 ms |
| p99 latency | 195.8 ms | 123.7 ms | 277.2 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | not measured |
| Head lag | 0.34 blocks | 0.34 blocks | no cohort | no cohort |
| Rate limited | 7 | 0 | 0 | 263 |
| Unsupported | 0 | 0 | 46 | 0 |
| Samples | 1,567 | 1,567 | 1,593 | 314 |
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.
dRPCvsNodeReal
+3.7points
- Latency+3.8
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +3.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.7points
- Availability+29.8
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.6
The parts add to +38.7, 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
+86.2points
- Availability+40.0
- Correctness*+20.0
- Latency*+16.6
- Head freshness*+9.6
The parts add to +86.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.