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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 14:47:31 UTC
| Metric | NodeReal | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 8 |
| Score | 81.8 | 79.4 | 47.7 |
| Status | Good | Good | Poor |
| Availability | 99.99% | 99.99% | 23.18% |
| p50 latency | 87.5 ms | 35.3 ms | 13.9 ms |
| p95 latency | 99.4 ms | 115.0 ms | 91.5 ms |
| p99 latency | 125.9 ms | 197.7 ms | 136.5 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 20 | 6 |
| Unsupported | 0 | 0 | 278 |
| Samples | 9,227 | 9,234 | 9,382 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsdRPC
+2.4points
- Latency+2.4
- Head freshness+0.0
- Correctness−0.0
- Availability+0.0
The parts add to +2.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+34.1points
- Availability+29.7
- Head freshness*+9.6
- Latency−2.9
- Correctness−2.2
The parts add to +34.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.