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 03:47:28 UTC
| Metric | PublicNode | Cloudflare |
|---|---|---|
| Rank | 1 | 9 |
| Score | 99.4 | 52.3 |
| Status | Excellent | Degraded |
| Availability | 99.98% | 23.13% |
| p50 latency | 18.3 ms | 16.1 ms |
| p95 latency | 35.2 ms | 93.3 ms |
| p99 latency | 74.2 ms | 246.5 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.49 blocks | no cohort |
| Rate limited | 0 | 45 |
| Unsupported | 0 | 1,137 |
| Samples | 38,839 | 38,486 |
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.1points
- Availability+29.7
- Latency+10.2
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.1, 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.