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
30d window · 2.6 days observed · generated 2026-08-27 11:20:14 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 92.5 | 55.2 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.93% | 23.11% |
| p50 latency | 18.5 ms | 33.8 ms | 15.0 ms |
| p95 latency | 33.8 ms | 72.0 ms | 86.6 ms |
| p99 latency | 71.7 ms | 167.7 ms | 251.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 626 | 96 |
| Unsupported | 0 | 0 | 2,983 |
| Samples | 102,317 | 99,873 | 101,363 |
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.
PublicNodevsdRPC
+6.9points
- Latency+7.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +6.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.2points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.3
- Correctness−2.2
The parts add to +44.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.