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 15:59:11 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 78.7 | 54.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.95% | 23.09% |
| p50 latency | 19.2 ms | 106.8 ms | 16.0 ms |
| p95 latency | 32.4 ms | 197.1 ms | 90.8 ms |
| p99 latency | 70.8 ms | 245.4 ms | 251.7 ms |
| Correctness | 99.98% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 6,273 | 9 |
| Unsupported | 0 | 85 | 1,147 |
| Samples | 39,162 | 9,077 | 38,867 |
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.7points
- Latency+20.7
- Head freshness−0.0
- Availability+0.0
- Correctness−0.0
The parts add to +20.7, 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.