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 12:03:54 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 8 |
| Score | 97.4 | 86.9 | 50.0 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.96% | 23.18% |
| p50 latency | 22.2 ms | 33.2 ms | 15.1 ms |
| p95 latency | 42.2 ms | 77.5 ms | 85.3 ms |
| p99 latency | 110.2 ms | 176.2 ms | 117.3 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 38 | 19 |
| Unsupported | 0 | 0 | 240 |
| Samples | 8,272 | 8,076 | 8,210 |
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
+10.5points
- Latency+10.6
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +10.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.4points
- Availability+29.7
- Latency+10.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.4, 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.