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
24h window · 24 hours observed · generated 2026-08-27 07:25:07 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 86.4 | 77.9 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 100.00% | 100.00% |
| p50 latency | 18.2 ms | 87.1 ms | 107.2 ms |
| p95 latency | 35.3 ms | 100.3 ms | 193.3 ms |
| p99 latency | 74.0 ms | 129.4 ms | 240.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.49 blocks |
| Rate limited | 0 | 0 | 6,061 |
| Unsupported | 0 | 0 | 72 |
| Samples | 38,245 | 37,323 | 8,668 |
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.
PublicNodevsNodeReal
+13.0points
- Latency+13.2
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.5points
- Latency+21.5
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.