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 07:57:53 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 70.0 | 51.1 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.99% | 100.00% | 23.11% |
| p50 latency | 18.0 ms | 104.9 ms | 13.0 ms |
| p95 latency | 29.5 ms | 193.7 ms | 70.3 ms |
| p99 latency | 59.6 ms | 268.8 ms | 130.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.59 blocks | no cohort |
| Rate limited | 0 | 1,530 | 0 |
| Unsupported | 0 | 17 | 287 |
| Samples | 9,735 | 2,168 | 9,667 |
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.3
- 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
+48.3points
- Availability+29.7
- Latency+11.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +48.3, 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.