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-28 15:48:18 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 2 | 6 |
| Score | 98.4 | 77.5 |
| Status | Excellent | Good |
| Availability | 99.98% | 100.00% |
| p50 latency | 21.4 ms | 107.4 ms |
| p95 latency | 37.3 ms | 196.0 ms |
| p99 latency | 80.8 ms | 260.1 ms |
| Correctness | 99.98% | 100.00% |
| Head lag | 0.49 blocks | 0.53 blocks |
| Rate limited | 0 | 6,210 |
| Unsupported | 0 | 73 |
| Samples | 38,924 | 9,016 |
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.9points
- Latency+20.9
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.