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 02:27:43 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 2 | 6 |
| Score | 98.8 | 77.7 |
| Status | Excellent | Good |
| Availability | 99.99% | 100.00% |
| p50 latency | 17.2 ms | 105.7 ms |
| p95 latency | 35.3 ms | 193.2 ms |
| p99 latency | 92.0 ms | 229.0 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.45 blocks |
| Rate limited | 0 | 1,395 |
| Unsupported | 0 | 19 |
| Samples | 8,935 | 1,965 |
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
- Availability−0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.