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
1h window · 60 minutes observed · generated 2026-08-28 14:46:31 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 8 |
| Score | 85.2 | 82.7 | 46.5 |
| Status | Good | Good | Poor |
| Availability | 100.00% | 100.00% | 23.21% |
| p50 latency | 37.1 ms | 87.5 ms | 15.3 ms |
| p95 latency | 84.8 ms | 98.8 ms | 102.4 ms |
| p99 latency | 184.0 ms | 119.4 ms | 161.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.37 blocks | no cohort |
| Rate limited | 7 | 0 | 0 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,570 | 1,579 | 1,607 |
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
+2.5points
- Latency+2.5
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.7points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.7
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.