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
30d window · 47 hours observed · generated 2026-08-26 19:11:14 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 1 | 6 |
| Score | 99.4 | 78.4 |
| Status | Excellent | Good |
| Availability | 99.97% | 99.97% |
| p50 latency | 18.4 ms | 106.6 ms |
| p95 latency | 32.9 ms | 196.1 ms |
| p99 latency | 68.7 ms | 244.4 ms |
| Correctness | 99.98% | 100.00% |
| Head lag | 0.49 blocks | 0.46 blocks |
| Rate limited | 0 | 12,211 |
| Unsupported | 0 | 149 |
| Samples | 75,926 | 17,581 |
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.0points
- Latency+21.1
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.