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:12:03 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 70.0 | 50.6 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.99% | 100.00% | 23.07% |
| p50 latency | 19.1 ms | 105.3 ms | 13.3 ms |
| p95 latency | 31.7 ms | 194.3 ms | 74.7 ms |
| p99 latency | 66.4 ms | 228.0 ms | 116.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.61 blocks | no cohort |
| Rate limited | 0 | 1,321 | 7 |
| Unsupported | 0 | 14 | 251 |
| Samples | 8,483 | 1,917 | 8,431 |
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.2
- 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.9points
- Availability+29.7
- Latency+11.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +48.9, 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.