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 13:02:23 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 4 | 8 |
| Score | 98.8 | 78.6 | 47.6 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.96% | 23.22% |
| p50 latency | 21.1 ms | 33.9 ms | 13.5 ms |
| p95 latency | 34.7 ms | 119.3 ms | 90.5 ms |
| p99 latency | 70.7 ms | 202.3 ms | 135.1 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 18 | 6 |
| Unsupported | 0 | 0 | 244 |
| Samples | 8,234 | 8,028 | 8,170 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+20.3points
- Latency+20.4
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +20.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+51.2points
- Availability+29.7
- Latency+14.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +51.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.