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
7d window · 2.3 days observed · generated 2026-08-27 04:18:05 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 78.9 | 55.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.98% | 23.11% |
| p50 latency | 18.2 ms | 106.5 ms | 15.1 ms |
| p95 latency | 33.6 ms | 196.1 ms | 88.3 ms |
| p99 latency | 70.3 ms | 243.2 ms | 254.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.46 blocks | no cohort |
| Rate limited | 0 | 14,516 | 77 |
| Unsupported | 0 | 179 | 2,648 |
| Samples | 90,828 | 20,861 | 89,957 |
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.
PublicNodevsMerkle
+20.5points
- Latency+20.5
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+43.7points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.8
- Correctness−2.2
The parts add to +43.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.