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 09:37:10 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 70.0 | 50.2 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.98% | 100.00% | 23.06% |
| p50 latency | 19.3 ms | 105.2 ms | 13.4 ms |
| p95 latency | 32.3 ms | 194.3 ms | 76.8 ms |
| p99 latency | 67.9 ms | 228.8 ms | 116.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.62 blocks | no cohort |
| Rate limited | 0 | 1,429 | 19 |
| Unsupported | 0 | 17 | 270 |
| Samples | 9,166 | 2,067 | 9,105 |
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
+29.4points
- Latency+29.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+49.2points
- Availability+29.7
- Latency+12.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +49.2, 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.