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
1h window · 60 minutes observed · generated 2026-08-27 12:29:48 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 2 | 6 |
| Score | 96.0 | 70.5 |
| Status | Excellent | Degraded |
| Availability | 99.94% | 100.00% |
| p50 latency | 24.8 ms | 112.0 ms |
| p95 latency | 47.0 ms | 204.6 ms |
| p99 latency | 101.1 ms | 217.6 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.20 blocks |
| Rate limited | 0 | 253 |
| Unsupported | 0 | 2 |
| Samples | 1,621 | 368 |
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
+25.5points
- Latency+25.9
- Head freshness−0.3
- Availability−0.0
- Correctness+0.0
The parts add to +25.5, exactly — the score is a weighted sum, so it comes apart.