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 16:04:06 UTC
| Metric | PublicNode | Cloudflare |
|---|---|---|
| Rank | 2 | 9 |
| Score | 98.4 | 53.5 |
| Status | Excellent | Degraded |
| Availability | 99.97% | 23.15% |
| p50 latency | 20.0 ms | 14.8 ms |
| p95 latency | 39.0 ms | 85.9 ms |
| p99 latency | 92.8 ms | 235.0 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.49 blocks | no cohort |
| Rate limited | 0 | 55 |
| Unsupported | 0 | 1,099 |
| Samples | 37,687 | 37,323 |
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
+44.9points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.0
- Correctness−2.2
The parts add to +44.9, 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.