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-27 17:33:38 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 98.2 | 78.0 | 53.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 100.00% | 23.16% |
| p50 latency | 20.4 ms | 107.3 ms | 15.0 ms |
| p95 latency | 40.0 ms | 193.2 ms | 86.8 ms |
| p99 latency | 95.8 ms | 235.0 ms | 241.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.52 blocks | no cohort |
| Rate limited | 0 | 6,003 | 36 |
| Unsupported | 0 | 74 | 1,123 |
| Samples | 38,493 | 8,681 | 38,195 |
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.2points
- Latency+20.2
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.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.