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.8 days observed · generated 2026-08-27 14:56:00 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 92.2 | 54.7 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.93% | 23.11% |
| p50 latency | 18.9 ms | 33.8 ms | 15.1 ms |
| p95 latency | 34.6 ms | 71.9 ms | 87.9 ms |
| p99 latency | 73.7 ms | 169.0 ms | 250.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 644 | 96 |
| Unsupported | 0 | 0 | 3,156 |
| Samples | 108,202 | 105,607 | 107,203 |
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
+7.2points
- Latency+7.3
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.7points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.8
- Correctness−2.2
The parts add to +44.7, 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.