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 21:05:31 UTC
| Metric | PublicNode | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 2 | 8 | 9 |
| Score | 94.3 | 47.1 | 0.0 |
| Status | Excellent | Poor | Poor |
| Availability | 100.00% | 23.15% | 0.00% |
| p50 latency | 25.2 ms | 17.5 ms | 0.0 ms |
| p95 latency | 52.9 ms | 101.0 ms | 0.0 ms |
| p99 latency | 113.4 ms | 277.2 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.47 blocks | no cohort | no cohort |
| Rate limited | 0 | 0 | 1,416 |
| Unsupported | 0 | 244 | 0 |
| Samples | 8,324 | 8,248 | 1,627 |
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
+47.2points
- Availability+29.7
- Latency+10.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.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.
PublicNodevs1RPC
+94.3points
- Availability+40.0
- Latency*+24.9
- Correctness*+20.0
- Head freshness*+9.4
The parts add to +94.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.