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-26 19:08:06 UTC
| Metric | PublicNode | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 8 | 9 |
| Score | 99.4 | 64.7 | 52.6 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.97% | 90.50% | 23.10% |
| p50 latency | 18.9 ms | 259.6 ms | 15.8 ms |
| p95 latency | 33.3 ms | 2579.7 ms | 92.0 ms |
| p99 latency | 71.0 ms | 4625.5 ms | 246.8 ms |
| Correctness | 99.98% | 98.18% | 100.00% |
| Head lag | 0.49 blocks | 0.94 blocks | no cohort |
| Rate limited | 0 | 6,439 | 28 |
| Unsupported | 0 | 0 | 1,108 |
| Samples | 37,775 | 7,708 | 37,406 |
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.
PublicNodevs1RPC
+34.7points
- Latency+30.0
- Availability+3.8
- Head freshness+0.5
- Correctness+0.4
The parts add to +34.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+46.8points
- Availability+29.7
- Latency+9.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.8, 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.