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 15:06:40 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 95.2 | 70.9 | 47.6 |
| Status | Excellent | Degraded | Poor |
| Availability | 99.99% | 100.00% | 23.18% |
| p50 latency | 25.0 ms | 109.8 ms | 16.8 ms |
| p95 latency | 49.6 ms | 191.2 ms | 97.7 ms |
| p99 latency | 113.1 ms | 277.4 ms | 166.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.44 blocks | no cohort |
| Rate limited | 0 | 1,307 | 0 |
| Unsupported | 0 | 12 | 243 |
| Samples | 8,355 | 1,921 | 8,290 |
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
+24.3points
- Latency+24.4
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +24.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.6points
- Availability+29.7
- Latency+10.7
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.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.