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
24h window · 24 hours observed · generated 2026-08-27 00:01:24 UTC
| Metric | PublicNode | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 1 | 8 | 9 |
| Score | 99.4 | 47.4 | 0.0 |
| Status | Excellent | Poor | Poor |
| Availability | 99.98% | 23.10% | 0.00% |
| p50 latency | 18.4 ms | 16.2 ms | 0.0 ms |
| p95 latency | 35.0 ms | 94.0 ms | 0.0 ms |
| p99 latency | 73.5 ms | 247.5 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.49 blocks | no cohort | no cohort |
| Rate limited | 0 | 39 | 6,415 |
| Unsupported | 0 | 1,102 | 0 |
| Samples | 37,591 | 37,234 | 7,350 |
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
+52.0points
- Availability+29.7
- Latency+15.1
- Head freshness*+9.4
- Correctness−2.2
The parts add to +52.0, 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
+99.4points
- Availability+40.0
- Latency*+30.0
- Correctness*+20.0
- Head freshness*+9.4
The parts add to +99.4, 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.