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
1h window · 60 minutes observed · generated 2026-08-27 05:50:55 UTC
| Metric | PublicNode | Cloudflare |
|---|---|---|
| Rank | 1 | 8 |
| Score | 99.5 | 51.3 |
| Status | Excellent | Degraded |
| Availability | 100.00% | 22.98% |
| p50 latency | 17.3 ms | 12.8 ms |
| p95 latency | 28.6 ms | 69.2 ms |
| p99 latency | 50.5 ms | 242.0 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.45 blocks | no cohort |
| Rate limited | 0 | 0 |
| Unsupported | 0 | 49 |
| Samples | 1,625 | 1,613 |
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
+48.2points
- Availability+29.8
- Latency+11.1
- Head freshness*+9.5
- Correctness−2.2
The parts add to +48.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.