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
6h window · 6.0 hours observed · generated 2026-08-27 20:56:11 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 8 |
| Score | 94.5 | 89.1 | 47.0 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 99.98% | 23.15% |
| p50 latency | 25.2 ms | 35.0 ms | 17.5 ms |
| p95 latency | 52.1 ms | 70.7 ms | 101.3 ms |
| p99 latency | 112.7 ms | 191.9 ms | 277.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.35 blocks | no cohort |
| Rate limited | 0 | 24 | 0 |
| Unsupported | 0 | 0 | 284 |
| Samples | 9,700 | 9,466 | 9,606 |
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
+5.4points
- Latency+5.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +5.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.5points
- Availability+29.7
- Latency+10.5
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.5, 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.