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
24h window · 24 hours observed · generated 2026-08-26 18:08:05 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 78.1 | 52.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 23.11% |
| p50 latency | 18.9 ms | 106.6 ms | 15.8 ms |
| p95 latency | 33.0 ms | 195.6 ms | 92.3 ms |
| p99 latency | 70.8 ms | 241.2 ms | 248.0 ms |
| Correctness | 99.98% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.46 blocks | no cohort |
| Rate limited | 0 | 6,080 | 28 |
| Unsupported | 0 | 82 | 1,105 |
| Samples | 37,780 | 8,833 | 37,410 |
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
+21.3points
- Latency+21.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+46.6points
- Availability+29.7
- Latency+9.7
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.6, 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.