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
7d window · 3.7 days observed · generated 2026-08-28 13:03:38 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 1 | 6 |
| Score | 99.4 | 78.0 |
| Status | Excellent | Good |
| Availability | 99.98% | 99.99% |
| p50 latency | 19.4 ms | 106.8 ms |
| p95 latency | 35.3 ms | 195.6 ms |
| p99 latency | 75.6 ms | 243.7 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks |
| Rate limited | 0 | 23,006 |
| Unsupported | 0 | 280 |
| Samples | 144,374 | 33,257 |
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
+21.4points
- Latency+21.4
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.