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
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 00:00:34 UTC
| Metric | PublicNode | Cloudflare |
|---|---|---|
| Rank | 2 | 8 |
| Score | 98.6 | 49.3 |
| Status | Excellent | Poor |
| Availability | 100.00% | 23.17% |
| p50 latency | 17.6 ms | 15.5 ms |
| p95 latency | 38.1 ms | 86.1 ms |
| p99 latency | 93.6 ms | 263.3 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.49 blocks | no cohort |
| Rate limited | 0 | 11 |
| Unsupported | 0 | 239 |
| Samples | 8,180 | 8,111 |
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.
PublicNodevsCloudflare
+49.3points
- Availability+29.7
- Latency+12.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +49.3, 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.