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 21:23:37 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 2 | 6 |
| Score | 94.4 | 70.8 |
| Status | Excellent | Degraded |
| Availability | 100.00% | 100.00% |
| p50 latency | 25.1 ms | 109.7 ms |
| p95 latency | 52.5 ms | 191.2 ms |
| p99 latency | 113.5 ms | 231.9 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.60 blocks |
| Rate limited | 0 | 1,382 |
| Unsupported | 0 | 13 |
| Samples | 8,813 | 2,062 |
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
+23.6points
- Latency+23.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +23.6, exactly — the score is a weighted sum, so it comes apart.